Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-AF (Application Component) Application Framework⤷
USMD1 (Package) Master Data: Data Modeling
IMG Activity
| ID | VC_USMD008 | Configure Properties of Change Request Step |
| Transaction Code | S_BT6_28000048 | (empty) |
| Created on | 20101203 | |
| Customizing Attributes | VC_USMD008 | Configure Properties of Change Request Step |
| Customizing Activity | VC_USMD008 | Configure Properties of Change Request Step |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | MDG_VC_USMD008 |
Use
In this Customizing activity, you determine settings for the execution of a change request step for a change request type.
The following are typical tasks you can complete for a change request step:
- Enrich parts of data, by assigning an enrichment spot.
- Ensure validations occur by assigning checks.
- Specify which fields are relevant, and which relevant fields are required, by setting field properties.
- Assign a different Web Dynpro application to the standard one configured for the data model.
Sometimes, conflicts between settings might occur. In such cases, the system informs you of the conflicts.
Enrichment Spots and Checks per Change Request Step View
In this view, you can complete the following actions for a change request step:
- Specify which enrichment spots and checks are relevant.
- View the execution sequence for enrichment spots and checks.
- Control the display of messages by specifying a message output. For example, you can ensure some messages display only as warnings.
- Determine whether a check is always executed or only executed when changes occur.
Entity Types per Change Request Step View and Attributes per Change Request Step View
You can complete the following actions for a change request step:
- Specify which fields are relevant, and which relevant fields are required, by setting field properties. For example, you can make a required field optional.
- Reduce the number of checks applied to fields by specifying a Check Logic for an entity type.
- For more information about which entity types are available for configuration, see the Prerequisites section.
User Interface per Change Request Step View
You can assign a Web Dynpro application and a corresponding Web Dynpro configuration to a change request step.
This allows you to deviate from settings defined in the following Customizing activities:
- Link Actions to a UI Application and Business Activity: Standard Definition
- Link Actions to a UI Application and Business Activity: Customer Definition
The following screens you can use for navigation only:
- starting from a personal object worklist (POWL)/ universal worklist (UWL)
- starting from a search result screen
- starting from a My Change Requests screen
- starting from a Display Change Requests screen
- starting from an object list
Requirements
Governance Scope
You can only define properties for entity types, attributes, or relationships that are governed. You can apply this setting in Customizing for Master Data Governance under General Settings -> Process Modeling -> Define Governance Scope.
Change Requests
You have associated the change request types with data models in the Create Change Request Type Customizing activity.
Change Request Steps
You have defined change request steps in Customizing.
You create change request steps in one of the following Customizing activities, depending on which type of workflow is used for the change request type:
- General Settings -> Process Modeling -> Workflow -> Rule-based Workflow -> Define Steps for Rule-Based Workflow
- General Settings -> Process Modeling -> Workflow -> Other MDG Workflows -> Define Workflow Step Numbers
Entity Types per Change Request Step
You have defined entity types that can be configured at change request step level.
Only the following entity types can be configured:
- Main entity types with a storage and use type of 1
This setting is defined in the Type of Change Request view of the Create Change Request Type activity.
- Entity types related to main entity types with a Storage and Use type of 1 or 4
You can apply this setting in the following locations:
- The General tab page of the Configuration Workbench Customizing activity
- To access this tab page, you must select a data model and then an entity type.
- The Entity Types view of the Edit Data Model Customizing activity
For each entity type, you have created a structure for use in Field Properties for Attributes and Key Fields in the Structures view of Customizing activity Generate Data Model-Specific Structures.
Attributes per Change Request Step
You have defined attributes that can be configured at the level of the change request step.
Only the following attributes can be configured:
- Direct attributes
The attributes of the entity type itself
- Resolved attributes
Attributes from a referenced entity type
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 |
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_USMD008 | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20110614 |
| SAP Release Created in | 703 |
