Defining a Governance Scope
You can determine a governance scope based on your business needs. Ungoverned fields are read-only in change requests, unless you remove them from the user interface.
Example
In the material application, you can for example, remove sales grouping data from the governance scope.
You have identified the data models whose governance scope you want to change, as well as the content within each data model that you want to govern.
You are aware of the consequences of changing the governance scope. See the help document in Customizing for Master Data Governance
under
In Customizing for Master Data Governance
under , choose Define Governance Scope
.
In the Data Models
view, select the data model whose governance scope you want to define.
Make necessary changes to the Governed
settings of entity types, attributes, and referencing relationships.
If there are dependencies, a pop-up informs you of these dependencies and proposes required changes. You can apply required changes or cancel. The following changes to governance scope are not possible:
Changes to the Governed
setting for entity types
with a storage and use type
of 1.
These entity types are shown in the Customizing activity, to enable navigation to attributes.
Changes the Governed
setting of attributes that are key fields.
These attributes are not shown in the Customizing activity.
Changes to attributes for which the Required Field
setting is set to Yes
in the data model.
These attributes are not shown in the Customizing activity.
You have defined a governance scope for the data model. You can keep ungoverned data model elements on the user interface for information purposes. If the elements are not informative to your users, we recommend that you remove them. For more information, see Managing of UI Configurations.