Creating Alternate Sales Force Hierarchies
Oracle Pharma Sales Analytics supports the ability to analyze Rx script data and compare it with alternate sales force organizational structures. These alternate sales force hierarchies can support co-marketing sales organizations where Rx scripts might be 100% allocated to both sales forces, as well as Mirror Sales Forces where Rx Script allocation might be shared between the Sales Forces.
You can assign scripts to each alternate sales representative by:
Using a report or metadata calculation based on the attribute of the W_POSITION_D dimension table
Creating a new set of aggregation tables to de-duplicate scripts
The alternate sales force hierarchies are configured as an additional set of positions and alignment rules within the Siebel Pharma application. This topic details the tasks that application administrators perform to configure these positions and alignment rules.
To create an alternate sales force hierarchy
Navigate to the Administration - Group screen, then the Positions view.
In the Positions list, create a new high-level position record in the Sales Force Hierarchy and complete the necessary fields.
Some fields are described in the following table.
Field Comments Division
Division for the alternate sales force hierarchy.
Position
Position associated with the alternate sales force hierarchy.
Position Type
Select the position type from the drop-down list.
For each of level that appears after the Sales Hierarchy, repeat Step 2 down to the Sales Territory level position.
In the Parent Position field for each record, select the Position for the level preceding the current Position.
The prebuilt Oracle Pharma Sales Analytics configuration supports the sales hierarchy levels described in the following table.
Level Description Cardinality to Parent Organization
The highest level of the sales organization that is sometimes referred to as Franchise. For example, Respiratory Franchise refers to a sales force commissioned to promote respiratory products. This level does not have any parents.
None
Sales Force
Child of Organization. Refers to a sales forces promoting products within a sales organization.
M:1
Area
Child of Sales Force. Refers to a large geographic sales area, such as US East, US West, or US South.
M:1
Region
Child of Area. Refers to a sales geographic region.
M:1
District
Child of Region. Refers to a sales geographic district.
M:1
Territory
Child of District. Refers to a sales geographic territory composed of ZIP codes, bricks, contacts, or accounts.
M:1
Create all levels for the sales hierarchy as positions, and link them to a position hierarchy to populate the Oracle Business Analytics Warehouse correctly.
For the territory level position in this new alternate hierarchy, set the Position Type field to either mirror, swat, or job share as appropriate for the alternate sales force.
Note: Select these position types for the territory level positions in the alternate sales force.In the new Owner Allocation field that has been exposed in the Position List Applet, enter the percentage allocation of scripts as a decimal for the alternate territory level position.
The Pharma Sales Analytics ETL populates the value from the Owner Allocation Percentage field to a column in the Position Dimension that can then be used to calculate measures and aggregates for Rx script allocations.
After the alternate sales force positions and hierarchy have been created, you must create an additional alignment rule for the alternate sales territory as an assignment rule.
For more information about creating these additional Assignment Rules, see Creating Sales Territories.
Note: The alternate sales force territory level position must be selected as the candidate position for these assignment rules.