Applies to

SAP Master Data Governance, as of SAP ERP 6.0 Enhancement Package 5. For more information, visit the Master Data Management homepage.

Summary

The main purpose of this article is to show how to implement a simple scenario of Master Data Governance for supplier and portray MDG capabilities. A basic step by step guide to implement data governance over the vendor master tables LFA1, LFB1, LFM1 etc.

Author:        Goutham Kanithi

Company:    Mahindra Satyam

Created on:  10 December 2011

Author Bio

 

Goutham Kanithi has been associated with Mahindra Satyam for 15 months and has been a part of MDM practice. He is skilled in SAP MDM, Java, J2EE and completed his Bachelor’s degree in Electronics and Communication Engineering

Table of Contents

1.        Business Scenario

2.        Prerequisites

3.        Configuration of MDG for Supplier

3.1      Activation of the data model

3.2      Importing the predefined content for supplier

3.3      Data Modeling.

3.4      UI Modeling.

3.5      Data Quality and Search.

3.6      Process Modeling.

3.6.1      Configuring Change Requests.

3.6.2      Configuring Workflows.

3.7      Customer Vendor Integration (CVI) for MDG for Supplier

3.7.1      Activate PPO Requests for Platform Objects in the Dialog

3.7.2      Activate Creation of Postprocessing Orders.

3.7.3      Activate Synchronization Options.

3.7.4      Set BP Role Category for Direction BP to Vendor

3.7.5      Define BP Role for Direction Vendor to BP

4.        Working with Master Data Governance for Supplier

5.        Related Content

6.        Copyright

1.    Business Scenario

Proper maintenance of Master Data is a big challenge in present business environments. Customers are facing challenges where there is no governing body to manage master data. No clearly defined roles and responsibilities for creating and approving master data. No transparency and visibility on who has done what. Lot of manual work where the request and reasons for new or changed master data had to be communicated by phone or email to master data specialists. Follow up processing by certain specialist have to be manually triggered. The whole process is time consuming. Need for single source of truth and data quality is the top priority. Data has to be replicated to SAP and Non-SAP systems.

SAP Master Data Governance (MDG) which delivers out of the box governance is the solution to the above challenges. SAP MDG is a domain specific, embedded MDM solution for SAP Business Suite to ensure data quality and regulatory compliance. Currently MDG is offered for material, supplier, financial and customer master data. This article gives you a detailed view of MDG for Supplier configuration and working.

2.      Prerequisites

·        You are working on ECC 6.0 EHP 5 or higher

·        You have installed the software component SAP Business Suite Foundation (SAP_BS_FND 702).

·        You have activated the following business functions

o    Master Data Governance, Generic Functions (MDG_FOUNDATION)

o    Master Data Governance for Supplier (ERP) (MDG_ERP_SUPPLIER)

o    Business Foundation for Services for Supplier (CA_SUPPLIER_SOA)

·        You are assigned to the following roles

o    SAP_BC_TREX_ADMIN

o    SAP_QAP_ESH or SAP_ESH_LOCAL_ADMIN if it is not available.

o    SAP_MDGS

·        NWBC services are activated

·        Webdynpro services are activated

·        Technical configuration of Embedded search is done with TREX version 7.10.40.00 or higher

3.      Configuration of MDG for Supplier

For configuring MDGS execute transaction code MDGIMG in SAP GUI

3.1      Activation of the data model

We have to activate Business partner (BP) data model in General settings -> Data Modeling -> Edit Data Model

3.2      Importing the predefined content for supplier

As MDG has pre defined content for supplier, we only need to import that content.

Select Master Data Governance for Supplier in the dropdown and perform the following activities.

Import Predefined Change Request Types

Activate the Business Configuration set

Import MDG Outbound Service. Activate the BC set

Import Predefined Field Modification Criteria for Transaction BP Using MDGS. Activate the BC set

Import Predefined Workflow Dependent Checks. Activate the BC set

3.3      Data Modeling

We can view the data model attributes and entities, check and edit the mapping of active and staging area in this area

But for our scenario, we don’t need to do customization; we will use the data model which is already defined.

To assign internal key with a prefix, General settings -> Data Modeling -> Define Prefixes for Internal Key Assignment

3.4      UI Modeling

We don’t need to configure UI for Supplier. UI is already defined

3.5      Data Quality and Search

We define and configure the search applications in this area.

Define Search applications in General settings -> Data Quality and Search -> Define Search Applications

Define Search object connector template in General settings -> Data Quality and Search -> Create Search Object Connector Templates

