6.3.1.1.6.2.1 Debit/Credit Definition Pane

The Debit/Credit Definition pane allows you to input the Output Table and/or the Output column.

• When Output is Management Ledger-level: When posting Allocation Results to the Management Ledger-level, the Profitability Management Allocation Engine generates a balanced accounting transaction consisting of multiple debits and credits. One debit or credit is generated, or you may generate thousands of debits and credits.

  Note:

  When the output table is Management Ledger, Hierarchy Node Members can be selected in Output [Debit and Credit] tabs only for Static Driver and Dynamic Driver Allocation Types. Other allocation Types do not support Hierarchy Node Member Selection in Output.

• Figure 6-35 Debit Definition pane when Output table is Management Ledger

  
  

  

  
  
• When the Output Table is Instrument Level: When using an Allocation Rule to update an Instrument or Transaction Summary Table, the Profitability Management Allocation Engine updates your chosen output column for each Instrument-Level Account found in your Source and for which a matching Driver is found. When the output is generated to the Instrument or Transaction Summary Tables, you may choose to either Replace or Increment your Target Column Values. The default behavior for Allocation Rules built is Replace.

  Figure 6-36 Debit Definition pane when Output table is Instrument

  
  

  

  
  

Determining the Target side

With rules of the Static Driver Table type and the Dynamic Driver type, the user encounters a radio button with the question "Apply Static Table Driver to". There are two options available - Debit or Credit, the default being 'Debit' selected. User can change the value as required to either of 'Debit' or 'Credit'.

The Target side is the side of the output that consumes the driver. The other side of the output (if not suppressed) is generally the Offset side.

When the value of this radio button is set as 'Debit', the UI considers the Debit side to be the Target side that consumes the driver. Similarly, when the value is set as 'Credit', the UI considers the Credit side to be the Target side.

When 'Debit' is selected, user cannot apply 'No Debit'. Similarly, when 'Credit' is set, user cannot apply 'No Credit’.

As soon as the Target is determined, for Dynamic Driver type of rules, the macros <Match Source & Driver> and <Same as Driver> are available to be used as dimension constraints only for the Target definition. The <Same as Source> macro is avialble to be used both in the Target definition and in the Offset definition.

For Static Table Driver types, as soon as the Target is determined, the Target side auto-applies the Static Table Driver. This means:

1. the Key only dimensions are set with <Match Key> macro and gets disabled for user input,
2. the Target only dimensions are set with <Match Target> macro and gets disabled for user input,
3. the dimensions that are common to both Key and Target are set with <Match Key & Target> macro and gets disabled for user input.

The user can set any dimension other than the Key and the Target dimensions that remain enabled for user input. The <Same as Source> macro is avialble to be used both in the Target definition and in the Offset definition.

Output Table and Output Column Specification

To specify the output table and column for the Allocation Rule, use the following rules:

• You may only output to < Current Amount > when posting allocation results to the Management Ledger-level.
• For Constant and Leaf type rules, you may only output to the Management Ledger-level.
• For Field type rules, you may only output to an Instrument or Transaction Summary Table.