Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG (Application Component) Master Data Governance⤷
MDG_BS_COMMON_OBJECTS (Package) MDG: Common Objects (IMG, Switches, Roles, ...)
IMG Activity
| ID | FMDM_USMDA420101 | Assign Processor to Workflow Step Number (Extended Workflow) |
| Transaction Code | S_E7B_95000010 | (empty) |
| Created on | 20120827 | |
| Customizing Attributes | FMDM_USMDA420101 | Assign Processor to Workflow Step Number (Extended Workflow) |
| Customizing Activity | FMDM_USMDA420101 | Assign Processor to Workflow Step Number (Extended Workflow) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FMDM_USMDA42010 |
Use
In this Customizing activity, you assign processors to the individual workflow step numbers for each type of change request and each entity type. This determines which tasks the processors need to perform.
Requirements
The following prerequisites must be met:
- You have done the basic Customizing for the workflow.
- You have edited the step numbers for your workflow.
- If applicable, you have modeled the organizational plan of your enterprise in the system.
- You have created the type of the change request you want to use to assign a processor to the workflow step numbers.
- While creating the change request type, you selected the Objects Required checkbox.
Standard settings
Activities
To make an assignment between a processor and a workflow step number, proceed as follows:
- Under Processor Assignment to Workflow Step Number, make the settings for the default entries for each step.
Only one entry is possible per change request type and step. These default entries are used if no entry exists in the table Processor Determination Depends on Entity Type, which contains the assignments of processors to steps and entity types.
- If it makes sense to make the processor assignment dependent on the entity type for certain workflow steps - due to how the master data is organized in the enterprise - make the following assignment under Processor Determination Depends on Entity Type:
- Under Processor Assignment to Workflow Step Number, select the entry for which you want to make the processor assignment dependent on the entity type.
- Make the necessary settings.
- If you want to activate a processor (for example, for testing purposes) and then deactivate the processor again, deselect or select the Inactive indicator (X = inactive).
- If the indicator is selected, the entry is ignored during the processor assignment.
Example
To define that the evaluation for change request type 0F and entity type COA is to be performed by organizational unit 50000734, you create the following entry under Processor Determination Depends on Entity Type for the change request type:
Entity Type Processor Type Processor ID
COA O 50000734
You define organizational unit 50000807 as the default setting for the change request type under Processor Assignment to Workflow Step Number:
Step Description Object Type Processor ID
1 Evaluation O 50000807
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_USMDA42010 | 0 | SE40000001 | MDG for Financials |
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 |
| IMGDUMMY | D - Dummy object | USMDA4_MAINTAIN_VC |
History
| Last changed by/on | SAP | 20120827 |
| SAP Release Created in | 732 |
