Set Up the Workflow
This section describes how to make the Customizing settings required to run the workflow for the approval process in MDG-S.
You define the workflow settings in Customizing for Master Data Governance, Central Governance
under .
Activate type linkage
To activate the type linkage, run the following activity in Customizing for Master Data Governance, Central Governance
under .
Ensure, that one object type BUS2250 has the following settings:
Event: CREATED
Receiver Type: (blank)
Type linkage active: yes
Enable event queue: deactivated
The type linkage indicator must not be active for all other receiver types of object type BUS2250 and event CREATED. This receiver type is defined via the receiver type function module USMD_WF_RECEIVER_TYPE. Make sure that receiver function module SWW_WI_CREATE_VIA_EVENT_IBF is entered.
To enter the receiver type function module or if you need to change the settings, mark the according line in the table and choose.
Configure workflow tasks.
To configure workflow tasks, run the following activity in Customizing for Master Data Governance, Central Governance
under .
Go to application component CA-MDG-AF
and choose Assign Agents
.
All activities (denoted by TS*
) that are not set as Background Task
need to be set to General Task
. To do so, select the activity, choose Attributes
, and change to General Task
.
Repeat the procedure for all non-background activities within the CA-MDG-APP-BP
and CA-MDG-APP-SUP
application components.
Check number of workflow steps
To define the workflow steps for the workflows assigned to your change request types (which shall be assigned to a processor), run the following activity in Customizing for Master Data Governance, Central Governance
under .
If you use the change request types delivered with MDG-S, the following workflow steps are delivered:
WS54300005: Step 0, 1, 4, 5, 6, 7
WS54300007: Step 0, 1, 4, 5
WS60800059: Step 0, 1, 2, 3
WS60800068: Step 0, 1, 2, 3
WS60800095: Step 0, 1, 2, 3, 4, 5
WS72100006: Step 0, 1, 2, 3, 4, 5
Create organizational unit or change staff assignments for organizational unit
Create an organizational unit with transaction PPOCW
or change staff assignments for an organizational unit with transaction PPOME
. Users who will process the workflow steps have to be assigned to this organizational unit.
Check or set up the business rule framework plus (BRFplus)
To check the business rule framework plus (BRFplus) run the following activity in Customizing for Master Data Governance, Central Governance
.
Note
If the system does not contain the Customizing application MDG_BS_ECC_SUPPLIER_WF_CUSTM export it from client 000 using transaction SCC1
.
Note
To copy the content of the decision table GET_AGENT, do the following:
Prerequisite: In transaction BRF+
under Personalize
the User Mode
Expert is selected.
Run transaction BRF+
in the source client and search for Name
MDG_BS_ECC_SUPPLIER_WF_CUSTM
.
In the search result list expand and open GET_AGENT with a double click.
Choose to download the data.
In your target client repeat the steps 1 and 2 to open the decision table GET_AGENT.
Choose to upload the data.
To assign processors to workflow step numbers run the following activity in Customizing for Master Data Governance, Central Governance
Assign processors, for example users or organizational units , for all change request types and their created workflow steps.
The following table shows an example of the change request types and their workflow steps.
Change Request Type | Workflow Step Number | Object Type | Object ID |
|---|---|---|---|
SUPPL1P1 | 01 Approval | O | OrgUnit-ID |
SUPPL1P1 | 04 Revision after Rejection | O | OrgUnit-ID |
SUPPL1P1 | 05 Subworkflow: Data Maintenance | O | OrgUnit-ID |
SUPPL1P1 | 06 Subworkflow: Approval | O | OrgUnit-ID |
SUPPL1P1 | 07 Decision: Activation Despite Discrepancy | O | OrgUnit-ID |
SUPPL2P1 | 01 Approval | O | OrgUnit-ID |
SUPPL2P1 | 04 Decision: Activation Despite Discrepancy | O | OrgUnit-ID |
SUPPL2P1 | 05 Revision after Rejection | O | OrgUnit-ID |
SUPPL5P1 | 01 Approval | O | OrgUnit-ID |
SUPPL5P1 | 02 Decision: Activation Despite Discrepancy | O | OrgUnit-ID |
SUPPL5P1 | 03 Revision after Rejection | O | OrgUnit-ID |
SUPPL6P1 | 01 Approval | O | OrgUnit-ID |
SUPPL6P1 | 02 Decision: Activation Despite Discrepancy | O | OrgUnit-ID |
SUPPL6P1 | 03 Revision after Rejection | O | OrgUnit-ID |
BPLP1 | 01 Processing | O | OrgUnit-ID |
BPLP1 | 02 Approval | O | OrgUnit-ID |
BPLP1 | 03 Revision after Rejection | O | OrgUnit-ID |
BPLP1 | 04 Revision after Rejection | O | OrgUnit-ID |
BPLP1 | 05 Decision: Activation Despite Discrepancy | O | OrgUnit-ID |
BPMP1 | 01 Processing | O | OrgUnit-ID |
BPMP1 | 02 Approval | O | OrgUnit-ID |
BPMP1 | 03 Revision after Rejection | O | OrgUnit-ID |
BPMP1 | 04 Revision after Rejection | O | OrgUnit-ID |
BPMP1 | 05 Decision: Activation Despite Discrepancy | O | OrgUnit-ID |
BPHP1 | 01 Processing | O | OrgUnit-ID |
BPHP1 | 02 Approval | O | OrgUnit-ID |
BPHP1 | 03 Revision after Rejection | O | OrgUnit-ID |
BPHP1 | 04 Revision after Rejection | O | OrgUnit-ID |
BPHP1 | 05 Decision: Activation Despite Discrepancy | O | OrgUnit-ID |
Note
If you intend to use MDG-S and MDG-C in parallel and you already have assigned the processors to the change request types for MDG-C, then nevertheless the assignment of processors to the change request types BPLP1, BPMP1, and BPHP1 has to be done in the Customizing activity Assign Processor to Workflow Step Number in BRFplus for Supplier
as described in this document.