SAP MDG · DATA MODEL UI
How do I extend SAP MDG Business Partner, Customer, or Supplier governance?
SAP MDG Business Partner governance is based on change requests, staging, approval, activation, and distribution. MDG-BP is the foundation, while MDG-C and MDG-S extend it for customer and supplier-specific data. For extensions, first identify the target object and release behavior, then inspect data model BP, check CVI impact, extend the correct software layer, use a custom handler, extend genIL and UI objects, and test activation and UI behavior.
SAP MDG Business Partner governance is based on change requests, staging, approval, activation, and distribution. MDG-BP is the foundation, while MDG-C and MDG-S extend it for customer and supplier-specific data. For extensions, first identify the target object and release behavior, then inspect data model BP, check CVI impact, extend the correct software layer, use a custom handler, extend genIL and UI objects, and test activation and UI behavior.
SAP MDG Business Partner governance uses workflow-driven change requests with staging, approval, activation, and distribution. MDG-BP is the foundation, while MDG-C and MDG-S are built on top of it for customer and supplier governance. Before coding, decide whether the new data belongs to BP, Customer, Supplier, or several objects, then check the BP data model and CVI impact.
Process flow
- Use MDG to find, create, change, or mark master data for deletion.
- Maintain master data in a central governance hub.
- Process changes using workflow-driven change requests.
- Use staging while the change request is being processed.
- Perform approval and revision phases as required.
- Activate approved master data.
- Distribute activated master data to connected systems.
- Treat `MDG-BP` as the foundation for Business Partner governance, `MDG-C` for customer-specific data, and `MDG-S` for supplier-specific data.
MDG data model display
Inspect data model `BP`, review entities and fields, and validate the local MDG model content.
Referenced tables
| Object | Purpose |
|---|---|
BUT000 | Example active Business Partner table referenced by the guide. |
KNA1 | Example active customer table referenced by the guide. |
LFA1 | Example active supplier/vendor table referenced by the guide. |
VC_MDG_BS_GENIL | SAP entity-to-genIL mapping view for MDG BP-related models. |
VC_MDG_BS_GENIL_C | Custom entity-to-genIL mapping view for BP extensions. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What does MDG provide for Business Partner governance?
- How does MDG process Business Partner master data?
- What is the purpose of MDG-BP, MDG-C, and MDG-S?
Possible questions
- Which MDG data model is used for Business Partner?
- How do I decide whether a field belongs to BP, Customer, or Supplier?
- What is the correct extension sequence for MDG BP?
- How do CVI and activation affect BP extensions?
- Which access classes and handler classes are relevant for MDG BP?
- Which genIL and FPM objects are typically extended for BP UI changes?