SAP MDG · UTILITIES
How do I enable a system as an Application Data Owner in classic mode for federated processes in SAP MDG?
Use this guide to configure an SAP MDG Central Governance system as an Application Data Owner in Classic Mode (ADOCM) for federated processes. The CDO must run on SAP S/4HANA 2023 FPS01 or higher, while the ADO in classic mode can run on SAP S/4HANA 1809 or higher.
Use this guide to configure an SAP MDG Central Governance system as an Application Data Owner in Classic Mode (ADOCM) for federated processes. The CDO must run on SAP S/4HANA 2023 FPS01 or higher, while the ADO in classic mode can run on SAP S/4HANA 1809 or higher.
This guide explains how to configure an SAP MDG Central Governance system as an Application Data Owner in Classic Mode (ADOCM) for federated processes. The central release requirement is that the Core Data Owner runs on SAP S/4HANA 2023 FPS01 or higher, while the Application Data Owner in classic mode can run on SAP S/4HANA 1809 or higher. The implementation combines Federation customizing, Change Request setup, DRF technical settings, and BAdI/enhancement logic.
Process flow
- Complete the general Federation configuration.
- Create inbound Change Request types in the ADOCM system.
- Configure Change Request step properties.
- Configure inbound DRF technical settings.
- Add the CDO as an outbound DRF target.
- Implement BAdI `MDG_SE_BP_BULK_REPLRQ_IN`.
- Implement BAdI `MDG_SE_BP_BULK_REPLRQ_OUT` when client maintenance/outbound changes are required.
- Implement BAdI `MDG_BS_SUPPLIER_SI`.
MDGIMGMaster Data Governance, Central Governance -> General Settings -> Process Modeling -> Change Requests -> Create Change Request Type
Create the inbound Change Request types used by the classic-mode ADO for federated processing.
MDGIMGMaster Data Governance, Central Governance -> General Settings -> Process Modeling -> Change Requests -> Configure Properties of Change Request Step
Set step 00 checks, entity-type properties, and manual-processing behavior for inbound federation Change Requests.
DRFIMGDefine Custom Settings for Data Replication -> Define Technical Settings -> Define Technical Settings for Business Systems
Maintain the CDO business system and BP Type 147 technical settings for inbound federation replication.
DRFIMGDefine Custom Settings for Data Replication -> Define Replication Models
Add the CDO as an outbound target for the replication model used for BP and BPRel via SOA.
Referenced tables
| Object | Purpose |
|---|---|
mdg_fnd_bus_doc_msg_header | Stores the current single-message header for federation context in the inbound BAdI pattern. |
USMD1210 | Stores Change Request notes in the example ABAP utility pattern. |
USMD120C | Used in the example code to read Change Request type information from the data model. |
USMD1601 | Used in the example code to derive process and Change Request type context. |
cvi_vend_link | Used in the example code to map Business Partner to Vendor for specific supplier processes. |
BUT000 | Used in the example code to resolve Business Partner master data keys. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What does this guide explain?
- How do I enable an application data owner in classic mode?
- Which releases support CDO and ADO classic mode?
Possible questions
- What is the complete implementation order?
- Give me the high-level setup for ADOCM.
- What must be configured before ADOCM enhancements?
- Which federation configuration comes first?
- Where do I create inbound CR types?
- What is the MDGIMG path?
- Why are special Change Request types required?