Change Profit Centre Replication Status as Bulk

To update status information about cost center replication requests.

Technical Data

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

Business Context and Use

Master Data Governance for Financials (MDGF) provides a central place to maintain the master data used in financial processes and provides consistent data throughout the enterprise. It is designed to eliminate manual distribution of financial master data and facilitates regulatory compliance by enabling time-dependent versioning of master data and system integrated change and approval processes.

MDGF uses asynchronous SOA services for the distribution of approved master data changes. For data replication from MDGF, a corresponding replication request service is called to update master data.

In the remote systems, another confirmation service is then used to send a processing status back to MDGF.

The Change Profit Centre Replication Status as Bulk service operation returns a processing status to MDGF from a remote Fnancial Accounting back-end system.

Features

This inbound service operation processes bulk confirmation messages that are sent back from Financial Accounting back-end systems to FIN-MDM for corresponding master data replication bulk messages after the processing.
In the first step, the fields of the message data type proxy - that is, DDIC-structure MDGF_PRFT_CTR_RPLCTN_CONF_MSG - 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. A processing status for corresponding replication request messages is derived from the processing result status element which is part of each included single message.
These status entries will be 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 the back-end systems.
The sender system (= receiver system of the corresponding replication request message) is included in the header data of the confirmation message.

Error Handling

In case of any errors during inbound processing, messages are added to the corresponding outbound distribution log for later analysis. Such a log is always available in the distribution monitor of FIN MDM and can be analyzed there.

Message Types

Profit Centre Replication Bulk Confirmation

Prerequisites

SOAMANAGER configuration has been completed and is working.

Notes on SAP Implementation

Enhancements

The USMD_SE_PC_RPLCTN Business Add-In (BAdI) is available for this operation. It is used to redefine standard mappings or for customer enhancements during inbound processing. The relevant interface method is called IF_EX_USMD_PC_RPLCTN~INBOUND_PROCESSING.