SAP MDG · COMMUNITY
How to extend MDG-S / MDG-C with a new custom-defined field using the Reuse Option
Use the Reuse Option when the custom attribute already exists in the backend ERP/customer structures. Extend the active-area table/include, add the attribute to MDG data model BP in MDGIMG, regenerate MDG structures, maintain SMT mappings, then adjust linked change requests and UI/search settings as needed.
Use the Reuse Option when the custom attribute already exists in the backend ERP/customer structures. Extend the active-area table/include, add the attribute to MDG data model BP in MDGIMG, regenerate MDG structures, maintain SMT mappings, then adjust linked change requests and UI/search settings as needed.
This guide explains the MDG Reuse Option for Supplier/Customer master data: if the custom attribute already exists in the backend, you extend the active-area ERP structure and the MDG BP data model together, then regenerate the MDG structures and maintain the required SMT mapping. The exact path depends on whether the field exists in Business Partner only, Vendor/Customer only, or in both BP and Vendor/Customer.
Process flow
- Identify whether the field exists in Business Partner, Vendor/Customer, or both.
- Extend the relevant ERP/customer include structure in the active area.
- Open MDGIMG and add the field to data model BP and the correct entity.
- Save and activate the model change.
- Run Generate Data Model-Specific Structures if required.
- Maintain the relevant SMT mappings in both directions.
- Check mapping customizing for errors.
- Maintain UI field properties and search settings if the field should be exposed there in MDG UI/search scenarios. Adjust the staging area of linked change requests. If the field exists in both BP and Vendor/Customer, implement CVI custom
MDGIMGGeneral Settings → Data Modeling → Edit Data Model
Add the custom attribute to data model BP and the relevant entity such as BP_CENTRL
MDGIMGGeneral Settings → Data Modeling → Generate Data Model-Specific Structures
Regenerate the MDG structures after model changes
MDGIMGGeneral Settings → Data Modeling → Extend Mappings → Extend Mappings
Maintain SMT field mappings for BP staging and active-area structures
MDGIMGGeneral Settings → Data Modeling → Create and Edit Mappings → Check Customizing
Validate SMT mapping customizing for errors
MDGIMGGeneral Settings → UI Modeling → Define Field Properties for UI
Expose the custom BP field in the UI field catalog
MDGIMGGeneral Settings → Data Quality and Search → Search and Duplicate Check → Define Joins, Field Mapping, and Authorizations for Reuse Tables
Maintain field mapping for HANA-based search and duplicate check where needed
Referenced tables
| Object | Purpose |
|---|---|
BUT000 | Business Partner active-area table used in the BP-only example |
KNA1 | Customer general data table mentioned as a reuse-option active-area example |
KNB1 | Customer company-code data table mentioned as a reuse-option active-area example |
KNVV | Customer sales-area data table mentioned as a reuse-option active-area example |
LFA1 | Vendor general data table mentioned as a reuse-option active-area example |
LFB1 | Vendor company-code data table mentioned as a reuse-option active-area example |
LFM1 | Vendor purchasing-org data table mentioned as a reuse-option active-area example |
INCL_EEW_BUT000 | Customer include used to extend BUT000 |
INCL_EEW_BUT000_X | X-structure include used with BUT000 extension |
USMD_DATA_MODEL | Program used to inspect generated MDG data-model-specific structures |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is the MDG reuse option for custom fields?
- How do I extend MDG-S or MDG-C with an existing database field?
- What areas are affected when adding a custom attribute to MDG BP?
Possible questions
- What customer includes do I use for BUT000, KNA1, and LFA1?
- Which MDGIMG path adds a field to BP_CENTRL?
- Which SMT mappings are required for a BP-only custom field?
- When is CVI mapping required for an MDG custom field?
- How do I regenerate MDG structures after model changes?