Change General Ledger Account Master Replication Status as Bulk

To perform inbound processing of a bulk confirmation message received in response to a G/L account replication request.

Technical Data

Entity Type	Service Operation
Software Component Version	FINBASIS 605
Release State	released
Technical Name	GeneralLedgerAccountMasterReplicationBulkConfirmation_In
Namespace	http://sap.com/xi/FINB/Global2
Application Component	CA-MDG-APP-FIN
Web Service Definition (Back End)	GENERALLEDGERACCOUNTMASTERREPL
Category	SAP A2A
Direction	inbound
Mode	asynchronous
Idempotency	not applicable
Change/Update Behavior	Type3
P2P Communication Enabled	yes

Business Context and Use

This service operation performs asynchronous inbound processing (in FIN-MDM) of a bulk confirmation message received from a remote Financial Accounting system in response to a corresponding bulk replication request message for G/L account master data. The confirmation message contains a list of confirmations indicating the processing result status of each of the replication requests contained in the original bulk request.

Related Operations

Confirm General Ledger Account Master Replication as Bulk is the corresponding asynchronous outbound service operation in the backend systems that sends the outbound bulk confirmation message received and processed by this service operation.

Features

This service operation processes confirmation messages that are sent back from Financial Accounting backend systems to FIN-MDM following the processing of corresponding bulk master data replication requests.
In the first step, the fields of the message data type proxy (DDIC structure USMD_GENERAL_LEDGER_ACCOUNT_MA) are mapped to corresponding fields of DDIC structure USMD_S_INBOUND_DATA which is used for further processing of the message content in FIN-MDM. This mapping is implemented directly in ABAP code. Mapping enhancements and modifications can be implemented using the related BAdI USMD_SE_GLAM_RPLCTN.
A processing status of a corresponding replication request message is derived from the processing result status element which is part of the message content. This status is then stored (updated) in specific status tables of FIN-MDM (USMD6500, USMD6510 and USMD6400 for distribution monitor) in order to keep track of the processing status of corresponding original replication request messages in those backend systems.
The sender system (= receiver system of the corresponding replication request message) is included in the header data of the confirmation message.

Message Types

GeneralLedgerAccountMasterReplicationBulkConfirmation

Notes on SAP Implementation

Configuration

You have implemented (activated) the FIN_MDM_ACC business function (transaction SFW5) and maintained all necessary customizing.

Enhancements

The Business Add-In (BAdI) USMD_SE_GLAM_RPLCTN is available for this operation (BAdI interface method IF_EX_USMD_GLAM_RPLCTN~INBOUND_PROCESSING).