SAP MDG · DATA MODEL UI
How do I extend SAP MDG-S / MDG-C Business Partner data model BP with a new custom-defined field using the Reuse Option?
Use the reuse option when the field already exists as a database field in BP, Customer, or Supplier structures: extend the backend include, add the attribute to data model BP in MDGIMG, generate the MDG structures, maintain SMT mapping, and adjust the staging area; if the field exists in both BP and Vendor/Customer, also implement CVI mapping.
Use the reuse option when the field already exists as a database field in BP, Customer, or Supplier structures: extend the backend include, add the attribute to data model BP in MDGIMG, generate the MDG structures, maintain SMT mapping, and adjust the staging area; if the field exists in both BP and Vendor/Customer, also implement CVI mapping.
The reuse option is the standard MDG-S/MDG-C approach when your custom attribute already exists as a backend database field. You extend the relevant customer include, add the attribute to data model BP in MDGIMG, generate or regenerate the MDG structures, define SMT mappings, and then adjust the staging area of linked change requests.
Process flow
- Identify whether the field exists in BP only, Vendor/Customer only, or both.
- Extend the relevant backend customer include such as `INCL_EEW_BUT000` for BP-only cases.
- In `MDGIMG`, extend data model `BP` and add the attribute to `BP_CENTRL` or `BP_VENGEN` as applicable.
- Generate or regenerate MDG structures if the data model change requires it.
- Maintain SMT mappings: `BP_BP_CENTRL_2API` and `MDG_BS_BP_MAP_2STA` for BP-only, or `SUPPL_BP_VENGEN_2API` and `SUPPL_BP_VENGEN_2STA` for Vendor/Customer-only.
- Check mapping customizing for errors in `MDGIMG`.
- Maintain field properties for the UI.
- If needed, enable HANA search and add the field to search UIBBs such as `BS_CU_DQUERY_HA` or `BS_SP_DQUERY_HA`.」「Run Adjust Staging Area of Linked Change Requests for data model `BP`.」「If the field exists in both BP and Vendor/Customer, add
MDGIMGGeneral Settings → Data Modeling → Edit Data Model → BP → Entity Types → Attributes
Extend data model `BP` with the custom attribute for `BP_CENTRL` or `BP_VENGEN`
MDGIMGGeneral Settings → Data Modeling → Generate Data Model-Specific Structures
Generate or regenerate the MDG structures after attribute changes
MDGIMGGeneral Settings → Data Modeling → Extend Mappings → Extend Mappings
Maintain SMT field mappings such as `BP_BP_CENTRL_2API`, `MDG_BS_BP_MAP_2STA`, `SUPPL_BP_VENGEN_2API`, and `SUPPL_BP_VENGEN_2STA`
MDGIMGGeneral Settings → Data Modeling → Create and Edit Mappings → Check Customizing
Check SMT mapping customizing for errors
MDGIMGGeneral Settings → UI Modeling → Define Field Properties for UI
Make the new field visible/controllable in the MDG UI framework
MDGIMGGeneral Settings → Data Quality and Search → Search and Duplicate Check → Define Joins, Field Mapping, and Authorizations for Reuse Tables
Maintain field mapping for SAP HANA-based search and search views for reuse fields and add the field to the search application if required
Referenced tables
| Object | Purpose |
|---|---|
BUT000 | Business Partner general data table for BP-only and shared-field scenarios |
KNA1 | Customer general data table |
KNB1 | Customer company-code data table |
KNVV | Customer sales data table |
LFA1 | Supplier general data table |
LFB1 | Supplier company-code data table |
LFM1 | Supplier purchasing-organization data table |
VMDS_EI_VMD_CENTRAL_DATA | Vendor central data structure used in the reuse-option scenario |
VMDS_EI_VMD_CENTRAL_DATA_XFLAG | Vendor X-flag structure used in the reuse-option scenario |
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 include should I use for BUT000, KNA1, KNB1, KNVV, LFA1, LFB1, or LFM1?
- Which transaction do I use to add a custom attribute to data model BP?
- Which SMT mappings are required for BP-only, Vendor-only, or BP-and-Vendor fields?
- When do I need CVI custom mapping?
- How do I add the custom field to the MDG UI and search?
- How do I adjust the staging area after a data model change?