Show TOC

 Request Chart of Accounts Replication V1

 

To request replication of Chart of Accounts master data from FIN-MDM into a connected Financial Accounting or Financial Consolidation backend system.

Technical Data

Entity Type

Service Operation

Software Component Version

MDG_FND

Release State

released

Technical Name

ChartOfAccountsReplicationRequest_Out_V1

Namespace

http://sap.com/xi/FIN/MDG/Global2

Application Component

CA-MDG-APP-FIN

Category

SAP A2A

Direction

outbound

Mode

asynchronous

Idempotency

not applicable

Change/Update Behavior

not applicable

P2P Communication Enabled

yes

Business Context and Use

This service operation is used for asynchronous replication of Chart of Accounts master data from FIN-MDM into a connected Financial Accounting (FI-GL) or Financial Consolidation backend system (e.g. SEM-BCS, CPM-BPC).

Related Operations

Replicate Chart of Accounts  is the corresponding asynchronous inbound service operation in the backend systems that performs inbound processing of the replication requests created and sent by this service operation.

Features

  • This service operation reads Chart of Accounts master data from the relevant editions in FIN-MDM and maps the generic FIN-MDM data fields to the fixed fields of the relevant message data type proxy (i.e. DDIC-structure USMD_COA_REPLCTN_REQUEST_V1 and its sub-structures).

  • SOA messages are then created and sent (via PI) to the connected backend systems (e.g. FI-GL, SEM-BCS, CPM-BPC). The service operation creates one replication request message for each chart of accounts or financial statement item catalogue with data included in the relevant FIN-MDM editions.

  • For the mappings of the data model fields in FIN-MDM to the fixed fields of the message data  type it is recommended to use SMT Mappings. The data model generation in FIN-MDM generates DDIC structures automatically with naming convention "/1MD/<client>_<data model>_<entity type>" for each entity type to be used as a source structure in the SMT mapping definitions, while the substructures of message data type USMD_COA_REPLCTN_REQUEST_V1 generally represent the target structures.

  • For further processing of the message data the following prerequisites must be fulfilled:

    • The CategoryCode attribute of the message type has to be set accordingly during outbound processing:

      • CategoryCode = “1”: Distribution into Financial Accounting

      • CategoryCode = “2”: Distribution into Financial Consolidation.

    • In case of distribution into SEM-BCS, the FinancialConsolidationArea attribute for the consolidation area has to be set to a valid value that already exists in the relevant SEM-BCS backend system(s).

Message Types

  • ChartOfAccountsReplicationRequest_V1

Prerequisites

Customizing for data distribution has been maintained and is complete in FIN-MDM:

  • SMT Mappings are available and/or relevant BAdI-methods are implemented.

  • Distribution service is defined in FIN-MDM.

  • Master data package is defined in FIN-MDM.

  • Assignment to target system is done in FIN-MDM.

  • Edition with COA data in FIN-MDM has been released for distribution.

Constraints

The following restrictions apply to the message data types relevant for this service operation:

  • The length of a COA name is restricted to 4 characters.

  • The length of an account/ FS item is restricted to 10 characters.

If the lengths required exceed these restrictions, it is necessary to define specific mappings (on the outbound and on the inbound side).

Notes on SAP Implementation

Configuration

You have activated the MDG_FINANCIALS_3 business function (transaction SFW5) and maintained all necessary customizing in the backend systems. FIN-MDM services do not replicate any customizing data, so the required customizing has to be completed in the tartet system(s) before this service operation is used.

Enhancements

The Business Add-In (BAdI) USMD_SE_COA_RPLCTN is available for this operation (BAdI interface method IF_EX_USMD_COA_RPLCTN~OUTBOUND_PROCESSING).In case of delta distribution into SEM-BCS, this BAdI can be used to provide the consolidation area .

The BAdI can be used, for example, to modify or enhance the SMT field mappings, or even to define the complete data field mappings to be used instead of the SMT mappings.