Bookshelf Home | Contents | Index | PDF |
Siebel Life Sciences Guide > Administering and Managing Accounts in Life Sciences > Generating Account HierarchiesData aggregation is available using 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 HierarchiesThe 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 about Global Accounts in the Siebel Applications Administration Guide. When new accounts are created, 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. For information about configuring the Generate Hierarchy button, see About Configuring the Generate Hierarchy Button. To generate a default account hierarchy
Custom Account HierarchiesIn 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 customer 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 custom account hierarchy of selected accounts
|
Siebel Life Sciences Guide | Copyright © 2008, Oracle. All rights reserved. | |