Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG (Application Component) Master Data Governance⤷
MDG_BS_COMMON_OBJECTS (Package) MDG: Common Objects (IMG, Switches, Roles, ...)
IMG Activity
| ID | USMD_SE_CP_RPLCTN1 | BAdI: Replicate Company |
| Transaction Code | S_E7B_95000018 | (empty) |
| Created on | 20120827 | |
| Customizing Attributes | USMD_SE_CP_RPLCTN1 | BAdI: Replicate Company |
| Customizing Activity | USMD_SE_CP_RPLCTN1 | BAdI: Replicate Company |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | USMD_SE_CP_RPLCTN |
Use
This Business Add-In (BAdI) is used in the MDG Financials (CA-MDG-APP-FIN) component. You can use this BAdI to change or enhance data that is transferred via service interface CompanyReplicationBulkRequest_Out(method OUTBOUND_PROCESSING) or CompanyReplicationBulkConfirmation_In (method INBOUND_PROCESSING).
Both methods, OUTBOUND_PROCESSING and INBOUND_PROCESSING, have the following parameters, respectively:
OUTBOUND_PROCESSING (prior to sending a replication message):
I_EDITION_TO To-edition
I_EDITION_FROM From-edition
IT_ENTITY_MAPPING Entities and related SMT maps
I_DIS_SYSTEM Target system for distribution
I_APPL Application of the Data Replication Framework (DRF)
I_STEPNR Distribution step
IT_SEL Selection condition (currently not supported)
IF_DELTA Indicator for delta replication: Only changes are distributed
IT_DATA Selected dataset
C_SERVICE_GROUP Service group
CT_MESSAGE Message table
CS_PROXY_DATA Data for subsequent proxy call (message)
INBOUND_PROCESSING(after receipt of a confirmation message):
IS_PROXY_DATA Data for proxy call
CT_MESSAGE Message table
CS_DATA Structure for subsequent inbound processing of confirmation message
Standard settings
In the standard system, there is no activated BAdI implementation.
The BAdI is not filter-dependent.
The BAdI is designed for multiple use. All active implementations are called and executed.
BAdI implementation:
USMD_SE_CP_RPLCTN_EX
The BAdI implementation USMD_SE_CP_RPLCTN_EX serves as an example implementation and a template to demonstrate the access to the data to be processed prior to, or after, the proxy call. In an active BAdI implementation you also can redefine or extend the field assignments used by default.
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
See also
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20120827 |
| SAP Release Created in | 732 |
