Set Up the Workflow

This section describes how to make the Customizing settings required to run the workflow for the approval process in MDG-C.

You define the workflow settings in Customizing for Master Data Governance, Central Governance under Start of the navigation path General Settings Next navigation step Process Modeling Workflow End of the navigation path .

Activate type linkage
To activate the type linkage, run the following activity in Customizing for Master Data Governance, Central Governance under General Settings Process Modeling Workflow Activate Type Linkage .

Ensure that the 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.

Note
To enter the receiver type function module or if you need to change the settings, mark the according line in the table and choose Goto Details .

End of the note.
Configure workflow tasks.
To configure workflow tasks, run the following activity in Customizing for Master Data Governance, Central Governance under General Settings Process Modeling Workflow Configure Workflow Tasks .
1. Go to application component CA-MDG-AF and choose Assign Agents.
2. 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.
3. Repeat the procedure for all non-background activities within the CA-MDG-APP-BP application component.
Check number of workflow steps
1. 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 General Settings Process Modeling Workflow Other MDG Workflows Define Change Request Step Numbers .
2. If you use the change request types delivered with MDG-C, the following workflow steps are delivered:
  - WS54300003. Step 0, 1, 2, 3
  - WS46000023: Step 0, 1, 2, 3, 4, 5
  - WS46000027: Step 0, 1, 2, 3, 4
  - WS60800095: 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 Master Data Governance for Customer Workflow Assign Processor to Workflow Step Number in BRFplus for Customer .

Note
If the system does not contain the Customizing application MDG_BS_ECC_CUSTOMER_WF_CUSTM export it from client 000 using transaction SCC1.

End of the note.
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.
1. Run transaction BRF+ in the source client and search for Name MDG_BS_ECC_CUSTOMER_WF_CUSTM.
2. In the search result list expand MDG_BS_ECC_CUSTOMER_WF_CUSTM Expression Decision Table GET_AGENT and open GET_AGENT with a double click.
3. Choose Additional Actions Export to Excel to download the data.
4. In your target client repeat the steps 1 and 2 to open the decision table GET_AGENT.
5. Choose Additional Actions Import from Excel to upload the data.
End of the note.

To assign processors to workflow step numbers run the following activity in Customizing for Master Data Governance, Central Governance Start of the navigation path Master Data Governance for Customer Next navigation step Workflow Assign Processor to Workflow Step Number in BRFplus for Customer End of the navigation path

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
CUST1P2	01 Approval	O	OrgUnit-ID
CUST1P2	04 Revision after Rejection	O	OrgUnit-ID
CUST1P2	05 Subworkflow: Data Maintenance	O	OrgUnit-ID
CUST1P2	06 Subworkflow: Approval	O	OrgUnit-ID
CUST1P2	07 Decision: Activation Despite Discrepancy	O	OrgUnit-ID

Note Note

The change request type CUST1P2 supports distributed workflow for customers. It is delivered with the business function Master Data Governance for Customer 7.0 Feature Pack.

End of the note.

Note Note

For the change request types CUSTL1 (lean request UI for ERP customers) and CUSTL1P2 (distributed workflow for ERP customers) that are also delivered with the business function Master Data Governance for Customer 7.0 Feature Pack processors are assigned to workflow step numbers in the same way.

End of the note.

Assign processors to workflow steps (Simple Workflow)

To assign the object ID of the organizational units to the workflow step number, run the following activity in Customizing for Start of the navigation path Master Data Governance, Central Governance Next navigation step General Settings Process Modeling Workflow Other MDG Workflows Assign Processor to Change Request Step Number (Simple Workflow) End of the navigation path

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
CUST2P1	01 Approval	O	OrgUnit-ID
CUST2P1	02 Decision: Activation Despite Discrepancy	O	OrgUnit-ID
CUST2P1	03 Revision After Rejection	O	OrgUnit-ID
CUST5P1	01 Approval	O	OrgUnit-ID
CUST5P1	02 Decision: Activation Despite Discrepancy	O	OrgUnit-ID
CUST5P1	03 Revision After Rejection	O	OrgUnit-ID
CUST6P1	01 Approval	O	OrgUnit-ID
CUST6P1	02 Decision: Activation Despite Discrepancy	O	OrgUnit-ID
CUST6P1	03 Revision After Rejection	O	OrgUnit-ID
CUSTHI01	01 Maintenance of Duplicate Entries	O	OrgUnit-ID
CUSTHI01	02 Approval (No Rejection)	O	OrgUnit-ID
CUSTHI01	03 Revision	O	OrgUnit-ID
CUSTHI01	04 Decision: Activation Despite Discrepancy	O	OrgUnit-ID
CUSTHI02	01 Approval (No Rejection)	O	OrgUnit-ID
CUSTHI02	02 Revision	O	OrgUnit-ID
CUSTHI02	03 Decision: Activation Despite Discrepancy	O	OrgUnit-ID
CUSTHI02	04 Revision of Address After Validation	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 Note

If you intend to use MDG-C and MDG-S in parallel and you already have assigned the processors to the change request types for MDG-S, then the assignment for the change request types BPLP1, BPMP1, and BPHP1 already is completed.

For all other MDG-C change request types the assignment has to be done in the Customizing activity Assign Processor to Change Request Step Number (Simple Workflow) as described in this document.

End of the note.