Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-AF (Application Component) Application Framework⤷
USMD1 (Package) Master Data: Data Modeling
IMG Activity
| ID | MDG_VC_USMD007 | Define Governance Scope |
| Transaction Code | S_BT6_28000025 | (empty) |
| Created on | 20100908 | |
| Customizing Attributes | MDG_VC_USMD007 | Define Governance Scope |
| Customizing Activity | MDG_VC_USMD007 | Define Governance Scope |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | MDG_VC_USMD007 |
Use
In this Customizing activity, you can determine how much data to include in the governance process, based on your business needs. This task involves deciding which fields in the data model for your MDG application are governed.
SAP delivers a comprehensive set of fields with the data models for each MDG application. Users can edit governed fields in change requests, unless you make the fields read-only for particular change request steps. Users can never edit ungoverned fields. We recommend that you remove ungoverned fields from the user interface unless they contain information users need. The MDG framework does not store any value for an ungoverned field. For example, it is not possible to use an ungoverned field as a target for a Business Rules Framework plus (BRFplus) derivation.
You cannot access attributes that are key fields or required entry fields in this Customizing activity; these fields are always governed. Entity types with a storage and use type of 1 are also always governed, but the system includes these entity types in the Customizing activity, because you can decide which of their attributes and referencing relationships are governed. You can find the settings for key fields and required entry fields in the following Customizing activities under Master Data Governance:
When you include or exclude a field from governance, the system may prompt you to make changes to dependent fields in the data model. For more information, see the field help for the Governed indicator.
After you define the governance scope, you can fine-tune the properties of governed fields in change request steps. For example, you can decide the checks that apply, specify whether the system runs a required field check, and indicate whether a field is relevant to a change request step. You do this in the Customizing for Master Data Governance under General Settings -> Process Modeling -> Change Requests -> Configure Properties of Change Request Step.
Defining the governance scope has implications for users in the following areas:
- Single processing (processing of change requests for individual objects)
The system makes ungoverned fields read-only. For ungoverned fields, the system disables checks in the user interface.
- Mass change (processing of change requests for multiple objects at the same time)
Users cannot perform a mass change on ungoverned fields.
- File download
The system includes ungoverned fields in file download, but includes a comment in the downloaded file indicating which ungoverned fields are downloaded.
- File upload
The system omits ungoverned fields from file upload. However, if an ungoverned field is part of a file structure variant that you use for uploading and downloading files, the upload still works for all governed fields.
- Data export
The governance scope has no effect on data export; the system exports governed and ungoverned fields.
- Data import
The governance scope has no effect on data import if you do not use change requests (that means importing into the active area).
Caution
If you use change requests for the data import and you apply either the Governance setting or the Post-processing setting, the system omits ungoverned fields from the data import.
- Search
You can search for both governed fields and ungoverned fields.
To set your own rules regarding governance scope, you can use BAdI: Setting Rules for Defining Governance Scope (USMD_GOVERNANCE_SCOPE). For more information, see the documentation for BAdI Interface: Set Rules for Defining Governance Scope.
Requirements
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | MDG_VC_USMD007 | 0 | BTD0000051 | Application Framework |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VC_USMD007C | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20120330 |
| SAP Release Created in | 703 |
