SAP MDG · DATA MODEL UI
How do I extend MDG-S/MDG-C with a new entity type using the Flex Option?
Use the Flex Option when the new entity data should remain in MDG-generated tables after activation. In the example, you create entity type ZINFOREC and support entity ZMATNR in data model BP via MDGIMG, activate and adjust staging, generate the BP-specific structures, then extend the BUPA genIL model and Supplier UI so the entity appears in the Supplier overview page.
Use the Flex Option when the new entity data should remain in MDG-generated tables after activation. In the example, you create entity type ZINFOREC and support entity ZMATNR in data model BP via MDGIMG, activate and adjust staging, generate the BP-specific structures, then extend the BUPA genIL model and Supplier UI so the entity appears in the Supplier overview page.
Use the Flex Option for MDG-S/MDG-C when the custom entity should be stored only in MDG tables after change request activation. In the source example, data model BP is extended with ZINFOREC (Purchasing Info Record) plus ZMATNR, then the UI is enhanced so the new entity can be maintained in the Supplier overview page.
Process flow
- Open MDGIMG and edit data model BP
- Create entity type ZINFOREC with storage/use type Changeable via Other Entity Type
- Create supporting entity ZMATNR with data element MATNR
- Create leading relationship ZZBP2INFR from BP_HEADER to ZINFOREC
- Create qualifying relationship ZZMAT2INF from ZMATNR to ZINFOREC
- Add attribute ZZPURBLOC with data element SPERM_X
- Activate the model and choose Adjust Staging Area if prompted
- Generate data model-specific structures in MDGIMG and verify ZXX_S_BP_PP_ZINFOREC and ZXX_S_BP_FP_ZINFOREC variants in SE11 if needed, see guide examples for exact names used there as generated artifacts can vary by category naming in the c
MDGIMGGeneral Settings > Data Modeling > Edit Data Model
Create and activate entity types, relationships, and attributes for data model BP
MDGIMGGeneral Settings > Data Modeling > Generate Data Model-Specific Structures
Generate BP-specific active area mapping and field property structures
Create enhancement under superenhancement BUPA_CUSP and define dependent object/relation
Extend the BUPA genIL model for the new entity
SE34View Cluster VC_MDG_BS_GENIL_C
Connect MDG data model BP with the genIL object and node mapping
SE80Copy BS_OVP_SP to ZBS_OVP_SP and BS_SP_OVP to ZZBS_SP_OVP
Copy and adapt Supplier UI application/component configurations
SE80Create or copy FPM_LIST_UIBB template to ZFPM_LIST_UIBB_PIR
Build the custom List UIBB for the new entity and wire it into the Supplier OVP
Referenced tables
| Object | Purpose |
|---|---|
BP_HEADER | Leading parent entity in the BP model relationship to the custom entity |
ZINFOREC | Custom flex entity stored in MDG-generated tables |
ZMATNR | Supporting entity using material key data element MATNR |
USMD_DATA_MODEL | Program to inspect generated tables for a data model/entity type |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is the Flex Option for an MDG-S/MDG-C entity extension?
- How do I add an entity that exists only in MDG?
- When should I use this new entity type extension guide?
Possible questions
- What transaction do I use to create a new entity type in the MDG data model?
- What transaction generates the MDG data model-specific structures?
- How do I see the generated database tables for a new entity type?
- What transaction/tool is used to extend the genIL model?
- How do I connect the MDG data model with the genIL data model?
- Which transaction is used to copy or create the UI configurations?