SAP MDG · COMMUNITY
How do I extend MDG-F data model 0G with new fields?
Extend MDG-F data model 0G by first classifying each backend field as either a simple attribute or an SU Type 3 entity with relationships, then enhance and activate the model, extend the UI, and only afterward address validation, initial load, and replication.
Extend MDG-F data model 0G by first classifying each backend field as either a simple attribute or an SU Type 3 entity with relationships, then enhance and activate the model, extend the UI, and only afterward address validation, initial load, and replication.
The recommended MDG-F approach is to analyze each backend field first, decide whether it can be modeled as a simple attribute or needs an SU Type 3 entity, then enhance data model 0G in the MDG data modeling workbench. After that, activate the model, verify the generated structures, and extend the UI with either an existing UIBB or a custom form UIBB.
Process flow
- Analyze each source field in SE11 for data element and check-table dependencies.
- Decide whether the field is a simple attribute or requires an SU Type 3 entity.
- Open MDGIMG and prepare data model 0G for enhancement.
- Assign a transport package for the customizing include if required.
- Add simple attributes in the data modeling workbench.
- Create SU Type 3 entities for complex fields.
- Create leading relationships for foreign-key dependencies.
- Create referencing relationships to CCTR where needed with no existence check as specified by the source example.','Check and activate data model 0G, then adjust linked change requests if USMD1B040 appears.','Verify the active model and the
MDGIMGGeneral Settings → Data Modeling → Assign Package for Customizing Include
Assign a package to data model 0G if the enhancement must be transported.
MDGIMGGeneral Settings → Data Modeling → Edit Data Model
Open data model 0G in the MDG data modeling workbench.
MDGIMGData modeling workbench → Entity Types → CCTR → Attributes → New Entries (F5)
Add simple attribute `ZJV_OTYPE` with data element `JV_OTYPE`.
MDGIMGData modeling workbench → Entity Types → New Entries (F5)
Create SU Type 3 entity `ZVNAME` with data element `JV_NAME` and the source-specified settings.
MDGIMGData modeling workbench → Relationships → New Entries (F5)
Create leading relationship `ZCCVNAME` from `COMPCODE` to `ZVNAME`.
MDGIMGData modeling workbench → Relationships → New Entries (F5)
Create referencing relationship `ZCTRVNAME` from `ZVNAME` to `CCTR` with cardinality `0 : N` and `No Existence Check = True`.
Referenced tables
| Object | Purpose |
|---|---|
CSKS | Source table analyzed for the JVA fields used in the Cost Center extension. |
T8JV | Check table for `VNAME` / Joint Venture. |
T8JJ | Check table for `RECID` / Recovery Indicator. |
T8JG | Check table for `ETYPE` / Equity Type. |
T8J6A | Check table for `JV_JIBCL` / JIB/JIBE Class. |
T8J6C | Check table for `JV_JIBSA` / JIB/JIBE Subclass A. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How do I add custom fields to MDG-F data model 0G?
- How can I extend an existing MDG-F entity with new fields?
- How do I extend Cost Center in SAP MDG-F?
Possible questions
- What is data model 0G?
- Which financial master-data objects are in MDG-F 0G?
- Which entity represents Cost Center in MDG-F?
- How do I decide between a simple attribute and SU Type 3?
- Which fields in the JVA example become simple attributes and which become SU Type 3 entities?