Applies To: SAP ECC 6.0 EHP 5 & onwards.
Summary:
This document helps the SAP Technical consultants to understand the ‘Master Data Governance for Suppliers: Workflow Configuration’. It explains how to configure workflow for ‘Master Data Governance for Supplier’. Any suggestions and improvements towards this document will be always welcome.
Author: Ketan D. Badnore
Company: Larsen & Toubro Infotech Ltd.,
Created on: 5 May 2012
Author Bio:
Ketan D Badnore, a SAP Technical Consultant, is an employee of Larsen &Toubro InfoTech Ltd.
He is associated with Larsen & Toubro InfoTech Ltd, since March 2011 and has experience of 14 months.
Table of Contents
- Overview on Master Data Governance Workflows
- Workkflows for Master Data Governance
- Configuring Master Data Governance
- Realization Phase
- Create a Supplier
- Edit a Supplier
- Block/Unblock a Supplier
- Mark Supplier for Deletion
- Process Multiple Supplier
- Related Contents
- Copyright
1. Overview on Master Data Governance Workflows
Managing & Maintaining Master Data has become a major challenge for all customers today. Lack of transparency in roles & responsibilities for creating & approving changes in master data, manual work towards changes in master data have to be communicated to specialist. Along with this, Business need is to have single source of truth & high quality data.
SAP Master Data Governance (MDG) which delivers out of the box governance is the solution to the above challenges. SAP MDG is an extension of SAP Business suite which is for governing domain specific data like Material, supplier, customer, also ensures high quality & correct master data. This article gives you a detailed view of Workflow Configuration needed to achieve Governance over Supplier Master Data.
MDG is tightly integrated with the SAP Business Suite and thus uses the existing Process logic of SAP. SAP Delivers Standard Workflows which can be again integrated with MDG, thus avoiding any manual requests, follow ups and it builds a sense of Responsibility and Accountability across various business users within the system. One can either you a Standard workflow or customize this to business Requirements or build his own workflow to achieve Governance of Data.
2. Workflows for Master Data Governance
There are 5 Workflows for each activity:
- Create a Supplier (WS60800041)
- Edit a Supplier (WS60800048)
- Block/Unblock a Supplier (WS60800059)
- Mark Supplier for Deletion (Ws60800068)
- Process Multiple Supplier (WS60800095)
Workflow 1: Create a Supplier
1. Workflow will be executed after triggering the 'Created' event from the Business Object
'BUS2250'.
So activate the event linkage.
Go to Basic Data and switch to Start Event tab and activate the event.
2. Assign Agents to the step 'Approve Change Request'.
This step is to approve or reject the change request which is getting generated and will
be processed
by the Master Data Specialist having the
authority to approve or reject the change request.
3. Similarly assign agents to the steps 'Activate Change Request', 'Process Contact Person',
'Rework After Rejection'.
4. Sub-workflow is used to check the company code and purchasing organization group.
Workflow: WS60800042.
Assign agents who are going to take action on the steps.
Click on the icon to Create Agent Assignment and add agents who are going to take action.
5. After adding agents to all the nedded steps and activate the workflow.
6. Similarly assign agents to the other workflows used to Edit Supplier, Block/Unblock Supplier,
Mark Supplier for Deletion and Process Multiple Supplier.
3. Configuring Master Data Governance
To Proceed with the configurations, it is considered that all the five workflows are created properly and proper agents are assigned to it who are going to take any action on the steps and also for the sub-workflow which is used to check the company code and purchasing organization group for the supplier.
The following are the configuration needed:
1. 1. Activate the Linkage type.
Path: Spro -> Cross Application components -> Process and Tools for Enterprise Applications ->
General Settings ->Process Modeling -> Workflow -> Activate Linkage Type
Transaction: SWETYPV.
Ensure that one object type BUS2250 has the following settings:
Event: Created
Receiver Type: (Blank)
Type Linkage Active: Yes
The type linkage indicatoe must not be active for all other receiver types of object type BUS2250 and event Created.
This receiver type is defined via the receiver is defined via receiver type function module USMD_WF_REVEIVER_TYPE.
2. Configure Workflow Tasks.
Path: Spro -> Cross Application components -> Process and Tools for Enterprise Applications ->
General Settings ->Process Modeling -> Workflow -> Configure Workflow Tasks
Transaction: USMD_OOCU
a. Go to application components CA-MDG-AF and choose Assign Agents.
b. All activities (denoted by TS*) that are not set as Background Task need to be set to General
Task. To do so, select tha activity, choose Attributes, and change to General task. For MDG
Supplier, this must be done for the Approve Change Request (TS75707980) and Revise
Change Request (TS75707981) activities.
c. Repeat the procedure for all non-background activities within the CA-MDG-APP-BP and
CA-MDG-APP-SUP application components, at least for TS60808007 (Process Change
Request), TS608080004 (Change Request Approval) and TS60807991 (MDGS Process
Contact Person).
3. Define Workflow Step Numbers.
Path: Spro -> Cross Application components -> Process and Tools for Enterprise Applications ->
General Settings ->Process Modeling -> Workflow -> Other MDG Workflows ->
Define Workflow Step Numbers
4. Assign Processors to Workflow Step Numbers.
Path: Spro -> Cross Application components -> Process and Tools for Enterprise Applications ->
General Settings ->Process Modeling -> Workflow -> Other MDG Workflows ->
Assign Processors to Workflow Step Numbers.
Complete the Configuration for Data Replication and test the application.
4. Realization Phase
- Create a Supplier
- Edit a Supplier
- Block/Unblock a Supplier
- Mark Supplier for Deletion
- Process Multiple Supplier
Scenario 1: Create Supplier
When the change request is being created to create a supplier, a work item is getting created and assigned to the user who has the authority to approve or reject that request.
On execution of the work item from the SAP Business Workplace, the associated workflow will be executed and process according to the workflow.
The status of the change request in the data base is getting updated while executing the workflow.
After the creation of the change request, to see the change request status, click on show my request and click on workflow log after highlighting the change request.
Final check is approved; we can view the data in the database tables.
Scenario 2: Change Supplier
If there is any need to edit the supplier’s data, the change request is being created to change a supplier, a work item is getting created and assign to the user who has the authority to take action on it.
On execution of the work item from the SAP Business Workplace, the associated workflow will be executed and processed according to the workflow.
We can track the status of the change request in the workflow log.
After Successful completion the database tables are getting updated.
Scenario 3: Block / Unblock Supplier
The change request is being created to block or unblock a supplier. A work item is getting created and assigned to the user who has the authority to take action on it.
On execution of the work item from the SAP Business Workplace, the associated workflow will be executed and process according to the workflow.
We can track the status of the change request in the workflow log.
After successful execution the database tables are getting updated.
Scenario 4: Mark Supplier for Deletion
The change request is being created on marking a supplier for deletion. A work item is getting created and assigned to the user who has the authority to take action on it.
On execution of the work item from the SAP Business Workplace, the associated workflow will be executed and process according to the workflow.
We can track the status of the change request in the workflow log.
After successful execution the database tables are getting updated.
Scenario 5: Process Multiple Supplier
The change request is being created to process a multiple supplier. A work item is getting created and assigned to the user who has the authority to take action on it.
On execution of the work item from the SAP Business Workplace, the associated workflow will be executed and process according to the workflow.
We can track the status of the change request in the workflow log.
After successful execution the database tables are getting updated.
5. Related Contents
http://wiki.sdn.sap.com/wiki/display/SAPMDM/SAP+Master+Data+Governance
http://help.sap.com/erp2005_ehp_05/helpdata/EN/3e/b67a9facd34cb09ce87e3bc24b4c52/content.htm
http://help.sap.com/erp2005_ehp_05/helpdata/en/c6/472d8078e440c28ebc65e71ed5c620/content.htm
6. Copyright
© Copyright 2012 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SA AG. The information contained herein may be changed without any prior notice. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
- SAP Managed Tags:
3 Comments
