SAP MDG · COMMUNITY

How do I design Customizing synchronization between ERP and SAP MDG?

Design the synchronization by first choosing the MDG deployment model, then deciding which Customizing areas must be identical, classifying the Customizing by type, defining source/target roles per category, and finally applying a filter → export → import → activate → transport process with either manual or automated ongoing synchronization.

Design the synchronization by first choosing the MDG deployment model, then deciding which Customizing areas must be identical, classifying the Customizing by type, defining source/target roles per category, and finally applying a filter → export → import → activate → transport process with either manual or automated ongoing synchronization.

The presentation frames ERP–MDG Customizing synchronization around the deployment model, the requirement for identical Customizing where needed, and two core design questions: which Customizing data must be transferred, and how it will be transferred and kept synchronized.

It then recommends classifying Customizing into reference data, project-specific IMG Customizing, master-data-related Customizing, and MDG Customizing, before deriving the relevant object list and assigning source/target roles per category.

Process flow

  1. Choose the MDG deployment model: standalone hub or co-deployment.
  2. Identify the systems participating in master-data governance and replication.
  3. Decide which Customizing areas must be identical.
  4. Classify the Customizing into reference data, project-specific IMG Customizing, master-data-related Customizing, and MDG Customizing.
  5. Build the relevant Customizing object list.
  6. Define the source and target system for each Customizing category.
  7. Maintain each Customizing setting once where possible.
  8. Filter the Customizing to the relevant synchronization scope.\nExport the selected settings.\nImport them into the target.\nActivate the target settings.\nWrite target settings into a transport request.\nTransport changes through the DQP or

No detailed SPRO path is provided in the retrieved source; the presentation only names IMG-based Customizing, BC Sets, ALE Customizing Distribution, Customizing Synchronization, ChaRM, Retrofit, and SAP Solution Manager as tool options.

Use the presentation's listed tool options to design the synchronization approach. Verify the exact implementation path in your SAP release.

Referenced tables

ObjectPurpose
— The retrieved source does not name specific tables for this topic. It only states that the relevant Customizing object list should be derived from the required Customizing categories.

The remaining configuration, implementation details, and testing guidance continue from this answer more…

Related questions and keywords

Alternative questions

  • What MDG deployment options are relevant for Customizing synchronization?
  • Can SAP MDG be deployed as a standalone hub or co-deployed with S/4HANA/ECC?
  • Why does MDG deployment affect Customizing synchronization?

Possible questions

  • Does Customizing have to be identical between MDG and ERP?
  • What is the basic assumption for Customizing transfer?
  • What are the two main questions when designing MDG Customizing synchronization?
  • What types of Customizing data should be considered?
  • Which categories of Customizing are relevant for MDG synchronization?
  • How do I decide which Customizing tables to synchronize?
  • What is the purpose of the Customizing object list?
  • How do I define source and target systems for Customizing synchronization?
  • Can different Customizing types have different sender systems?

Keywords

SAP MDGSAP S/4HANASAP ECCstandalone hubco-deploymentmaster data hubdeploymentidentical customizingCustomizing transfermaster data replicationvalue mappingcustomizing scopesynchronization methodobject listtransferreference dataISO codesproject-specific customizingIMGmaster-data-related customizing