1. User's Guide
  2. Working with Standard Profitability and Cost Management Applications
  3. Managing Standard Profitability Allocations
  4. Defining Drivers and Formulas for Standard Profitability Models
  5. Driver Formulas
  6. Custom Driver Formulas
  7. Custom Driver Formula Examples

Custom Driver Formula Examples

The custom driver formula examples assume the following values:

  • Stage 1 Dimensions: GL_ Department x GL_Account

  • Stage 2 Dimensions: ACT_Department x ACT_Activity

The calculation script generation process in Oracle Hyperion Profitability and Cost Management inserts the script defined for a custom driver for any source that uses this driver. The system-generated script creates the FIX statements to pinpoint the source and destination combinations defined by the assignment logic attached to the source.

The custom driver script need not provide this FIX, but it can take advantage of it, or modify the FIX to reference data from different locations that is normally defined for the Destination, Source, Assignment, or Global measure locations.

Common uses for custom drivers rely on the ability to reference data that is stored in locations other than the normal four, enabling the user to enter driver measures at higher levels in the hierarchy or at fewer intersections.

The default FIX statement that the CalculatedDriverValue measure computed reflects the link between source and destination. Using the example stages, the FIX created by the system-generated script is shown below:

GL_Department.member x GL_Account.member x ACT_Department.member x ACT_Activity.member

where the dimension members for each dimension reflect the source intersection and destination intersection for the allocation being performed.

The examples below modify this default FIX to retrieve driver measures from another location. Remember that if the member referenced by the default FIX is correct for the purposes you need not override it.

Example 1: Referencing a driver measure located at only one of the destination dimensions cross NoMember in the other (in this case ACT_Department)

"CalculatedDriverValue" = "DriverMeasure" ->"[ACT_Activity.NoMember] ->"[ GL_Department.NoMember] ->"[ GL_Account.NoMember];

Use this formula when there is a single driver value for the entire department; for example, square feet, meters, or headcount.

Example 2: Referencing a driver measure located at the parent of one of the destination dimensions cross NoMember in the other dimension:

"CalculatedDriverValue" = "DriverMeasure" ->"[ACT_Activity.NoMember]"->"(@PARENT(ACT_Department)" ->"[ GL_Department.NoMember] ->"[ GL_Account.NoMember];

Alternatively, you can reference the Generation of the ancestor from which you want to retrieve the value using @ANCSET function. In this example, the driver pulls the DriverMeasure value from the Generation 2 ancestor of the destination’s Department member:

"CalculatedDriverValue" = "DriverMeasure" ->"[ACT_Activity.NoMember]"->"(@ANCEST(ACT_Department, 2)" ->"[ GL_Department.NoMember] ->"[ GL_Account.NoMember];

Other common uses are to key the driver value calculation on the nature of the source/destination combination. This option enables the driver to adapt to specific circumstances based on characteristics of the intersections involved in the allocation.

Example 3: Referencing a different measure for driver calculation based on the UDA of one destination member:

IF(@ISUDA(Activity,"UDA1"))

"CalculatedDriverValue" = {Measure1->Destination};

ELSE IF (@ISUDA(Activity,"UDA2"))

"CalculatedDriverValue" = {Measure2->Destination};

ELSE IF (@ISUDA(Activity,"UDA3"))

"CalculatedDriverValue" = {Measure3->Destination};

ENDIF;

Use this formula to key the driver formula from a characteristic of the destination, such as product form factor or customer classification Note that the syntax in the example: ‘{Measure1->Destination}’ does not match usual Oracle Essbase calc Script syntax. The use of the curly brackets ({ }) enables Profitability and Cost Management to interpret the ‘->Destination’ shorthand, and to replace it with the actual destination being targeted. When the script is deployed to Essbase, Profitability inserts the correct member references and syntax.