Skip to Content

Workflow Configuration for Master Data Governance for Material

Applies To: SAP ECC 6.0 EHP 5 & onwards.


This document helps the SAP Technical consultants to understand the ‘Master Data Governance for Material: Workflow Configuration’. It explains how to configure workflow for ‘Master Data Governance for Material’. 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

  1. Overview on Master Data Governance Workflows
  2. Workkflows for Master Data Governance
  3. Configuring Master Data Governance
  4. Realization Phase 
    • Create a Supplier
    • Edit a Supplier
    • Block/Unblock a Supplier
    • Mark Supplier for Deletion
    • Process Multiple Supplier
  5. Related Contents
  6. 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

     The workflow used to implement Master Data Governance for Material is WS60800086.

     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 authority to approve or reject the change request.


     3. Activate the workflow after the changes.

     3. Configuring Master Data Governance

          To Proceed with the configurations, it is considered that workflow is created properly and proper agents are assigned to it who are going to take any action on the steps.

     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 Task.

          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

                    Material, this must be done for Dialog Processing (TS60807954) task.


     3. Configure Workflow Task.

          Path: Spro -> Cross Application components -> Process and Tools for Enterprise Applications ->

                       General Settings ->Process Modeling -> Workflow -> Other MDG Workflows ->

                       Define Workflow Step Numbers


     4. Configure Rule-Based Workflow.

          MDG for Material uses advanced workflow capabilities by combibing the SAP Business Workflow with tha SAP Business Rule Framework Plus tool.

          Path: Spro -> Cross Application components -> Process and Tools for Enterprise Applications ->

                      General Settings ->Process Modeling -> Workflow -> Other MDG Workflows ->

                      Configure Rule-Based Workflow

          Enter the change request type’s one after the another and choose the Start button.


          If the change request is not visible then,

          Export the content from client 000 and import it into your hub client.

               a. Call transaction BRF+ in the client 000.

               b. To switch to Expert mode from the Workbench  menu choose User Mode.

               c. Search for the object USMD_SSW_CATA_MAT01 using the Workbench menu by choosing

                  OpenObject. Use the following values to search:

      • Object Type CA: Catalog
      • Name: USMD_CATA_MAT*

               d. From the search result select USMD_SSW_CATA_MAT01

               e. To export the content from client 000, right -click on the application in the repository (not the

                   catalog entry) to open teh context menu and choose -> Tools–>XML Export.

                   Choose Include Referenced Objects (do not check Include Surrounding Application).

                   Generate the XMl file and download it. You can ignore the warnings on missong values not in the

                   value list.

                   The file size of each XML file should be approximately 101 kb. The system may require you to

                   assign the import to a transport.

               f. To Import the content into your MDG main client run the BRF+ transaction, from the Tools menu

                   choose XML Import, Select your XML File, and choose Upload file.

               g. Repeat these steps for all relevant change request types including:

      • MAT01 – Create Material
      • MAT02 – Edit Material
      • MAT06 – Mark Material for Deletion
      • MAT0A – Process multiple Material
      • MAT0B – Import Material

Define the steps in the Decision Table: DT_SINGLE_VAL_MAT01


Define the steps in the Decision Table: DT_USER_AGT_GRP_MAT01


Define the steps in the Decision Table: DT_NON_USER_AGT_GRP_MAT01


Follow the above procedures for all the change requests:

  • MAT02 – Edit Material
  • MAT06 – Mark Material for Deletion
  • MAT0A – Process multiple Material
  • MAT0B – Import Material


  • It is necessary to activate your new entries for each of the three decision tables.
  • The quickest way to allow users to participate in any workflow steps for testing purpose is to copy to default entries in the DT_USER_AGT_MAT01/02/06/0A/0B tables and change the entries as follows:
    • User Type: AG (Role)
    • User Value: SAP_MDGM (The MDGM role of PFCG/SU01)
  • If the system cannot find a processor for your change requsts check the background steps of the change requests workflow log to see if a work item with the description Set Status x for Change Request y is in process or in error. If this is the case regenerate the authorization profile of SAP_ALL or include USMD* authorization objects into the authorization for the user WF_BATCH.

     Complete the configuration for Data repliaction and test the application.

     5. Related Contents:

     6. Copyrights:

          © 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.

You must be Logged on to comment or reply to a post.
  • Hello,

    In Step 2: Assign Agents to the step “Approve Change Request”., you have changed it to User ASST_MAN.

    Why is that required??

    • Hi,

      Here ASST_MAN is a user which has authority to approve or reject the Change Request.

      So, whenever the change request will be created, ASST_MAN has to take above actions on it and the workflow will proceed accordingly.

      • Hello,

        Since WS60800086 is a rule based workflow template, we can just assign the approval user in the decision tables.

        I don't think we should change anything in WS60800086 workflow template.

        • I wanted to learn the concept through this application, so I used only one user.

          The simple way is to use this method to assign agents.

          You can assign rule: 60800140 to assign agents to the processors used in the workflow.

          I tried with both the methods of assignments and it doesn't make much difference in working.

  • Hello Ketan, I have gone through your post and it's nice. I have a requirement to trigger a workflow for every 'Create' and 'Change' events done on PA30. In other words for every record created or record changed done to an employee it should go through an approval process. Am wondering if i can use this your post for this requirement. i have 2 clarifications to get from your post, I wonder if you can help me.

    1. Can all update request on Employee data be put on hold till its approved.
    2. The business object for PA30 is BUS1006 not BUS2250 as specified in your post, How does this affect the workflow.
  • Hi Ketan,

    thanks a lot for your input.

    Currently I am implementing MDG on S/4HANA 1902 SP02. In our project is the strategy "fiori first". Therefor I will configure the workflow WS60800086 e.g. for my custom change request type ZSUF1P1 (Create supplier with SAP Fiori).

    Following configuration steps I have done:

    1. Create custom change request type (ZSUF1P1)
    2. Define steps for rule based workflow (BRF+)
    3. Configure rule based workflow (decision tables)
    4. Activate type linkage BUS2250
    5. Configure workflow tasks

    BUT I can not see my workitems in the Fiori App "Approva Master Data Extended". Why?

    In the SAP Business Workplace I can see my workitem (custom change request type) in the inbox and the workflow is working fine.

    Do you have an idea?

    Thanks and

    Best regards,