Master Data Governance for Financials: Enable Changeable IDs
This document explains how to enable the new functionality of changeable IDs for Master Data Governance for Financials entities. It describes the key concepts and implementation details as well as possible enhancement options. Download the DocumentPUBLIC
How-To
Enable Changeable IDs in MDG-F
Applicable releases:
From MDG 7.0 on
Version: 4.0
Date: December 2025
How-To
Enable Changeable IDs in MDG-F
Applicable releases:
From MDG 7.0 on
Version: 4.0
Date: December 2025
Document History
Document Version Description
1.4 New Layout and updated links
1.3 New Layout and updated links
1.2 Updated new SAP Community Links
1.1 Updated chapter “Adjust MDG Customizing”
1.0 First official release of this guide (October 2016)
© 2025 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 / 9
Document Version Description
1.4 New Layout and updated links
1.3 New Layout and updated links
1.2 Updated new SAP Community Links
1.1 Updated chapter “Adjust MDG Customizing”
1.0 First official release of this guide (October 2016)
© 2025 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 / 9
Table of Contents
1. Business scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. SAP notes and links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Background information and prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Step by Step Explanation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.1. Further Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
© 2025 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 / 9
1. Business scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. SAP notes and links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Background information and prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Step by Step Explanation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.1. Further Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
© 2025 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 / 9
1. Business scenario
SAP Master Data Governance provides business processes to find, create, change, and mark master data for
deletion. It supports the governance of master data in a central hub and the distribution to connected opera
tional 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 guide explains how to enable the functionality of changeable IDs for MDG-F entities. It describes the key
concepts and implementation details as well as possible enhancement options.
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 and prerequisites
You must have access to an SAP system with the MDG business functions enabled. You need access to the
system used for cross-client maintenance. You must have a basic understanding of the following areas:
• SAP Master Data Governance
• SAP Floorplan Manager (FPM). For more information see SAP Note 1619534 - How to Create, Enhance
and Adapt FPM Applications
• MDG-F Overview Guide
• MDG-F Extend Data Model by New Fields
• MDG 7.0 feature pack 1 support package 2
4. Step by Step Explanation
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
master 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)
The default implementation for the data model 0G defines all key components of the entity types with SU
Type 1 as external and non-changeable. The master data requestor must define the keys in the first steps of
© 2025 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 / 9
SAP Master Data Governance provides business processes to find, create, change, and mark master data for
deletion. It supports the governance of master data in a central hub and the distribution to connected opera
tional 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 guide explains how to enable the functionality of changeable IDs for MDG-F entities. It describes the key
concepts and implementation details as well as possible enhancement options.
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 and prerequisites
You must have access to an SAP system with the MDG business functions enabled. You need access to the
system used for cross-client maintenance. You must have a basic understanding of the following areas:
• SAP Master Data Governance
• SAP Floorplan Manager (FPM). For more information see SAP Note 1619534 - How to Create, Enhance
and Adapt FPM Applications
• MDG-F Overview Guide
• MDG-F Extend Data Model by New Fields
• MDG 7.0 feature pack 1 support package 2
4. Step by Step Explanation
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
master 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)
The default implementation for the data model 0G defines all key components of the entity types with SU
Type 1 as external and non-changeable. The master data requestor must define the keys in the first steps of
© 2025 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 / 9
the creation process. The keys cannot be changed in later process steps, for example by a master data expert.
Nevertheless, many real-life scenarios require a late assignment of the actual object ID (for example the
account or the cost center number) since its correct value is usually unknown to the master data requestor.
The document explains the configuration steps you must apply to the MDG system to enable this feature.
4.1. Implementation
The feature does not change the data model definition. It provides the functionality on the user interface level.
It only allows you to changing IDs (such as account numbers or cost center numbers) only. It does not enable
you to change key components that related to entity types with SU Type 3 (such as chart of accounts or con
trolling areas).
You can use the feature only for the creation of new entities in single object maintenance. The feature is not
supported in mass maintenance or in hierarchy maintenance.
The implementation consists of several steps.
1. Create a custom Web Dynpro Application Configuration.
The feature itself is enabled by a new application parameter. The parameter is not set in the default
deliverables by SAP. The document uses the Cost Center entity type as an example configuration.
2. Create a custom MDG Communicator Configuration.
Using a custom Web Dynpro application configuration requires the creation of a custom MDG Communicator
configuration, too. Otherwise, the integration of the change request and its UIBBs would not work automati
cally anymore.
3. Add your custom Web Dynpro Application Configuration to the MDG Customizing.
Using a custom Web Dynpro Application Configuration requires a few updates in MDG customizing
tables that are used during the navigation into the user interfaces.
4.1.1. Step 1: Create a Custom Web Dynpro Application Configuration
The changeable IDs functionality is enabled by setting the application parameter
MDGF_ENABLE_KEY_SWITCH to X within a Web Dynpro Application Configuration. SAP delivers these for
each entity type with SU Type 1 that has its own user interface. It is possible to enable the feature only for a
single entity type. The following steps use the `Cost Center `as an example.
1. Start the Web Dynpro application configurator for the application configuration.
2. Define the existing Web Dynpro application configuration with component name MDGF_OVP_GEN and
its configuration ID MDGF_0G_OVP_CCTR.
3. Choose the Copy button. Follow the instruction of the Copy Configuration pop-up to create your
custom Web Dynpro application configuration.
© 2025 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 / 9
Nevertheless, many real-life scenarios require a late assignment of the actual object ID (for example the
account or the cost center number) since its correct value is usually unknown to the master data requestor.
The document explains the configuration steps you must apply to the MDG system to enable this feature.
4.1. Implementation
The feature does not change the data model definition. It provides the functionality on the user interface level.
It only allows you to changing IDs (such as account numbers or cost center numbers) only. It does not enable
you to change key components that related to entity types with SU Type 3 (such as chart of accounts or con
trolling areas).
You can use the feature only for the creation of new entities in single object maintenance. The feature is not
supported in mass maintenance or in hierarchy maintenance.
The implementation consists of several steps.
1. Create a custom Web Dynpro Application Configuration.
The feature itself is enabled by a new application parameter. The parameter is not set in the default
deliverables by SAP. The document uses the Cost Center entity type as an example configuration.
2. Create a custom MDG Communicator Configuration.
Using a custom Web Dynpro application configuration requires the creation of a custom MDG Communicator
configuration, too. Otherwise, the integration of the change request and its UIBBs would not work automati
cally anymore.
3. Add your custom Web Dynpro Application Configuration to the MDG Customizing.
Using a custom Web Dynpro Application Configuration requires a few updates in MDG customizing
tables that are used during the navigation into the user interfaces.
4.1.1. Step 1: Create a Custom Web Dynpro Application Configuration
The changeable IDs functionality is enabled by setting the application parameter
MDGF_ENABLE_KEY_SWITCH to X within a Web Dynpro Application Configuration. SAP delivers these for
each entity type with SU Type 1 that has its own user interface. It is possible to enable the feature only for a
single entity type. The following steps use the `Cost Center `as an example.
1. Start the Web Dynpro application configurator for the application configuration.
2. Define the existing Web Dynpro application configuration with component name MDGF_OVP_GEN and
its configuration ID MDGF_0G_OVP_CCTR.
3. Choose the Copy button. Follow the instruction of the Copy Configuration pop-up to create your
custom Web Dynpro application configuration.
© 2025 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 / 9