The mapping combinations for the General Ledger Code for Mgmt Reporting hierarchy at child member level (individual nodes) are:
· One-to-One mapping with or without Debit Credit Indicator.
· Many-to-One mapping with or without Debit Credit Indicator.
· Many-to-Many mapping with or without Debit Credit Indicator.
The procedures for mapping combinations are:
To map one GL Code to one Reporting Line Code, use the Mapper Maintenance utility. In this utility, select one member in the General Ledger Code for Mgmt Reporting hierarchy, select one member in the Debit Credit Indicator hierarchy with the value Debit or Credit or Missing, and select one member in the Reporting Line Code hierarchy. As a result, during the T2T process, the corresponding data from the Stage GL Data table for the selected GL Code loads into the Fact Management Reporting table.
NOTE |
The conditions for the Debit Credit Indicator column values in the Stage GL Data table are: · The value must be M, when you map GL Code to the Missing (MSG) member. If nothing is mapped, the system automatically sets value to M. · The value must be D, when you map GL Code to the Debit member. · The value must be C, when you map GL Code to the Credit member. |
To perform One-to-One mapping with or without Debit Credit Indicator:
1. In the Mapper Maintenance page, in the Member combinations section, click Add.
2. The Add Mappings pop-up page appears. For illustration, select the member of the General Ledger Code for Mgmt Reporting hierarchy OTH - Others, and the member of the Debit Credit Indicator for Mgmt Reporting hierarchy D - Debit to map to the member of the Reporting Line Code for Mgmt Reporting hierarchy 100 - Corporate with the member of the GL Rollup Signage for Mgmt Reporting hierarchy P - Positive Multiplier.
3. To map the members, click Go. The list of mapped members appear at the bottom. To save the mappings, click Save.
4. An acknowledgement pop-up message appears. To confirm saving the mapping, click Yes.
5. The mapped member combinations are listed in the Mapper Maintenance page.
To map multiple GL Codes to one Reporting Line Code, use the Mapper Maintenance utility. In this utility, select two or more members in the General Ledger Code for Mgmt Reporting hierarchy, select one member in the Debit Credit Indicator hierarchy with the value Debit or Credit or Missing, and select one member in the Reporting Line Code hierarchy. As a result, during the T2T process, the corresponding data from the Stage GL Data table, for the selected GL Codes, are aggregated and then loaded into the Fact Management Reporting table.
NOTE |
In the T2T process, in the Stage GL Data table, the GL Code aggregation takes place in all the Measure columns that are associated with the Primary Keys. The conditions for the Debit Credit Indicator column values in the Stage GL Data table are: · The value must be M, when you map GL Code to the Missing (MSG) member. If nothing is mapped, the system automatically sets value to M. · The value must be D, when you map GL Code to the Debit member. · The value must be C, when you map GL Code to the Credit member. |
To perform Many-to-One mapping with or without Debit Credit Indicator:
1. In the Mapper Maintenance page, in the Member combinations section, click Add.
2. The Add Mappings pop-up page appears. For illustration, select the child members of the General Ledger Code for Mgmt Reporting hierarchy, GL-3000-26 – Asset-backed Securities Liabilities_143 and GL-3000-28 - Corporate Debt Securities Liabilities_145, and the member of the Debit Credit Indicator for Mgmt Reporting hierarchy, C - Credit to map to the Reporting Line Code hierarchy member 1002 - Redeemable Non Cumulative Preference Shares with the GL Rollup Signage hierarchy member P - Positive Multiplier.
3. 
4. To map the members, click Go. The list of mapped members appear at the bottom. To save the mappings, click Save.
5. An acknowledgement pop-up message appears. To confirm saving the mappings, click Yes.
6. The mapped member combinations are listed in the Mapper Maintenance page.
To map multiple GL Codes to multiple Reporting Line Codes, use the Mapper Maintenance utility. In this utility, select two or more members in the General Ledger Code for Mgmt Reporting hierarchy, select one member in the Debit Credit Indicator hierarchy with the value Debit or Credit or Missing, and select two or more members in the Reporting Line Code hierarchy. As a result, during the T2T process, the corresponding data from the Stage GL Data table, for the selected GL Codes, are aggregated and then loaded into the Fact Management Reporting table.
NOTE |
In the T2T process, in the Stage GL Data table, the GL Code aggregation takes place in all the Measure columns that are associated with the Primary Keys. The conditions for the Debit Credit Indicator column values in the Stage GL Data table are: · The value must be M, when you map GL Code to the Missing (MSG) member. If nothing is mapped, the system automatically sets value to M. · The value must be D, when you map GL Code to the Debit member. · The value must be C, when you map GL Code to the Credit member. |
To perform Many-to-Many mapping with or without Debit Credit Indicator:
1. In the Mapper Maintenance page, in the Member combinations section, click Add.
2. The Add Mappings pop-up page appears. For illustration, select the child members of the General Ledger Code for Mgmt Reporting hierarchy, GL-3000-24 – Intangible Assets_141 and GL-3000-29 – Derivative Contracts Liabilities_145, and the member of the Debit Credit Indicator for Mgmt Reporting hierarchy, D - Debit to map to the child members of the Reporting Line Code for Mgmt Reporting hierarchy, 1 - Total Assets and 10 - Equities Listed with the member of the GL Rollup Signage for Mgmt Reporting hierarchy, P - Positive Multiplier.
3. To map the members, click Go. The list of mapped members appear at the bottom. To save the mappings, click Save.
4. An acknowledgement pop-up message appears. To confirm saving the mappings, click Yes.
5. The mapped member combinations are listed in the Mapper Maintenance page.
