You are on page 1of 8

Global Account Hierarchy Model POC Note: The POC was done on Siebel 8.

.1 vanilla link as the DEV web link thin client did not have the necessary views enabled on the Accounts Screen. Requirement: To perform a general POC on Global Account hierarchy model in Siebel 8.0.

Siebel Application Used: Siebel 8.1 Sales (Out-of-the-Box) Details: The Global accounts module provides a combined view of the accounts between internal sales organization and partners sales organization. For a given account, the global views show details for related sub entities like sub accounts / contacts / opportunities / activities etc. These sub entities can be further extended to include other entities; like orders / quotes etc for a given account. Accounts and the relationship with sub accounts are maintained in two methods with respect to the Global account module in Siebel; 1. The administrator can create a default hierarchy based on parent account field on the account record, 2. The administrator can define a custom hierarchy and specify the relationship between parent and child accounts (this is purely based on the relationship defined on the custom hierarchy and not based on the Parent account field on the account list/form applet) Before using global accounts on the application, we need to setup hierarchies on the Global Account Administration View.

The account hierarchy defined will contain the account relationship records across all account records in the database (the account relationships list applet shows this information)

To start with, the administrator can create a default hierarchy, which will automatically create the parent account and child account relationships based on the value filled into the Parent account field on the account list/form applet. To create a new default hierarchy, the user navigates to Accounts Global Account Administration click on the Generate Hierarchy button. This will create a new hierarchy record and create the child relationships automatically for all accounts in the database across organizations. But the parent child relation is based on Parent field on the account record.

The above screen shows how the KR Org 2 Ac 1 is the parent for KR Org 2 Ac 2. This relationship will automatically be picked up and stored into the default hierarchy. In this default hierarchy, KR Org 2 Ac 3 will not be related to any parent account as the Parent field is not populated. After generating the default hierarchy, the user logs out and logs in to the application. The user will now be able to view the global accounts hierarchy list. Sample screen shown below:

The screen shows Parent and Child accounts and its related entities. Two separate sets of data have been prepared for the POC demo. Data Set 1: User SADMIN set to a position on the Default Organization (Siebel Administrator) and account records created. On this scenario, parent and child accounts have been related using the Parent field on the account list/form applet. Then the default hierarchy was generated. Additionally, data was populated onto the related sub entities like Contacts/Activities/Account Team/Opportunities

List of contacts created across child accounts:

List of Opportunities created across child accounts:

List of activities created across child account/opportunity/contact

List of Account Team members across parent/child accounts:

Additional Entity: Quotes

Data Set 2: User SADMIN set to a new position on a new organization and account records created.

From the above screen shot, the account record KR Org 2 Ac 3 does not have a related parent record set in the Parent field. But the screen shot shows KR Org 2 Ac 3 as a sub account of KR Org 2 Ac 1. This is

possible using custom hierarchy definition. In order to set the custom hierarchy, administrator navigates to Accounts Global account administration. Create a new record and enter a hierarchy name. Do not set the default flag. On the below list applet, the administrator will manually define the parent account and the related child account definition. Refer screen shot shown below:

Continued This hierarchy will also include accounts from other organizations. In such a case, on the Global Account hierarchy list, we see all the accounts on the All Global Accounts Across Organizations

From the above screen shot, we see that accounts created are from two different organizations which appear on a single view. Updating Hierarchies: 1. Manual The administrator selects the specific hierarchy record on Global Account Administration list applet and edits the relationship on the child applet Account Relationships 2. Automated Use Generate Hierarchy business service in a batch workflow policy. In addition to this, separate hierarchies can be specified at organization level, so that users on that organization view the specific parent/child account relationships as defined on the hierarchy. This can be

a custom/generated hierarchy. The following screen shot shows the setup of a hierarchy on the organization: Navigate to Administration Groups Organizations. Query on the particular organization. On the below form applet, update the Account hierarchy field.

To add new business objects to Global account hierarchy view: Navigate to Administration Data List of Values Query for GLOBACC_USERPREF Add new record for this type and set the Display value and LIC to the Object name. Eg: Assets, Quotes, Orders. In addition to this, Siebel tools configuration is required to show this entity on the hierarchy tree. After complete configuration, if entities need to be hidden on demand, then follow this procedure: To enable/disable additional related entities on the Global accounts: Navigate to User preferences Global Accounts.

Administrator can hide/unhide additional entities. To include more entities, Siebel tools configuration is required. (Steps provided on Bookshelf) Account setup: Accounts: Filter for KR* Organizations: Filter for KR* Siebel Tools Configuration Details: hierarchy storage (Denormalized) BC Name Table Name Class Dynamic Hierarchy S_DYN_HRCHY CSSBCDynHierBase Dynamic Hierarchy Relationship S_DYN_HRCHY_REL CSSBCDynHierarchy Dynamic Hierarchy Reporting S_DYNHR_RPT_REL CSSBCBase Relationship Dynamic Hierarchy Parent S_DYN_HRCHY_REL CSSBCDynHierarchy Account Dynamic Hierarchy Direct S_DYN_HRCHY_REL CSSBCDynHierarchy Relationship

The above BCs are used while creating hierarchies. To view account data on hierarchy list, refer BC names starting with Global Account* *****