SAP MDG · COMMUNITY
How do I mass maintain SAP MDG value mapping using file export and import?
Use SAP MDG value mapping to map internal customizing codes to external code lists, then mass-maintain the mappings by exporting the current mapping to XML, editing it, importing it back, and verifying the result in MDGIMG. The guide applies from MDG 7.0 and SAP S/4HANA 1511.
Use SAP MDG value mapping to map internal customizing codes to external code lists, then mass-maintain the mappings by exporting the current mapping to XML, editing it, importing it back, and verifying the result in MDGIMG. The guide applies from MDG 7.0 and SAP S/4HANA 1511.
This guide explains how to mass maintain SAP MDG value mapping/customizing mapping using file export and import. It covers the concept of internal and external code values, the MDGIMG path to Maintain Value Mapping, the business and technical prerequisites, and the end-to-end export-to-XML and import flow for the material industry sector example (MARA-MBRSH).
Process flow
- Confirm the code values and agree the mappings with business users.
- Decide whether a global code list or system-specific code list is required.
- Check target-system support, service communications, custom fields, and client dependency.
- Open MDGIMG and navigate to General Settings > Value Mapping > Maintain Value Mapping.
- Find Object Type TABL (Structure) and Global Data Type MDG_BS_MATERIAL_INDUSTRIAL_SE1.
- Create or confirm Mapping ID 1 and the related list identifiers.
- Maintain the initial internal-to-external mappings and save.
- Export the mapping with MDG_EXTR_FPM_CMP as XML to a local file system using a saved variant such as ZIND_SEC. Edit the XML and add or change the required CodeMapping entries. Import the XML with MDG_FILE_UPLOAD_CMP using the required value
MDGIMGCross-Application Components > Master Data Governance > Central Governance > General Settings > Value Mapping > Maintain Value Mapping
Maintain and verify SAP MDG value mapping relationships
Master Data and Customizing File Export
Export existing value mapping to XML
Master Data File Import
Import edited value-mapping XML
PFCGRole SAP_MDGS_MENU_04 > Menu > Supplier Governance > Data Exchange > Load Data (File-Based) > Export Master Data / Import Master Data
Check or expose the standard launch points for export and import applications
Referenced tables
| Object | Purpose |
|---|---|
MARA-MBRSH | Example business field used in the guide: Material Industry Sector |
MDG_BS_MATERIAL_INDUSTRIAL_SE1 | Global Data Type and List ID used for the material industry sector example |
MDG_EXTR_FPM_CMP / MDG_FILE_UPLOAD_CMP | Web Dynpro applications used for export and import of value mapping |
ILLUSTRATIVE ABAP SAMPLE
Example XML code mapping block from the guide
The guide shows this as the XML payload pattern to add during mass maintenance. Use the exported XML from your own system as the authoritative baseline.
1<CodeMapping>
2 <InternalCode>1P</InternalCode>
3 <ExternalCode>005</ExternalCode>
4 <InMapDefault>/</InMapDefault>
5 <OutMapDefault>/</OutMapDefault>
6</CodeMapping>The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is this guide about?
- How do I mass maintain value mapping using files?
- Which releases support this process?
Possible questions
- What is value mapping in SAP MDG?
- Why do I need value mapping?
- What is mapped to an external code list?
- Where is Maintain Value Mapping in IMG?
- What is the MDGIMG path for value mapping?
- What must business users agree before value mapping?
- What should be known before creating mappings?
- What technical decisions are needed before value mapping?
- What about custom fields and client dependency?