5.3.1.3.7 Examples of Leaf Allocations

Leaf Allocations only support the Management Ledger-to-Management Ledger use case. Leaf Allocations are used to compare a Source set of Management Ledger Balances to a Driver set of Management Ledger balances to create an Output set of Management Ledger Balances.

In this type of rule, the Allocation Engine attempts to match each Source row to a Driver row where the two rows share the same values for every Key Processing Dimension. For example, in an implementation in which there are seven Key Processing Dimensions, for each Source row, the Engine attempts to find a Driver row that matches the Source row in six dimensions, but which differs in one dimension. The one dimension in which Source and Driver rows must differ is the dimension chosen in the Driver as the “Leaf” dimension.

• Example 1: You divide a set of Management Ledger Transfer Pricing Charge/Credit balances (stored under Financial Element 450) by a set of Management Ledger Average Balances (stored under Financial Element 140) to generate a third set of Management Ledger Weighted Average Transfer Rates (stored under Financial Element 170). In this case, constrain your Source data to Financial Element 450; for your Driver, you specify Financial Element as your Leaf Dimension and you select Financial Element 140. For your output, choose a Financial Element of 170.
• Example 2: You subtract a set of “Aggregated Instrument Level Ending Balances” (stored under a user-defined Financial Element such as 10100) from a set of “original General Ledger ending balances” (stored under Financial Element 100) to generate a set of variances between your General Ledger data and your Instrument data. These variance records might be stored under a second user-defined Financial Element such as 20100.