Using Siebel Tools > Managing Repositories > Viewing, Renaming, Comparing, and Configuring Repositories >

Configuring Siebel CRM to Read Data from a Single Repository


The example in this topic describes how to configure Siebel CRM to read data from a single repository when the Siebel database contains multiple repositories.

To configure Siebel CRM to read data from a single repository

  1. Log in to the Siebel client with administrative privileges, and complete the following steps:
    1. Navigate to the Administration - Order Management screen, and then the Message Types view.
    2. Navigate to the Payload view, and then create a new record.
    3. In the new record, access the drop-down list for the Response Field.

      If the Response Field drop-down list:

      • Does not display duplicate values. The Siebel database does not contain multiple repositories, and you can exit this task.
      • Displays duplicate values. The Siebel database contains multiple repositories, and you must configure Siebel CRM to read data only from a single repository. Continue to Step 2.
    4. Delete the new record that you created.
  2. Configure Siebel CRM to read data only from a single repository:
    1. Log in to Siebel Tools.
    2. In the Object Explorer, click Pick List.
    3. In the Pick Lists list, query the Name property for the following value:

    UMS PickList Response Field

    1. Modify the Search Specification property using the value from the following table.
      Property
      Value

      Search Specification

      [Buscomp] = 'UMS Response' and [Repository Id] = RepositoryId()

      Siebel CRM displays the UMS Type Variables List Applet in Step 2. This applet references the UMS Type Variable business component. It displays the Response Field Name field and uses the UMS PickList Response Field picklist for this field. This picklist uses the following search specification when it references the UMS Pick List Field business component:

    [Buscomp] = 'UMS Response'

    The UMS Pick List Field business component references the S_FIELD table. It does not include a search specification, so Siebel CRM does not filter the records that it gets according to the specifications that the repository contains. If the Siebel database contains multiple repositories, then Siebel CRM gets all the field names from all repositories, and then displays them in the picklist. This configuration might result in Siebel CRM displaying duplicate values that you cannot choose in the picklist. To correct this situation, you create a search specification that configures Siebel CRM to read data only from the current repository.

  3. Deliver your modifications.
  4. Repeat Step 1 to make sure the Response Field drop-down list does not display duplicate values.

Tagging Objects When Using Siebel Remote

This topic describes how to configure your environment so that you can use object tagging with Siebel Remote. Siebel Tools does not synchronize any modifications that you make when you use Siebel Remote. It communicates only with the repository on the Siebel Server through project Check Out, project Check In, or a Get. You do not use Siebel Tools to synchronize the modifications that you make through object tagging in a Siebel Remote client. Instead, you must use the synchronization features that Siebel Remote provides. For more information, see Siebel Remote and Replication Manager Administration Guide.

To tag objects when using Siebel Remote

  1. Make sure every developer who uses the Siebel Remote client uses the MOBILE CLIENT - STANDARD routing model to synchronize client changes with the server database.

    Developers must not use the MOBILE CLIENT - EXTRACT ONLY routing model because it only extracts the local database. It does not synchronize the local database. For more information about how to use these routing models and Siebel Remote, Siebel Remote and Replication Manager Administration Guide.

  2. Make sure the tools.cfg configuration file and the Local ODBC data source that the Siebel Web Client uses each reference the same database file, such as sse_data.dbf.
  3. Make sure each developer synchronizes any modifications that the developer makes through object tagging with the Siebel Server, and that each developer periodically synchronizes their local database with the Siebel Server so that their client includes the object tagging modifications that other developers make.
Using Siebel Tools Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.