Siebel Analytics Installation and Configuration Guide > Siebel Industry Applications Analytics Metadata > Metadata Requirements for Siebel Life Sciences Analytics Applications >

Configuring Dimensions Common to All Subject Areas

These dimensions are used in all subject areas:

Positions Dimension

A sales territory is defined in Group Administration-Positions by a Siebel position. Creating parent positions creates the sales force hierarchy. Up to 10 levels of sales force hierarchy are supported by the application. Employees should be assigned to positions to populate employee hierarchy.

Position Types need to be set up according to compensation type (Rx or sales) only at the sales territory level. A district manager does not need to have a Position Type assigned to it. Sales Allocation needs to be exposed on the list applet to enter script compensation percentages (Rx or Sales) associated with each territory. For example, if all sales representatives receive 100% of the Rx on a ZIP Code, no action is needed or Position Type = Sales Representative can be assigned to the position.

Seed data on the Position Type list of values has been enhanced to include types for mirror, job share, and swat. Typically, both mirror and job share represent a position that receives less than 100% of the total scripts on a ZIP Code.

Alignments Dimension

A sales territory alignment is the relationship of ZIP Code-to-territory or brick-to-territory. The alignment relationship is created in Siebel Assignment Manager under Assignment Administration-Territories, as shown in Table 34.

Table 34.  Sales Territory Alignment
Relationship
Criteria
Comments
Contact ZIP to Territory
Contact ZIP Code
Use contact primary address ZIP Codes. Do not use ranges of ZIP Codes (that is, enter unique ZIP Codes as low and high values).
Do not enter duplicate ZIP Codes.
Account ZIP to Territory
Account ZIP Code
Do not use ranges of ZIP Codes (that is, enter unique ZIP Codes as low and high values).
Do not enter duplicate ZIP Codes.
Contact Brick to Territory
Contact Brick
Use contact primary address brick. Do not use ranges of bricks (that is, enter unique bricks as low and high values).
Do not enter duplicate ZIP Codes.
Account Brick to Territory
Account Brick
Do not use ranges of bricks (that is, enter unique bricks as low and high values).
Do not enter duplicate ZIP Codes.
Account to Territory
Account
Do not enter duplicate accounts.
Contact to Territory
Contact
Do not enter duplicate contacts.

Products Dimension

The product hierarchy requires customer products (products of the company who licensed the software) to have predefined product types as shown in Table 35.

Table 35.  Customer Products Predefined Product Types
Product Level
Product Type
Example
3
Sample
Aracid 400 MG
2
Detail
Aracid
No Level
Sub Market
COPD
1
Market
Asthma

NOTE:  Competitive products should use the product type Competitor. Competitor product hierarchies are set up using parent product relationships exclusively and should not have product levels assigned to them.

Product Costs Dimension

Product costs for customer products (that is, products of the company that licensed the software) require population in the Product Administration, Product Form Applet, as shown in Table 36.

Table 36.  Product Costs For Customer Products
Product Type
Field to be Populated
Sample
Sample Cost
Detail
Avg. Promo Cost
Promotional Item Cost
Sample Cost

 Siebel Analytics Installation and Configuration Guide, Version 7.7, Rev. A 
 Published: 11 March 2004