Extend Data Model 0G by New Fields in Master Data Governance for Financials
This guide provides you with the foundation knowledge you need to extend the Master Data Governance for Financials data model by new fields. Download the DocumentPUBLIC
How-To
Extend MDG-F Data Model 0G by New Fields
Applicable releases:
All
Version: 1.6
Date: 2026-02-03
How-To
Extend MDG-F Data Model 0G by New Fields
Applicable releases:
All
Version: 1.6
Date: 2026-02-03
Document History
Document Version Description
1.6 Layout update
1.5 Minor textual updates and updated links
1.4 Updated Layout
1.3 Updated links for new SAP Community
1.2 Additional information for data transfer
1.1 Updated broken links
1.0 First official release of this guide
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on https://www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 2 / 41
Document Version Description
1.6 Layout update
1.5 Minor textual updates and updated links
1.4 Updated Layout
1.3 Updated links for new SAP Community
1.2 Additional information for data transfer
1.1 Updated broken links
1.0 First official release of this guide
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on https://www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 2 / 41
Table of Contents
1. Business Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. SAP Notes and Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Background Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Step by Step Explanation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Preparation of the Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1.1. Analyze the Field Attributes in the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1.2. Translate the Field Attributes into the MDG-F Specific Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1.3. Identify Further Development Items According to the Source System . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Extension of the MDG-F data model 0G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.1. Prepare the data model enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.2. Add fields as attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.3. Add fields using entity types with SU Type 3 and relations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.4. Activate the data model and generate the model-specific structures. . . . . . . . . . . . . . . . . . . . . . . . 10
4.3. Extension of the User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3.1. Upgrade and/or migration of "old" user interface enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3.2. Adding new fields to an existing UIBB vs. creating a new UIBB for the new fields . . . . . . . . . . . . 11
4.3.3. Create a custom feeder class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3.4. Optional: Implement transient fields in the feeder class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.5. Add fields to an existing UIBB (Option 1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.6. Add fields as a new UIBB (Option 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3.7. Implement OVS search helps in the feeder class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3.8. Optional: Implement the text retrieval for transient text fields in the feeder class . . . . . . . . . . . 20
5. Remarks on Data Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1. Initial Load using the MDM Generic Extractor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2. Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6. Appendix – Source Code of ZCL_MDGF_GUIBB_CCTR_JVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.1. Method CREATE_STRUCT_RTTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.2. Method GET_DEFINITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.3. Method GET_ENTITY_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.4. Method HANDLE_PHASE_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.5. Method OVS_HANDLE_PHASE_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.6. Method OVS_HANDLE_PHASE_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.7. Method OVS_OUTPUT_ZCTRETYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.8. Method OVS_OUTPUT_ZCTRJIBCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.9. Method OVS_OUTPUT_ZCTRJIBSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.10. Method OVS_OUTPUT_ZCTRRECID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.11. Method OVS_OUTPUT_ZCTRVNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
7. Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.1. Further Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.1.1. Information on SAP MDG on SAP S/4HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.1.2. SAP Roadmap Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.1.3. Related Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.2. SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on https://www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 3 / 41
1. Business Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. SAP Notes and Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Background Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Step by Step Explanation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Preparation of the Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1.1. Analyze the Field Attributes in the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1.2. Translate the Field Attributes into the MDG-F Specific Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1.3. Identify Further Development Items According to the Source System . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Extension of the MDG-F data model 0G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.1. Prepare the data model enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.2. Add fields as attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.3. Add fields using entity types with SU Type 3 and relations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.4. Activate the data model and generate the model-specific structures. . . . . . . . . . . . . . . . . . . . . . . . 10
4.3. Extension of the User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3.1. Upgrade and/or migration of "old" user interface enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3.2. Adding new fields to an existing UIBB vs. creating a new UIBB for the new fields . . . . . . . . . . . . 11
4.3.3. Create a custom feeder class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3.4. Optional: Implement transient fields in the feeder class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.5. Add fields to an existing UIBB (Option 1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.6. Add fields as a new UIBB (Option 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3.7. Implement OVS search helps in the feeder class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3.8. Optional: Implement the text retrieval for transient text fields in the feeder class . . . . . . . . . . . 20
5. Remarks on Data Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1. Initial Load using the MDM Generic Extractor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2. Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6. Appendix – Source Code of ZCL_MDGF_GUIBB_CCTR_JVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.1. Method CREATE_STRUCT_RTTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.2. Method GET_DEFINITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.3. Method GET_ENTITY_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.4. Method HANDLE_PHASE_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.5. Method OVS_HANDLE_PHASE_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.6. Method OVS_HANDLE_PHASE_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.7. Method OVS_OUTPUT_ZCTRETYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.8. Method OVS_OUTPUT_ZCTRJIBCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.9. Method OVS_OUTPUT_ZCTRJIBSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.10. Method OVS_OUTPUT_ZCTRRECID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.11. Method OVS_OUTPUT_ZCTRVNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
7. Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.1. Further Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.1.1. Information on SAP MDG on SAP S/4HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.1.2. SAP Roadmap Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.1.3. Related Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.2. SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on https://www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 3 / 41
1. Business Scenario
SAP Master Data Governance for Financials (MDG-F) provides business processes to find, create, change, and
mark financial master data for deletion. It supports the governance of financial master data in a central hub
and the distribution to connected operational and business intelligence systems.
The processes are workflow-driven and can include several approval and revision phases, and the collabora
tion of all users participating in the master data maintenance.
This How to Guide describes the solution to extend an existing entity type with storage and use type 1 with
some new fields. It covers the key concepts and implementation details in general and includes a real-life
example of the MDG-F data model 0G.
2. SAP Notes and Links
In addition to the detailed explanations written in this document, please see the following SAP Notes and
links for further important information:
1637249 MDG: Information for efficient message processing
2021246 MDG Financials – (Un-) Supported Segments and Fields
2105467 MDG Performance
2337685 MDG-F: Standard Validations of Data Model 0G
Configuration and Enhancement of SAP Master Data Governance
Web Dynpro & Floorplan Manager
3. Background Information
MDG offers a domain specific solution for financial governance (MDG-F). The current MDG-F data model is
called 0G. It covers entity types of the accounting, controlling and consolidation components of financial mas
ter data as indicated by the examples below:
• Accounting: G/L Account (ACCOUNT & ACCCCDET), Company
• Controlling: Cost Center (CCTR), Cost Element (CELEM) and Profit Center (PCTR)
• Consolidation: Consolidation Unit (CONSUNIT), Item (FSI)
In SAP ECC systems a Cost Center can be used for Joint Venture Accounting. Joint venture accounting has
been an add-on to SAP ECC before SAP ECC 6.0. Starting with SAP ECC 6.0 it is a built-in feature that needs
activation via business function(s). It adds some field to the SAP ECC cost center master data:
• Joint Venture
• Recovery Indicator
• Equity Type
• Joint Venture Object Type
• JIB/JIBE Class & Subclass A
The fields cannot be pre-defined by SAP within MDG-F data model 0G. They are valid only if both the MDG-F
and Joint Venture Accounting business functions are active.
In S/4 HANA, from release 1610 on, the business function for Joint Venture Accounting is already active
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on https://www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 4 / 41
SAP Master Data Governance for Financials (MDG-F) provides business processes to find, create, change, and
mark financial master data for deletion. It supports the governance of financial master data in a central hub
and the distribution to connected operational and business intelligence systems.
The processes are workflow-driven and can include several approval and revision phases, and the collabora
tion of all users participating in the master data maintenance.
This How to Guide describes the solution to extend an existing entity type with storage and use type 1 with
some new fields. It covers the key concepts and implementation details in general and includes a real-life
example of the MDG-F data model 0G.
2. SAP Notes and Links
In addition to the detailed explanations written in this document, please see the following SAP Notes and
links for further important information:
1637249 MDG: Information for efficient message processing
2021246 MDG Financials – (Un-) Supported Segments and Fields
2105467 MDG Performance
2337685 MDG-F: Standard Validations of Data Model 0G
Configuration and Enhancement of SAP Master Data Governance
Web Dynpro & Floorplan Manager
3. Background Information
MDG offers a domain specific solution for financial governance (MDG-F). The current MDG-F data model is
called 0G. It covers entity types of the accounting, controlling and consolidation components of financial mas
ter data as indicated by the examples below:
• Accounting: G/L Account (ACCOUNT & ACCCCDET), Company
• Controlling: Cost Center (CCTR), Cost Element (CELEM) and Profit Center (PCTR)
• Consolidation: Consolidation Unit (CONSUNIT), Item (FSI)
In SAP ECC systems a Cost Center can be used for Joint Venture Accounting. Joint venture accounting has
been an add-on to SAP ECC before SAP ECC 6.0. Starting with SAP ECC 6.0 it is a built-in feature that needs
activation via business function(s). It adds some field to the SAP ECC cost center master data:
• Joint Venture
• Recovery Indicator
• Equity Type
• Joint Venture Object Type
• JIB/JIBE Class & Subclass A
The fields cannot be pre-defined by SAP within MDG-F data model 0G. They are valid only if both the MDG-F
and Joint Venture Accounting business functions are active.
In S/4 HANA, from release 1610 on, the business function for Joint Venture Accounting is already active
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on https://www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 4 / 41
(Always-On business function).
The scenario assumes that you have activated Joint Venture Accounting in your system and now want to add
the fields to MDG-F, too.
4. Step by Step Explanation
The implementation consists of several steps. The list below relates to the planned scenario of the current
how-to guide. It may differ for your use case.
1. Preparation of the extension by collecting all required information about the fields to be added from
the source system.
a. Analyze the field attributes in the source system. Ask the following questions:
i. Which data element is used?
ii. Does the field use a check table?
iii. If yes, how is the table structured (single or multiple key fields)?
b. Translate the field attributes into the MDG-F specific format. Decide whether the field be mod
eled as an attribute or whether a relation (e.g. entity type with SU Type 3) needed.
c. Identify further development items according to the source system. Ask the following questions:
i. How are the fields represented in the backend user interface?
ii. Are the fields already part of data replication technologies or is an extension required?
2. Extension of the MDG-F data model 0G.
a. Add attributes and/or relations.
b. Activate the data model and generate the model-specific structures.
3. Extension of the User Interface.
a. Add new fields to an existing UIBB or a new UIBB (optional).
4. Validation (optional).
a. Implement new checks in USMD_RULE_SERVICE.
5. Replication (optional).
a. Replicate using ALE IDocs or SOA Services.
4.1. Preparation of the Extension
The scenario is adding the Joint Venture Accounting fields of the SAP ECC Cost Center to the MDG data
model 0G. The following steps are recommended to prepare the actual work. The information that is collected
during the preparation suites as the foundation for the extension.
4.1.1. Analyze the Field Attributes in the Source System
The fields Joint Venture, Recovery Indicator, Equity Type, Joint Venture Object Type, and JIB/JIBE classes
belong to the cost center object that is stored in data base table CSKS. Using the transaction SE11, the fol
lowing information can be retrieved about the fields:
Field Name Type Check Table Comment
Joint Venture VNAME JV_NAME
CHAR (6)
T8JV Check table uses the company code as for
eign key.
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on https://www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 5 / 41
The scenario assumes that you have activated Joint Venture Accounting in your system and now want to add
the fields to MDG-F, too.
4. Step by Step Explanation
The implementation consists of several steps. The list below relates to the planned scenario of the current
how-to guide. It may differ for your use case.
1. Preparation of the extension by collecting all required information about the fields to be added from
the source system.
a. Analyze the field attributes in the source system. Ask the following questions:
i. Which data element is used?
ii. Does the field use a check table?
iii. If yes, how is the table structured (single or multiple key fields)?
b. Translate the field attributes into the MDG-F specific format. Decide whether the field be mod
eled as an attribute or whether a relation (e.g. entity type with SU Type 3) needed.
c. Identify further development items according to the source system. Ask the following questions:
i. How are the fields represented in the backend user interface?
ii. Are the fields already part of data replication technologies or is an extension required?
2. Extension of the MDG-F data model 0G.
a. Add attributes and/or relations.
b. Activate the data model and generate the model-specific structures.
3. Extension of the User Interface.
a. Add new fields to an existing UIBB or a new UIBB (optional).
4. Validation (optional).
a. Implement new checks in USMD_RULE_SERVICE.
5. Replication (optional).
a. Replicate using ALE IDocs or SOA Services.
4.1. Preparation of the Extension
The scenario is adding the Joint Venture Accounting fields of the SAP ECC Cost Center to the MDG data
model 0G. The following steps are recommended to prepare the actual work. The information that is collected
during the preparation suites as the foundation for the extension.
4.1.1. Analyze the Field Attributes in the Source System
The fields Joint Venture, Recovery Indicator, Equity Type, Joint Venture Object Type, and JIB/JIBE classes
belong to the cost center object that is stored in data base table CSKS. Using the transaction SE11, the fol
lowing information can be retrieved about the fields:
Field Name Type Check Table Comment
Joint Venture VNAME JV_NAME
CHAR (6)
T8JV Check table uses the company code as for
eign key.
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on https://www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 5 / 41