Bookshelf Home | Contents | Index | Search | PDF

Siebel eHealthcare Guide > Companies > Administrator Procedures >

Generating Company Hierarchies for Data Aggregation

---

Data aggregation is available by 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 Company hierarchies to display aggregated data—the activities, opportunities, contacts, and coverage teams—across 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 Company Hierarchies

The application administrator sets up a default company 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 companies represented in the hierarchy. It is the administrator's responsibility to give end users access to Company views. For more information, see Siebel Applications Administration Guide.

When new companies are added, they are automatically added to the default hierarchy tree and the contacts, coverage teams, activities, and opportunities that are associated with the company are automatically displayed in the roll-up views.

In the preconfigured application, using the Generate Hierarchy button adds only parent account and child companies to the hierarchy. Any company that does not have a child or parent is not displayed in the roll-up 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 a generated hierarchy. When DynHierarchy LoadAllAccounts user property is set to Y, all companies are added to the generated hierarchy. For more information on setting user properties, see Siebel Tools Reference.

To generate a default company hierarchy

In the application-level menu, choose View > Site Map > Application Administration > Account Hierarchies.
In the Account Hierarchies list, click Generate Hierarchy.

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 company hierarchy has been generated, a new record appears in the Company Hierarchies list. The Hierarchy Name field of the record contains the user Id of the administrator who generated the hierarchy and the time it was generated. If it is the only hierarchy record, the Default field is automatically checked. The companies that have been added for participation in the roll-up views appear in the Company Relationships list.

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

Optional. Rename the company hierarchy and, if necessary, check the Default field.

NOTE:  If end users are using the application when you generate a hierarchy, they must log off and log on again to see the default hierarchy in the roll-up views.

Dynamic Company Hierarchies

In some cases, users work with particular companies within 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 companies they are interested in seeing.

To create a dynamic company hierarchy of selected companies

In the application-level menu, choose View > Site Map > Application Administration > Company Hierarchies.
Create a new company hierarchy record.
Click the Add button in the Company Relationships list, select companies in the Add Company dialog box, and click OK.

All the accounts in the Company Relationship list belong to the new account hierarchy.

To define parent and child relationships, select an company in the Company Relationship list that has no parent, click the select button in the Parent Company field, and select a parent company in the Pick Parent Company dialog box.
Repeat Step 4 for all companies that have no parents.
Associate the dynamic hierarchy with an organization.

End users can only see the 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 Siebel Applications Administration Guide

Bookshelf Home | Contents | Index | Search | PDF