1. User Guide
  2. Business Rules Administration
  3. Application Specific Rules
  4. Static Table Driver
  5. Navigating in the Detail Screen

5.3.5.1 Navigating in the Detail Screen

When you Add, Edit, or View a Static Table Driver rule, the Static Table Driver Detail Screen is displayed.

In addition to Name, Description, Folder, and Access Type, the definition of a Static Table Driver includes Key Leaves, a Target Leaf, and coefficients values. After a Static Table Driver is defined and saved, you only edit an existing rule to update your driver coefficients (you cannot delete the Key and Target dimensions).

The Audit Trail pane is a standard footer pane for every OFSAA rule type. It displays Created By, Creation Date, Last Modified By, and Modification Date on the Audit Trail tab. The User Comments tab is used to add comments to any rule, subject to a maximum of 4000 characters.

Static Table Drivers are used in conjunction with Allocation rules for the following purposes:

  • To distribute balances at the Management Ledger level.
  • To perform a lookup table function against instrument tables.

Distribution with the Management Ledger-level

Static Driver Table Allocation rules that distribute balances at the management ledger-level function similarly to Dynamic Driver allocation rules.

  • Key Leaves function similarly to Dynamic Driver allocation rules that utilize < Match Source & Driver >
  • Target Leaves function similarly to Dynamic Driver allocation rules that utilize < Match Driver >

Instrument Level Update: Static Driver Table Allocation rules perform a lookup table function against an instrument table to match dimension values for each instrument row against the Key Leaf values you define in your Static Table Driver rule. When you find matching rows, the allocation performs an arithmetic operation combining source balance columns and a coefficient value you specify to update a result column.

Static Table Driver Pane

Specify the Static Table Driver rule's Name and Description, select a Folder in which the Static Table Driver rule is to be stored, and specify whether you want the Static Table Driver rule to be “Read/Write” or “Read Only” (Access Type). Naming your Static Table Driver rule is required before you can save it. Static Table Driver rule Name does not accept Special characters (&, @, ~, +, Single quote). Default values for Folder and Access Type are stored in Application Preferences for Profitability Management.

Static Table Driver Definition Pane

When creating a new Static Table Driver, first define its structure. After a Static Table Driver has been defined, the maintenance is usually limited to updating driver coefficients. The most critical aspects of a Static Table Driver's structural definition are as follows:

  • Key dimension
  • Key Leaf values for each Key Leaf
  • Target dimension
  • Target Leaf values for each Target Leaf
  • Defining Key Leaf values and Target Leaf values
  • Static Table Driver Coefficients
You do not need to specify both a Key Leaf and a Target Leaf, but you must specify at least one of them. That is, you should select a Key or Target dimension while defining a new Static Table rule.

Note:

You cannot add or delete the Key or Target dimensions after defining the Static Table Driver (edit mode). You can add or delete the dimension members.
  • Key Leaves: For both Management Ledger-level and Instrument allocations, Key Leaves perform a lookup function. Rows from the Source of the Allocation rule are joined with the Key Leaf values from the Static Table Driver. If an Input Row Leaf value matches a Key Leaf value for the first Key Leaf dimension specified in the Static Table Driver, the row is checked against the second Key Leaf values, and so on. If you find a match for every Key Leaf dimension, the row is processed by the Allocation rule. Profitability Management supports a maximum of three Key Leaf dimensions.
  • Target Leaf: You can use Target leaves only in allocations that distribute to the Management Ledger-level. You can view the Distribution allocations as first performing a lookup on one or more Key Leaves. When you find a match for each Key Leaf dimension, the matching input row's amount is distributed to all dimension values specified as Target Leaf values. This means that data is added to the Management Ledger for each dimension member value specified as a Target Leaf value. The leaf values specified in the Allocation rule's Debit use the < Same As Source > macro for all Key leaf dimensions and use the < Same As Table > macro for the Target Leaf dimension (very similar to the < Same as Driver > macro used in Dynamic Driver allocation rules).
  • Coefficients: You must specify coefficient values for every Static Table Driver rule. A part of the coefficient specification process is to enter the values for each distinct combination of each of your Key Leaves and Target Leaves. Where only Key Leaves are used, you must enter values for each distinct combination of each of your Key Leaves.
    • For Static Table Drivers with a Target Leaf Dimension: For a Static Table Driver that uses a Target Leaf dimension, you must supply one coefficient value for each distinct combination of each of your Key Leaves and your Target Leaves., Static Table Drivers that use a Target Leaf dimension are only supported for Management Ledger allocation rules.

      Target Leaf coefficient values represent distribution statistics. You would typically use these statistics on a Percent-to-Total basis. Static Table Drivers support both the Percent-to-Total method and the Simple method.

      Precede the definition of the Target Leaf dimension by the definition of one or more Key Leaf dimensions. Key Leaves are never required unless there is no Target Leaf defined. When Key Leaves are present, they operate as lookup keys as described above. For a Static Table Driver that uses a Target Leaf dimension, the Key leaves function analogously to the Dynamic Driver allocation function of < Match Source & Driver > and the Target Leaf functions analogously to the Dynamic Driver allocation function of < Match Driver >.

    • For Static Table Drivers with Key Leaf Dimensions But No Target Leaf: For Static Table Drivers that do not use a Target Leaf dimension, you must supply one coefficient value for each distinct combination of each of your Key Leaves. Static Table Drivers that use Key Leaves but do not use a Target Leaf can support both distributive Management Ledger allocation rules and Instrument level update rules.

      For an Instrument level update rule using a Static Table Driver, the Key Leaves function as lookup keys, and the coefficients function as arithmetic factors in updating a target column in an instrument table. For Management Ledger allocation rules, the Key Leaves function analogously to the Dynamic Driver allocation function of < Match Source & Driver >.