Siebel Database Upgrade Guide > Postupgrade Tasks for Siebel Applications >

Generating Siebel Reporting Relationships

Upgrades from: All Supported Siebel releases.

Environments: Development, production test, production.

Platforms: Windows, UNIX, IBM z/OS.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

The Generate Reporting Relationships process needs to be executed after the upgrade process and whenever the denormalized hierarchy structure (S_PARTY_RPT_REL) becomes out of sync with the data in the normalized tables (S_PARTY). Tables can become out of sync in the following cases:

  • After upgrading, the organizational hierarchy (even if there is only one organization) must be established to maintain appropriate visibility in the views cited above.
  • When EIM is used to import or update any of the hierarchies (positions, organizations, or access groups).

There are three visibility hierarchies—position, organization, and access groups. These hierarchies are denormalized and maintained in the table S_PARTY_RPT_REL. These denormalized hierarchies are necessary for executing visibility modes that go up or down a hierarchy. For example:

  • Manager view mode. My Team's Accounts View displays all accounts on which managers and their subordinates are working.
  • Suborganizations view mode. All Contacts across My Organizations View displays all contacts that are associated to either my organization or any of my organization's suborganizations.

The Generate Reporting Relationships process rebuilds the denormalized relationships in the S_PARTY_RPT_REL table so that the hierarchical view modes display the correct information. The basic operation of the function is to empty the S_PARTY_RPT_REL table and then walk through each S_PARTY record to re-create the denormalized hierarchical structures in the table. This process generates a large number of transactions for Siebel Remote users and regional nodes.

This operation is time and CPU/memory-intensive. The process may take several minutes, depending on the size and complexity of your organizational structures. Do not perform this when you are running other memory-intensive processes.

To generate reporting relationships

  1. If you have an active Siebel Remote environment, confer with a Oracle Administrator. The Administrator should arrange for the Transaction Processor to be paused before performing this procedure.
  2. Choose Group Administration under Site Map and navigate to the Positions view in the Siebel Web Client application. Click the Generate Reporting Relationships button in the Position List Applet NB. Note that generating the reporting relationship may cause a large number of Siebel Remote transactions to be generated.
  3. When this has completed, restart the Transaction Processor.
Siebel Database Upgrade Guide Copyright © 2008, Oracle. All rights reserved.