SAP MDG · COMMUNITY
How do Cloud-Ready Mode and Classic Mode differ in SAP MDG, and how do I decide which mode to use?
Cloud-Ready Mode is the strategic MDG direction in the source for Business Partner governance: it is based on ABAP Cloud, CDS, RAP, and SAP Fiori, and uses a common MDG framework across Central Governance, Consolidation, and Data Quality Management. Classic Mode remains the broader established option with separate frameworks for Central Governance and CMP-based processing, plus wider domain coverage and custom-domain support.
Cloud-Ready Mode is the strategic MDG direction in the source for Business Partner governance: it is based on ABAP Cloud, CDS, RAP, and SAP Fiori, and uses a common MDG framework across Central Governance, Consolidation, and Data Quality Management. Classic Mode remains the broader established option with separate frameworks for Central Governance and CMP-based processing, plus wider domain coverage and custom-domain support.
Cloud-Ready Mode is the source’s strategic MDG direction for Business Partner governance. It uses ABAP Cloud, CDS, RAP, and SAP Fiori with a common MDG framework across Central Governance, Consolidation, and Data Quality Management. Classic Mode remains the established option with broader domain coverage and different frameworks, including WebDynpro for Central Governance and CMP-based processing for other areas.
Process flow
- Recognize Cloud-Ready Mode as ABAP Cloud/public-cloud-aligned and RAP-based.
- Use the common MDG framework/data model for Central Governance, Consolidation, and Data Quality Management.
- Treat Classic Mode as the established option with Change Requests for Central Governance and CMP Framework for Consolidation/Mass Processing/DQM.
- Use SAP Fiori-based UIs in Cloud-Ready Mode and WebDynpro for Central Governance in Classic Mode.
- Choose Business Partner scenarios for Cloud-Ready Mode; keep broader domains and custom domains in Classic Mode when needed.
Cloud-Ready Mode architecture: ABAP Cloud → CDS → RAP → SAP Fiori
Use for Business Partner governance when planning a cloud-aligned MDG implementation.
Classic Mode architecture: Change Requests for Central Governance; CMP Framework for Consolidation, Mass Processing, and DQM
Use when the scenario requires established Classic MDG processing and broader domain coverage.
Referenced tables
| Object | Purpose |
|---|---|
BUT000 | Business Partner central data segment referenced for Cloud-Ready coverage context. |
BUT020 | Business Partner addresses/usages segment referenced in the source. |
BUT021 | Business Partner address/usage-related segment referenced in the source. |
ADR2 | Business Partner address-dependent communication segment referenced in the source. |
ADR3 | Business Partner address-dependent communication segment referenced in the source. |
ADR6 | Business Partner address-dependent communication segment referenced in the source. |
ADR12 | Business Partner address-dependent communication segment referenced in the source. |
BUT100 | Business Partner roles segment referenced in the source. |
BUT0BK | Business Partner bank accounts segment referenced in the source. |
BUT0IS | Business Partner industries segment referenced in the source. |
BUT_DC_LNK | Business Partner data-controller assignment segment referenced in the source. |
BUT0ID | Business Partner identification numbers segment referenced in the source. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is this Cloud-Ready vs Classic Mode comparison about?
- Which SAP MDG releases support Cloud-Ready Mode?
- Does the comparison apply to Private Cloud and on-premise MDG?
Possible questions
- What is Cloud-Ready Mode in MDG?
- What technology is Cloud-Ready Mode based on?
- Which domain currently uses Cloud-Ready Mode?
- Does Cloud-Ready Mode use RAP and CDS?
- Which mode is strategic for future MDG deliveries?
- Which mode supports transition toward public cloud?