CoA Segment Mapping

This interface allows you to map segment codes employed in your ERP Financials Cloud service Chart of Accounts to Dimensions in AFCS. This information is required to be configured once prior to initial ingestion of balance information from your ERP Financials Cloud Service into AFCS. Balance information is ingested into Staging entities General Ledger and Management Ledger, corresponding to GL and Supporting Reference Balance information using this mapping.

The Ledger Balance Data from the AHC appear in the form of CoA Segment Columns. The CoA Segments are defined differently for each CoA Structure Instance and therefore, there is an option to select the appropriate dimension for each segment.

The Subledger CoA Mapping window displays the seeded dimension names, which are a part of the data model, and it is possible to select dimensions against each COA segment as required.

The list of predefined dimensions required in the application and which are mapped to CoA segments are as follows:

·        General Ledger Account Code

·        Legal Entity Code

·        Branch Code

·        Product Code

·        Organization Unit Code

·        Party Identifier

·        Counterparty Reference Code

·        Intercompany Identifier

·        Acquisition Channel Code

·        Location Code

·        Line of Business Code

·        Business Unit Code

·        Project Code

Mapping Segments

Depending on the CoA or accounting principles followed, the AFCS predefined dimensions can be mapped with the list of CoA Segments.

To map the segments, follow these steps:

1.      Navigate to Subledger Application Summary Page.

2.     Click from Top-right corner and select Administration.  Select CoA Mapping option from LHS. The Subledger Chart of Account Map Window is displayed. The Attribute Column displays the list of predefined dimensions and the Chart Of Account Segment displays the CoA Segment Value with a drop-down list of CoA Segments 'COA Segment 1 , COA Segment 2, and so on.

3.     Select the NONE option when the dimension is not required to be mapped or used.

4.     Select the required CoA Segments and click Save.

5.     These segment values are replaced with the dimension columns as mapped in the inbound connector and the data is loaded as per the mapping into the staging tables of the ledger loaded as mapped into Data Foundation.

6.     After it is saved, the Insert Connectors automatically get mapped for GL.

NOTE:   

Specify the CoA Segment as the attributes in AFCS. For example, if you map the CoA Segment 1 to GL Code, all the extracts from AHCS with column header as CoA Segment 1 are loaded as GL Code in AFCS.

The predefined dimensions with * must be mapped to some of the other CoA Segments to get values, as they are not null columns.