SAP MDG · COMMUNITY
How should I use the Object List for Customizing Synchronization in an MDG project?
Use the guide as a template, not a final mandatory list. Build a project-specific synchronization list by matching the supplied MDG Finance, BP/C/S and Material Customizing objects to the governed entities and levels, then add missing dependencies, remove irrelevant entries, restrict values where needed, and validate the result before synchronizing between the MDG hub and client systems.
Use the guide as a template, not a final mandatory list. Build a project-specific synchronization list by matching the supplied MDG Finance, BP/C/S and Material Customizing objects to the governed entities and levels, then add missing dependencies, remove irrelevant entries, restrict values where needed, and validate the result before synchronizing between the MDG hub and client systems.
Use the guide as a template for identifying Customizing tables that may need synchronization between the MDG hub and client systems. SAP notes that the supplied lists are not universally complete or mandatory, so the project-specific list should be built by comparing the tables with the actual governed entities and Material levels, then removing irrelevant objects, adding missing dependencies, and restricting values where only part of the Customizing is governed.
Process flow
- Identify the MDG domains in scope: Finance, Business Partner/Customer/Supplier, Material, or a combination.
- Start with the corresponding object list from the guide.
- Compare each object with the governed entities, fields, and Material levels.
- Remove irrelevant objects.
- Add project-specific dependencies not contained in the template.
- Restrict table values where only selected values are governed.
- Validate the final list with functional and technical owners before synchronization.
- Synchronize the selected Customizing between the MDG hub and client systems.
Guide usage: treat the supplied object lists as a template for project-specific Customizing synchronization
Define the synchronization scope based on governed MDG domains, entities, and Material levels.
MDG governance context: CR-based, workflow-driven processing with staging, approval, activation, and distribution
Ensure Customizing is aligned so governed master data behaves consistently across hub and client systems.
Referenced tables
| Object | Purpose |
|---|---|
BNKA | Bank master record for MDG Finance `ACCCCDET` |
T001 | Company Codes for MDG Finance `ACCCCDET` |
T004F | Field status definition groups for MDG Finance `ACCCCDET` |
T007A | Tax Keys for MDG Finance `ACCCCDET` |
T002 | Language Keys for MDG Finance `ACCCCDET` |
TCURC | Currency Codes for MDG Finance `ACCCCDET` |
TB004/TB004T | Business Partner Type for `BP_CENTRL` / `BPKIND` |
TB001/TB002 | Business Partner Grouping for `BP_HEADER` / `BU_GROUP` |
T005/T005T | Country Key for `AD_POSTAL` / `REF_POSTA` |
T604 | Commodity Code / Import Code Number for Material Plant / Foreign Trade |
T685A | Condition Types for Material General level |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is the Object List for Customizing Synchronization guide used for?
- Does SAP provide a final mandatory Customizing object list?
- Why does MDG need synchronized Customizing?
Possible questions
- How do I create a project-specific Customizing synchronization list?
- How can I reduce the MDG-M Customizing object list?
- What is the Level column used for in the Material list?
- Which Customizing tables are relevant for Account and Company Code Customizing?
- Which Finance entity types depend on these Customizing objects?
- Which Customizing tables are relevant for Currency, Language and General Reference Customizing?