Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-AF (Application Component) Application Framework⤷
USMD0 (Package) Master Data: Common Objects
IMG Activity
| ID | FMDM_USMD110 | Create Change Request Type |
| Transaction Code | S_SE4_70000041 | (empty) |
| Created on | 20080618 | |
| Customizing Attributes | FMDM_USMD110 | Create Change Request Type |
| Customizing Activity | FMDM_USMD110 | Create Change Request Type |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FMDM_USMD110 |
Use
In this Customizing activity, you define the following properties that are valid for a particular change request type:
- Data model on which a change request is based
This assignment is indirect by means of assigning an edition type.
- Objects required
You determine whether the user needs to specify which entities should be processed when creating a change request.
Note: You can use the Customizing activity Edit Statuses of Change Requests to control which workflow steps can be used for processing the object list.
- Target systems
You can specify a list of target systems where the master data affected by this change request is replicated. Note that the replication will also be performed in the systems configured within the Customizing activity Master Data Governance -> General Settings -> Data Replication. If you deselect the target system indicator when creating a new change request type, you deactivate the specification of the list of target systems.
- Business activity
You can assign a business activity to this change request.
Requirements
You have created the data model and the edition types.
Standard settings
Activities
Create one or more types of change requests and assign entity types to them. You can select only the entity types that are assigned to the selected edition type. However, you can assign an entity type to multiple types of change request.
Example
For standard changes, you use a change request type in which the object list is defined prior to processing. In this case, you create a change request type, set the Objects Required indicator, and assign all entity types to the change request type.
For mass changes, you use a different type of change request in which the object list is not required. Here, you create another change request type, do not set the Objects Required indicator, and assign all entity types to that change request type.
Now you can select between the different types when creating a change request. You can use authorizations to define that change requests of the second type can be created by certain users only.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory 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 | FMDM_USMD110 | 0 | BTD0000051 | Application Framework |
| SIMG | FMDM_USMD110 | 1 | O SE40000001 |
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_USMD110 | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20110427 |
| SAP Release Created in | 604 |
