1. User Guide
  2. Business Rules Administration
  3. Application Specific Rules
  4. Allocation Specification
  5. Detail Screen
  6. Outputs Process Tab
  7. Output Definition
  8. Specific Leaf Value versus <Same as Source> Macro

5.3.1.1.6.2.4 Specific Leaf Value versus <Same as Source> Macro

For Allocation Rules posting to the Management Ledger-level, <Same as Source> for a particular Dimension means that for that Dimension, the values found in Source records are passed directly to Output records. For example, you might want to allocate 100% of the expenses from one department to a second department. In your original General Ledger data, expenses for the Source Cost Center can be posted under hundreds of different General Ledger accounts. In this example, you might specify your Credit Output (expense allocation offset) as follows:

  • <Same as Source> for the Organizational Unit Dimension.
  • <Same as Source> for the General Ledger Account Dimension.

In this way, your Allocation Rule generates a credit to the original department for every original expense balance. If the Source Department contained balances under 81 different General Ledger Accounts, the Allocation Rule would generate 81 Credit Records.

Specify your Debit Output as:

  • Target Department (leaf value) for the Organizational Unit Dimension.
  • Allocated Expense (leaf value) for the General Ledger Account Dimension.

In this example, Allocated Expense is a user-defined General Ledger Account. Define this Dimension Member in a reserved range of accounts for use in your Profitability Management model. Note that only one debit row is created in this scenario.

Note:

When you choose to output to a specific Leaf Value, you may not output to a node value. The output generating to node values is not supported.

Other Output Macros: Other output macros include:

  • <Same as Driver>
  • <Match Source & Driver>
  • <Same as Table>
  • Constant Allocation Type: For Constant type Allocations, specify a target leaf value for each processing Dimension for both debit and credit. You may optionally suppress either the Debit or the Credit.
  • Static Driver Allocation Type: For Static Driver Allocations, choose either a specific Dimension Member Value or the <Same as Source> macro for each processing Dimension.
  • Leaf Allocation Type: For Leaf Allocations, choose either a specific Dimension Member value or the <Same as Source> macro for each processing Dimension.
  • Field Allocation Type: For Field Allocations, choose either a specific Dimension Member Value or the <Same as Source> macro for each processing Dimension.
  • Dynamic Driver Allocation Type: For Dynamic Driver Allocations, for each processing Dimensions choose either a specific Dimension member value or from the following:
    • <Same as Source>
    • <Same as Driver>
    • <Match Source & Driver>

At least one Dimension in either your Debit or Credit specification must be either <Same as Driver> or <Match Source & Driver>.

  • Same as Driver Macro: The <Same as Driver> macro is used when you want your outputs to inherit values from your Driver Data. For example, building an Allocation Rule to distribute some kind of processing expense to branches using “Number of Checks Processed per Branch” as your driver statistic set. In this example, your statistics “drive” your processing expense to branches, therefore, you must specify <Same as Driver> in the Organizational Unit Dimension of your Debit definition. Since this is an expense allocation, you might want to construct a Credit definition using <Same as Source> in every Dimension.
  • Match Source & Driver Macro: The <Match Source & Driver> macro is used when you want to distribute data to one Dimension while holding another Dimension constant. For example, you might want to build an Allocation Rule that allocates a Human Resource expense cost pool as a function of headcount, but that also allocates an Occupancy Expense cost pool as a function of square footage occupied. If your destinations are Cost Centers, then you can store your statistic sets – one for headcount and one for square footage – on a per Cost Center per Cost Pool basis. In this example, you would use <Match Source & Driver> on the Cost Pool dimension and <Same as Driver> on the Organizational Unit Dimension. This causes the rule engine to create two sets of Debits to Cost Centers:
    • Debits from the Human Resource expense Cost Pool using the headcount statistics.
    • Debits from the Occupancy expense Cost Pool using the square footage occupied statistics.
  • Static Driver Table Allocation Type: For Static Driver Table allocations, for each of the Processing Dimensions, choose either a specific Leaf Value or choose from the following:
    • <Same as Source>
    • <Same as Table>

    When you choose <Same as Table> for a Dimension, you indicate the Allocation Engine that the rule to inherit its destination Dimension Member values from the Static Table Driver.

  • Lookup Driver Table Allocation Type: For Lookup Driver Table Allocations, choose either a specific Leaf Value or the <Same as Source> macro for each processing Dimension.