SAP MDG · COMMUNITY
How do I configure an SAP MDG Central Governance system as an Application Data Owner in Classic Mode (ADOCM) for federated processes?
Use this guide to configure an SAP MDG Central Governance system as an Application Data Owner in Classic Mode for federated processes. The CDO must run on SAP S/4HANA 2023 FPS01 or higher, while the classic-mode ADO 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 for federated processes. The CDO must run on SAP S/4HANA 2023 FPS01 or higher, while the classic-mode ADO 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 core sequence is: complete the Federation prerequisite, create inbound Change Request types in MDGIMG, set CR step properties, configure DRF technical settings in DRFIMG, then implement the federation-related BAdIs and implicit enhancements.
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`.','Enhance `CL_MDG_BP_2_STAGING` method `IF_MDG_BP_2_STA~GET_DEFAULT_CR_TYPE`.','Enhance `CL_MDG_BP_BUPA_SI_IN` method `GET_OBJECT_KEY`.','Replace example placeholders with customer-specific Business Flow
MDGIMGMaster Data Governance, Central Governance -> General Settings -> Process Modeling -> Change Requests -> Create Change Request Type
Create inbound Change Request types for federation processing in the ADO system.
MDGIMGMaster Data Governance, Central Governance -> General Settings -> Process Modeling -> Change Requests -> Configure Properties of Change Request Step
Set step 00 checks, required-field behavior, and entity ownership visibility for the Change Request.
DRFIMGDefine Custom Settings for Data Replication -> Define Technical Settings -> Define Technical Settings for Business Systems
Maintain the CDO business system, BP Type 147, communication channel, key harmonization, and storage behavior.
DRFIMGDefine Custom Settings for Data Replication -> Define Replication Models
Assign the Core Data Owner business system to the BP/BPRel via SOA replication model.
Referenced tables
| Object | Purpose |
|---|---|
mdg_fnd_bus_doc_msg_header | Stored single-message header structure used to retain federation BusinessScope data in the inbound BAdI. |
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?
- Where do I create inbound CR types?
- What is the MDGIMG path?
- Why are special Change Request types required?
- What must be configured before ADOCM enhancements?
- Which federation configuration comes first?