SAP MDG · COMMUNITY
How do I extend the SAP MDG Business Partner governance setup, and where should I start?
Start by identifying whether the extension belongs to Business Partner, Customer, Supplier, or more than one object. Then inspect data model BP, check CVI impact, use the correct software layer and handler architecture, extend the genIL model, and finally expose the data in the relevant FPM UI through UIBBs and OVPs.
Start by identifying whether the extension belongs to Business Partner, Customer, Supplier, or more than one object. Then inspect data model BP, check CVI impact, use the correct software layer and handler architecture, extend the genIL model, and finally expose the data in the relevant FPM UI through UIBBs and OVPs.
This guide explains how SAP MDG Business Partner governance works and how to plan an extension safely. The key starting point is data model BP: verify whether your new field or node belongs to BP itself, or whether it also needs Customer/Supplier synchronization through CVI. From there, use the existing access/handler architecture, extend the genIL model at the matching hierarchy position, and finish with the required FPM UI configuration.
Process flow
- Identify whether the extension belongs to BP, Customer, Supplier, or multiple objects.
- Use data model BP and review the entity types in your system with
USMD_DISPLAY_DATA_MODEL. - Check whether CVI synchronization is required.
- Choose the correct layer: MDG_FND or MDG_APPL.
- Register or extend a handler instead of changing access classes.
- Add derivation logic only if the value must be calculated.
- Extend the genIL model and verify the hierarchy position.
- Maintain mapping and fix type-based mapping only if needed using IF_BS_TYPECASTED_MAP_ASSISTANT methods as appropriate.
MDG data model BP
Display the Business Partner data model and check entity types, reuse entities, and field support.
MDG data model BP
Use the BP data model for Business Partner, Customer, and Supplier governance.
Cross-Application Components → Master Data Synchronization → Customer Vendor Integration
Configure CVI synchronization, BP role triggers, grouping, account-group mapping, and number ranges.
Referenced tables
| Object | Purpose |
|---|---|
BUT000 | Example active Business Partner table. |
KNA1 | Example active customer table. |
LFA1 | Example active supplier/vendor table. |
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 display data model BP?
- What release restrictions apply?
- How do I decide whether a custom field belongs to BP, Customer, or Supplier?
- How does CVI affect an MDG-BP extension?