Master Data Governance, Generic Functions 3
Technical Name of Business Function |
MDG_FOUNDATION_3 |
Type of Business Function |
Enterprise Business Function |
Available From |
SAP Master Data Governance 6.1 |
|
Technical Usage |
Master Data Governance |
Application Component |
|
Required Business Function |
Master Data Governance, Generic Functions ( Master Data Governance, Generic Functions 2 ( |
You can use this business function to employ new features of SAP Master Data Governance for defining the governance scope, the blocking of entities and the data quality remediation.
You can use this business function to tailor the preconfigured data models for Financials, Material, Supplier, and Customer, or to create your own data models without using a template.
Once the business function is activated, you can adjust your Customizing settings under . In the target systems, you activate the business functions of SAP Master Data Governance that are relevant to your applications.
You have installed the following components as of the version mentioned:
Type of Component |
Component |
Required for the Following Features Only |
|---|---|---|
|
Software Component |
|
Note
For information on MDG business functions and activated industry solutions, see SAP Note 1690202
.
When you activate this business function, the following features of the application component SAP Master Data Governance (CA-MDG) become available:
You can allow or disallow the update of fields in single processing, in mass change, and in file upload.
Ungoverned fields can still be used in the following areas:
Single processing UI (as read-only fields)
Business rules (for checks)
File download
Search
With this function you can prevent that entities are changed due to application specific reasons. With the MDG application framework you can block entities to ensure that these entities are not added to change requests. The system checks, if application specific reasons exist, whenever an entity is added to the object list of a change request.
This function covers the following use cases:
External Reason: The entity is blocked independent of whether any other entity is being processed with a change request.
Same Entity Type (Symmetric): The processing of an entity blocks the processing of another entity and vice-versa.
Same Entity Type (Asymmetric): The processing of one entity blocks another, but not vice-versa.
Other Entity Type: Processing of one entity blocks entities of another type.
The data quality remediation provides the process integration of identifying master data objects with errors in a data quality tool as the SAP Information Steward, for example, and their correction in Master Data Governance. In order to use this process, you additionally need to implement a tool that is not part of the delivery of SAP Master Data Governance 6.1.
After you have implemented a data quality tool you can use the data quality remediation to do the following:
You can analyze master data according to a set of data quality rules to detect objects with errors.
If a data quality tool offers the filtering of the objects with errors according to a rule (or a set of rules), MDG allows the master data specialist to select the criteria for the filtering.
The data quality remediation retrieves the objects with errors and displays them for investigation by the master data specialist. The master data specialist selects an object with errors and creates a change request for the data quality remediation.
The following new role provides the menu and authorizations for working with the example data model SF (Flight Data Model) and the related processes of the application framework of SAP Master Data Governance for custom objects using SAP NetWeaver Business Client:
Custom Objects for Master Data Governance - Flight Data Model (SAP_MDGX_FND_SAMPLE_SF_03)