1. Accounting Foundation Cloud Service Core Functions
  2. Registering Accounting Content with your ERP Service
  3. Segment Mapping

11.6 Segment Mapping

You can map segment codes employed in your ERP Financials Cloud Service's Chart of Accounts to dimensions in AFCS. This information has 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.

You can configure ledger-wise segment mapping, Journal Ingestion and GL Ingestion.

To begin with, first extend the required CoA or ML segments and then perform segment mapping for the required ledgers. Ledgers available in ERP are available to choose from for mapping segments.

In case of tenants upgraded from AFCS 23.08.01, the Segment Mapping window displays the seeded dimension names, which are a part of the data model, and it is possible to map CoA segments to dimensions as required.

The following is a list of predefined dimensions which must be mapped to CoA segments:
  • 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
  • Ledger Identifier

    Note:

    The predefined dimensions such as Project Code, Counterparty, Ledger Identifier, and Intercompany Identifier are applicable only for General Ledger to Management Ledger type configuration.

    Note:

    The predefined dimension Account is applicable only for Management Ledger to Product Processor type configuration.

Note:

If you are creating new extensions post the 23.7.1 upgrade and want to use them in the GL Recon, and BCE reports, reach out to the customer support team.

In case of an upgrade to AFCS 23 C, the existing segment mappings are tagged to a seeded ledger named Default. The Default ledger mappings are used for ledgers whose segment mappings are not configured.

After the newly defined ledger-wise segment mappings are saved, Ingestion connectors (which help ingest journal entries and GL balances) are created. In addition, GL Balance pipeline and ERP Journal Ingestion pipelines are updated accordingly.