1. User Guide
  2. GL to Management Reporting
  3. Maintaining the Mappers for GL to Management Reporting Result Table
  4. Possible Mapping Combinations
  5. Mapping Combinations at Parent Hierarchy Level by Removing one or more Descendants

29.4.2.4 Mapping Combinations at Parent Hierarchy Level by Removing one or more Descendants

This section explains about the mapping combinations for the General Ledger Code for Mgmt Reporting hierarchy at Parent level hierarchy by removing one or more Descendants (child members).

To map one parent GL Code to one or more Reporting Line Codes by removing one or more Descendants, use the Mapper Maintenance utility. In this utility, select one parent GL Code with one or more Descendants, select one member in the Debit Credit Indicator hierarchy with the value Debit or Credit or Missing, and select one or more members in the Reporting Line Code hierarchy. Then for the GL hierarchy, in the Macro column, select Self & Descendants and in the Excluded column, select either Yes to exclude or No to include the Descendants from mapping. As a result, during the T2T process, the corresponding data from the Stage GL Data table, for the selected parent GL Code and its descendants, is aggregated and then loaded into the Fact Management Reporting table.

Note:

In the T2T process, in the Stage GL Data table, the aggregation of parent GL Code and its descendants take 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 One Parent to One or Many Reporting Line Codes mapping by removing one or more GL Code Descendants, follow these steps:

  1. In the Mapper Maintenance page, in the Member combinations section, click Add.
  2. The Add Mappings page is displayed. For illustration, select one parent member of the General Ledger Code for Mgmt Reporting hierarchy GL-3000-27 – Brokerage Payable_144 and its child member (Descendant) GL-3000-28 – Corporate Debt Securities Liabilities_145, 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 10 – Equities - Listed with the member of the GL Rollup Signage for Mgmt Reporting hierarchy P - Positive Multiplier.

    Figure 29-26 Add Mappings page for the mapping combinations at parent hierarchy level by removing one or more Descendants


    This illustration shows the Add Mappings page for the mapping combinations at parent hierarchy level by removing one or more Descendants. Select the required codes.

  3. To map the members, click Go. The list of mapped members appear at the bottom. To exclude the Descendant of the GL Code from the mapping, in the Macro column, select Self & Descendants, and in the Excluded column, select Yes. To save the mappings, click Save.

    Figure 29-27 Map the members and save the mappings by excluding Descendants


    This illustration shows mapping the members and saving the mappings by excluding Descendants. Click Go to proceed with the mapping. To exclude the Descendants of the GL Code from the mapping, in the Macro column, select Self and Descendants. Then click Save to save the mappings.

  4. An acknowledgement message is displayed. To confirm saving the mappings, click Yes.
  5. The mapped member combinations are listed in the Mapper Maintenance page with the Macro value of GL Code as Self.

    Figure 29-28 Mapped member combinations are listed in the Mapper Maintenance page


    This illustration shows the mapped member combinations listed in the Mapper Maintenance page.