Siebel Life Sciences Guide > Administering and Managing Accounts > Administrator Procedures >

Generating Account Hierarchies


Data aggregation is available via the Roll-up views provided the administrator defines one or more hierarchies. The application administrator typically defines a "default" hierarchy by associating accounts with one another using the parent field on a company form, or the subaccount view for child accounts. Administrators can define account hierarchies display aggregated data—the activities, opportunities, contacts, and coverage teams—across account organizational structures. For example, the top node of the hierarchy contains activities for the organization, the subsidiaries below the organization, the departments at the subsidiaries, and contacts working at any level of the tree. As the end users move up and down the tree, they see more or less data rolled up to the selected level.

The application administrator can define two types of hierarchies for data aggregation—a default hierarchy for all end users and specific hierarchies that are used only by certain end users.

Default Account Hierarchies

The application administrator sets up a default account hierarchy once, during the initial application setup. The default hierarchy is available to all end users who are not tied to a specific hierarchy and who have been granted view access to the accounts represented in the hierarchy. It is the administrator's responsibility to give end user access to Account views. For more information, see Applications Administration Guide.

When new accounts are added, they are automatically added to the default hierarchy tree and the contacts, coverage teams, activities, and opportunities that are associated with the accounts are automatically displayed in the rollup views.

In the preconfigured application, using the Generate Hierarchy button adds only parent account and child accounts to the hierarchy. Any account that does not have a child or parent is not displayed in the rollup views. In Siebel Tools, you can change the DynHierarchy LoadAllAccounts user property to alter this behavior.

The DynHierarchy LoadAllAccounts user property on the Dynamic Hierarchy Direct Relationship business component can be set to N or Y. When it is set to N, only parent and children appear in the generated hierarchy. When DynHierarchy LoadAllAccounts user property is set to Y, all accounts are added to the account hierarchy. For information on setting user properties, see Siebel Tools Reference.

To generate a default account hierarchy

  1. In the application-level menu, choose View > Site Map > Application Administration > Account Hierarchies.
  2. In the Account Hierarchies list, click Generate Hierarchy.
  3. The parent-child account relationships that have been defined in your application are registered for participation in the roll-up views. This process may take some time, depending on the quantity of account records that are in your existing environment.

    When the account hierarchy has been generated, a new record appears in the Account Hierarchies list. The Hierarchy Name field of the record contains the user Id of the administrator who generated the account hierarchy and the time it was generated. If it is the only account hierarchy record, the Default field is automatically checked. The accounts that have been added for participation in the roll-up views appear in the Account Relationships list.

    NOTE:  If no accounts are visible in the Account Relationships list, click the query button, step off the query, and click Go to refresh the view.

  4. Optional. Rename the account hierarchy and, if necessary, check the Default field.
  5. NOTE:  If end users are using the application when you generate the account hierarchy, they must log off and log on again to see the default account hierarchy in the rollup views.

Dynamic Account Hierarchies

In some cases, users work with particular accounts or subaccounts of a large corporation, but not with others. In these instances, some end users do not need to or should not see aggregated data across the entire corporation. An administrator can define a custom hierarchical structure across which data can be aggregated. This defined structure, called a dynamic hierarchy, can be as simple or complex as needed and offers users the ability to aggregate data across the accounts they are interested in seeing.

To create a dynamic account hierarchy of selected accounts

  1. In the application-level menu, choose View > Site Map > Application Administration > Account Hierarchies.
  2. Create a new account hierarchy record.
  3. Click the add button in the Account Relationships list, select accounts in the Add Account dialog box, and click OK.
  4. All the accounts in the Account Relationship list belong to the new account hierarchy.

  5. To define parent and child relationships, select an account in the Account Relationship list that has no parent account, click the select button in the Parent Account field, and select a parent account in the Pick Parent Account dialog box.
  6. Repeat Step 4 for all accounts that have no parents.
  7. Associate the dynamic hierarchy with an organization.
  8. End users can only see the account hierarchy with which their current position's primary organization is tied. It is the administrator's responsibility to associate end users with positions, positions with organizations, and organizations with hierarchies. For more information, see Applications Administration Guide.


 Siebel Life Sciences Guide 
 Published: 18 April 2003