Assign the created search object connector template to the object type in General settings -> Data Quality and Search -> Assign Search Object Connector Templates to Object Types

Open the Connector Administration Cockpit in Customizing for SAP NetWeaver under Search -> Embedded Search -> Modeling, Administration, and Monitoring -> Open Administration Cockpit

A web browser will be opened as shown above, where you have to create connector for the MDG Business partner in Template modeler.

And in the Administrator cockpit select schedule indexing in actions tab and activate immediate indexing. Indexing starts and status is shown as active after indexing is done.

3.6      Process Modeling

Change requests and workflows configurations are available in process modeling.

3.6.1      Configuring Change Requests

As we already imported the change request types, we don’t need to configure the change requests. We only need to define the priority and reason for change request.

Define change request priorities in General settings -> Process Modeling -> Change Requests -> Define Priorities for Change Requests

Define change request reasons in General settings -> Process Modeling -> Change Requests -> Define Reasons for Change Requests

Define change request rejection reasons in General settings -> Process Modeling -> Change Requests -> Define Rejection Reasons for Change Requests

3.6.2      Configuring Workflows

We use five workflows for MDG supplier which are predefined

Activate type linkages in General settings -> Process Modeling -> Workflow -> Activate Type Linkage

Check for Object type BUS2250, event should be created and Receiver type should be blank.

Assigning agents to the workflow tasks is done either in Workflow Builder or General settings -> Process Modeling -> Workflow -> Configure Workflow Tasks

Execute transaction code SWDD for Workflow Builder

Open the workflow for Create Supplier – WS53100044

Select a step in the navigation area

Check Agent assignment and Background processing in task properties.

If the task is not a background task, agent should be assigned to process the task. Hence if the Background processing is not preceded by a green color square, then Agent Assignment should be done by clicking on the icon which is present before Agent assignment.

Click on attributes, select ‘General Task’ and save it.

Follow the same procedure for every task in all the five workflows for supplier.

After making changes to each workflow, don’t forget to activate the workflow.

This is only making the task as general task. The actual assignment of processors is done in BRFplus as shown below.

Open object MDG_BS_ECC_SUPPLIER_WF_CUSTM in BRFplus

Assign an agent for each workflow step, like the example below.

 

Note that the users must be assigned to SAP_MDGS role.

Assign the workflow steps in Create Supplier (SUPPL01) to the following profiles in the company

WF step 1. Approval – Second central master data specialist

WF step 2. Decision: Maintain Contact – Central master data specialist

WF step 5. Subworkflow: Data Maintenance – master data specialist for company code data or purchasing organization data

WF step 6. Subworkflow: Approval – second master data specialist for company code data or purchasing organization data

Similarly assign workflow steps for the other four workflows to different profiles.

You can also define your own rules to assign agents for purchase organization and company code data as shown below, by selecting edit row option.

After assigning agents to all the five change request types, don’t forget to save and activate.

3.7      Customer Vendor Integration (CVI) for MDG for Supplier

For CVI navigate through Master Data Governance for Supplier -> Enterprise Services for ERP -> Set up Customer Vendor Integration for MDG for Supplier

3.7.1      Activate PPO Requests for Platform Objects in the Dialog

3.7.2      Activate Creation of Postprocessing Orders

3.7.3      Activate Synchronization Options

3.7.4      Set BP Role Category for Direction BP to Vendor

Here we define vendor link for business partner role. We can define which BP role categories enable vendor integration in the direction from the business partner to the vendor

These roles will be assigned to the suppliers we create.

3.7.5      Define BP Role for Direction Vendor to BP

Here we will assign BP roles to the account group for the vendor master record in which the business partner is to be created when processing the vendor.

These are the account groups and BP roles combinations, which we will need, while creating suppliers.

4.      Working with Master Data Governance for Supplier

Working with MDG for Supplier is explained in detail in Whitepaper – Governance Over Supplier Master Data Using SAP MDG – Part 2

5.      Related Content

(for ECC 6 Ehp06) : Master Data Governance – SAP Documentation

http://www.sap.com/solutions/enterprise-information-management/master-data-management/master-data-governance/index.epx

http://help.sap.com/erp2005_ehp_05/helpdata/EN/3e/b67a9facd34cb09ce87e3bc24b4c52/content.htm

http://www.sdn.sap.com/irj/boc/master-data-governance

http://www.sdn.sap.com/irj/sdn/master-data-governance?rid=/webcontent/uuid/f0801486-9562-2e10-54b1-9c123497f1a7

http://wiki.sdn.sap.com/wiki/display/SAPMDM/SAP+Master+Data+Governance

 

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 SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.

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.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

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.