16.9 Hierarchy Configuration for Reconciliation

Hierarchies are used in the User Interface and they allow you to select one or more member nodes or leaf nodes. A Hierarchy browser is a widget that needs data from a cache maintained in internal processing of the entities. A dimension data may change over a period of time, therefore the hierarchy cache must be refreshed to align with the latest dimension data. For this purpose, there is a PMF process available in the AFCS by the name ‘Hierarchy Resave’. This process can be executed to refresh the data of hierarchy. Once this step is done, then the Hierarchy Browser widgets start displaying the latest dimension members. The successful execution of PMF process indicates that the dimension data is refreshed in the internal cache. The Hierarchy Resave operation can be done multiple times for a date. It allows you to select more than one dimension hierarchies at once. You must re-save the Hierarchies and then proceed with the Run Pipeline execution.

• User Interface of Reconciliation uses hierarchies as mentioned in the page below. A Rule Configuration page uses Legal Entity and General Ledger hierarchies to render parent-child structures.
• Custom hierarchies are created for Reconciliation and the hierarchy codes are visible in the Hierarchy Management tab under Administration menu in the AFCS application. You can use this hierarchy code and perform data load activities in the dimension hierarchy entities. The Hierarchy Resave operation is common to the Out-of-the-Box Hierarchies and Custom Hierarchies. You must perform the data load for custom hierarchies in a way which is similar to the Out-of-the-Box hierarchies.
• Legal Entity and General Ledger Hierarchies are parent-child hierarchies for which the hierarchy needs to be loaded in the corresponding hierarchy table of the each of the dimension. The other hierarchies are all single level hierarchies being used in the filters of reconciliation rules.

Following are the seeded hierarchies and its corresponding mapping tables:

Table 16-6 Reconciliation Seeded Hierarchies and their corresponding Mapping Tables

Hierarchy Codes	Hierarchy Dimensions
HGL001	Product Dimension - Product for Reconciliation
HGL002	Business Unit Dimension - Business Unit for Reconciliation
HGL003	Branch Dimension - Branch for Reconciliation
HGL004	Counterparty Dimension - Counterparty for Reconciliation
HGL005	Currency Dimension - Currency for Reconciliation
HGL006	Organization Unit Dimension - Organization Unit for Reconciliation
HGL008	Legal Entity Hierarchy Dimension - Legal Entity for Reconciliation
HGL009	General Ledger Hierarchy Dimension - GL Code for Reconciliation
HGL012	Accounting Standard Dimension - Accounting Standard for Reconciliation
HGL014	Ledger Dimension - Ledger for Reconciliation
HGL015	Project Dimension - Project for Reconciliation
HGL020	Legal Entity Dimension - Intercompany for Reconciliation
HGL021	Account Dimension - Account for Reconciliation

To re-save the GL Hierarchies in Process Orchestration, follow these steps:

1. On the Home page, select Process Orchestration from the LHS menu. The Process Modeller page is displayed.
2. Create a pipeline GL Hierarchy Resave and select one or multiple of the above listed Hierarchy names in the Process Orchestration before re-saving them. To create a pipeline, follow these steps:
   1. On the Process Modeller Page, search for the created pipeline. The Process Flow Page is displayed. This Process Flow is designed on the Drawing Canvas using the Transition, Activity, and Widgets Components available in the floating toolbar. A HIERARCHYRESAVE Widget is added to the START for the purpose of resaving the Hierarchy.
   2. After the HIERARCHYRESAVE Widget is added in the Drawing Canvas, double-click the HIERACHYRESAVE Node, the HIERARCHYRESAVE window is displayed. Enter information in the Activity Desc field. Under Dynamic Parameters for HIERARCHYRESAVE fields, select the Entities, and then the corresponding Hierarchy names, and select Load Type as Resave. Click Tick mark icon to save the details.
3. To execute the Run, you can select the Run Parameter Values using the Execution Button on the Process Flow Page or on the Process Modeller Page.
4. Go to the Process Modeller Page to execute the Run. Click the Menu Button corresponding to the pipeline that needs to be executed. Click Execute Run. The Execution Page is displayed.
5. On the Execution Page, select the Execution Type as Without Parameters. Enter a unique value for the Object ID.
6. To save the details and execute the Run, click the Apply Button. The resaving process begins.

   Note:

   See the Process Orchestration Section for more details about the Processes.
7. To verify the Run Execution (GL Hierarchy Resave), do the following:
   1. To open the Process Monitor Page, on the Process Modeller Page, click the Process Monitor Button or select Process Flow Monitor on the Process Modeller Menu.
   2. The Process Monitor Page is displayed listing all the Run Instances corresponding to the GL Hierarchy Resave Processes. On the Process Monitor Page, search by the Process ID, or by the Process Name GL Hierarchy Resave, and select the Process Instance for the required Run Pipeline (GL Hierarchy Resave) that was executed.

      The Process Flow Page is displayed with the Run Execution Status on each Node of the GL Hierarchy Resave Process.

8. To verify the Run Execution Logs, do the following:
   1. On the Process Monitor Page, click the required Process Instance for which you need to verify the Execution Logs. The Process Flow Page is displayed with the Run Execution Status on each Node.
   2. To see the Execution Status details of a Node, double-click on that Node. The Execution Status details Page is displayed. Click Execution Logs. The Log Viewer Page is displayed, which lists all the Logs related to the Process Instance. To see the details of a log entry, click the Show More Button. Click outside the Log Viewer Page to close it.