Siebel Remote and Replication Manager Administration Guide > Extracting and Initializing a Remote Database > Process of Extracting the Server Database >

Verifying the Reporting Hierarchy and Employee Status


This process is a step in Process of Extracting the Server Database.

You must make sure that the reporting hierarchy for your organization is accurate and that the employee status is valid before you can extract the server database for a remote client.

To verify the reporting hierarchy and employee status

  1. Log in to the Siebel Server with administrator privileges.

    For more information, see Logging In to the Siebel Server as an Administrator.

  2. Make sure the reporting hierarchy for your organization is valid:
    1. Navigate to the Administration - Group screen, and then the Positions view.
    2. Verify that the user you are about to extract contains a valid position in your organization hierarchy.

      The routing rules use information from the Positions view of the Administration - Group screen. This information might affect the server database extract. For more information, see How Positions, Organizations, and Responsibilities Affect Access, and Siebel Applications Administration Guide.

  3. Verify the employment status.

    You must make sure that the Employee record for the remote client displays a status of Active. Some earlier versions of Siebel CRM did not populate this field. An inactive status or a null field value might prevent a successful extraction and initialization, and might cause incorrect data routing. You do the following work:

    1. Navigate to the Administration - User screen, and then the Employees view.
    2. Query the User ID field for the employee record you must verify.
    3. Click the Last Name field.
    4. Click the Job Information view tab.

      To view the Job Information view tab, it might be necessary for you to click the down arrow that is located at the far right of the view tab bar.

    5. In the Job Information form, verify that the Employment Status field is Active.

      The remote client environment requires a value of Active.

How Positions, Organizations, and Responsibilities Affect Access

Employee responsibilities and positions determine the access that the user possesses to the server database. Balancing the data routing model with user access helps to optimize the size of the local database for this user. It also helps to minimize synchronization time. You must make sure the routing model is consistent with the user responsibilities and position. For information about configuring the routing model, see Configuring the Remote Client to Automatically Synchronize.

Keeping Organization Information Current on the Remote Client

Modifications that you make to your organization, such modifying a position, division, or territory, can cause routers to reevaluate visibility for objects that are related to these modified objects. These modifications can affect Transaction Router performance and can result in a large backlog of transactions.

Siebel Remote creates progressively more transactions the higher in the hierarchy where you modify, add, or delete a position. The Transaction Processor and the Transaction Router might require a significant amount of time to work through the backlog and route these modifications to users. You can do the following to improve throughput:

  • Keep organization information current on the remote client
  • Use multiple routers

To keep organization information current on the remote client

  • Reextract users after you modify your organization.

CAUTION:  For important caution information about modifying a position for a user or modifying a routing model, see Caution About Extracting the Server Database.

For more information, see About the Standard Routing Model.

Updating a Responsibility

If you modify a user responsibility, then Siebel Remote downloads this new information to the local database during the next synchronization. It is not necessary to reextract the server database. For more information, see Limiting Access to Views by Modifying Responsibilities.

To update a responsibility

  1. Modify the responsibility on the Siebel Server.
  2. Inform the user to synchronize, log out, and then log back in to the remote client.

    This step is necessary to access the views that Siebel Remote displays under the new responsibility.

Siebel Remote and Replication Manager Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.