Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-APP-ISS (Application Component) Internal Self-Services⤷
UISS_MDG_CONTENT (Package) Internal Self Services: MDG Content
IMG Activity
| ID | ISS_FIN_WORKFLOW | Workflow |
| Transaction Code | S_SE5_45000054 | (empty) |
| Created on | 20100318 | |
| Customizing Attributes | ISS_FIN_WORKFLOW | Workflow |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISS_FIN_WORKFLOW |
Use
In this Customizing activity, you define the workflow steps to which you assign a processor.
Each change request type is assigned to a Workflow (in the Customizing activity Create Change Request Type). However, each processor is assigned to the individual workflow steps. Therefore, although only one workflow can be assigned to each change request type you can still assign multiple processors to the same change request type by assigning multiple workflow steps.
The workflow template WS32900043 is delivered by SAP and assigned by default to the change request types used for Internal Self-Services for Financials. You can assign the workflow tasks in the Customizing activity Configure Workflow Tasks.
Note: It is important that you do not assign a user or an organizational unit here. If you do, the system will not run the user determination that is defined in the workflow template for the task.
Requirements
Before you can use Internal Self-Services for Financials, you need to ensure that the type linkage for the Business Object Type 2250 is activated. This type linkage is used for Master Data Governance (MDG) change requests. You can use the customizing activity Activate Type Flow Linkage (MDG_SWETYPV_BUS2250) to verify that this setting is correct. Here, it is important that Linkage Activated checkbox is selected. It is very important that you do not select the enable Event Queue checkbox. If you do, your internal self-services will not function correctly.
Standard settings
Activities
You need to consider the following Customizing activities which are part of Customizing for Master Data Governance (MDG):
- Define Workflow Step Numbers
In this Customizing activity, you define the workflow step numbers that are assigned to each workflow. You can, for example, define whether a change request requires approval or not by defining the relevant workflow number.
- Assign Processor to Workflow Step Number (Simple Version)
In this Customizing activity, you can assign processors to the individual workflow step numbers (defined in the previous step) for each type of change request. This determines which processors perform the tasks.
- BAdI Assign Processor to Workflow Step
You can use this BAdI to define rules governing the allocation of processors to the individual workflow steps. You can use this BAdi to define your own specific processors where this deviates from the standard delivery. For example, you may want to adjust the settings so that all change requests with a high priority are sent to the manager for processing.
Example
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| 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 | ISS_FIN_WORKFLOW | 0 | SE50000001 | Internal Self-Services |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20100913 |
| SAP Release Created in | 605 |
