SAP Master Data Governance, as of SAP ERP 6.0 Enhancement Package 5. For more information, visit the Master Data Management homepage.
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
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.
3. Working with Master Data Governance for Supplier.
3.1 Create Supplier.
3.2 Change Supplier.
3.3 Process multiple suppliers.
3.4 Mark a Supplier for Deletion.
3.5 Blocking and Unblocking a Supplier.
4. Related Content.
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.
· You have NWBC Desktop client or web browser(NWBC for HTML).
· You have done all the configurations explained in Part 1.
3. Working with Master Data Governance for Supplier
Open the NWBC Desktop client. If you don’t have a desktop client, NWBC can be opened in HTML by executing the transaction code NWBC or else open a web browser and type url in the below format.
The Central master data specialist has to login with his credentials to create a change request
Select Supplier Master Data Manager and in the next window select Change requests
3.1 Create Supplier
Click on Enterprise search to search for the supplier before creating.
To create a supplier, central master data specialist initiates a search. Search results show if the trader exists
If the trader does not exist in our data, then a new supplier is created by clicking on create button.
Enter Organizational Data. We can check duplicates by clicking on duplicate check button.
Below is an example how “Duplicate Check” works.
Assign a Business Partner role
Enter Supplier General Data. Give a Unique supplier ID.
Enter Company Code Data
Enter Purchase organization data
Enter your comments in notes and attach files if any.
Clicking on submit button creates the change request
To see the change request status, click on show my change requests and click on workflow log after highlighting the change request.
The change request has to be approved by second central master data specialist.
He logs into his system and approves or rejects the change request.
If he approves the change request, the change request is further directed towards master data specialist for company code data and purchasing organization data. He can only edit that particular area which is assigned to him.
After he processes the request, it is forwarded to second master data specialist for approval of the changes made to company code data and purchasing organization data.
Once he approves, Change request is forwarded to central master data specialist, where he has to make a decision, process contact person.
We can see all the progress in workflow log at any time.
Final Check is approved at the end and we can view the data in BUT000, LFA1, LFB1, LFM1 tables
Execute transaction code se16 in SAP GUI connected to ECC.
Enter BUT000 and execute, where we can see the data which underwent a process of data governance is stored in BUT000 Business partner table
In LFA1 Vendor Master (General Section)
Similarly LFB1 Vendor Master (Company Code)
And LFM1 Vendor Master (Purchase Organization)
3.2 Change Supplier
If there is a need to edit a supplier’s data, A Master data specialist creates a change request. First a record has to be selected as shown above or search in enterprise search and click on change.
Make changes in the supplier’s data and submit
A second master data specialist reviews and approves or rejects the changes made in supplier data.
After the second master data specialist approves, decision on process contact person is made bymaster data specialist who created the request.
We can track the status of the change request in the workflow log. Here we can see final check approved status after decision on process contact person is taken.
We can see the changes made in all the four tables.
3.3 Process multiple suppliers
Below is the process how a Master data specialist create a request to process multiple suppliers at a time
Reason for changes and attachments if any
Specify objects which are to be changed. Click on specify objects for Supplier
To use mass change in process multiple suppliers tab, we don’t need to specify objects. For mass change we create a change request and assign this change request to the records selected in mass change.
Now master data specialist selects mass change in process multiple supplier tab and adds objects
Replace any value in search term 2 with test for the selected records
Check the existing values and replacing values
On clicking execute changes window pops up asking for change request number to be assigned. Here we have to assign change request created by the Master data specialist
To finalize the mass change, the master data specialist clicks on finalize processing
The change request is forwarded to second master data specialist for approval
We can see the workflow log for process multiple suppliers. Final check approved.
We can check the result of mass change in the tables
3.4 Mark a Supplier for Deletion
Master data specialist checks the required deletion flags in all the four tabs and submits
Request is forwarded to second master data specialist for approval. After approval the deletion flag is set
Deletion flag in LFA1:
You can check in LFA1 where deletion flag LOEVM and NODEL are set to ‘X’.
3.5 Blocking and Unblocking a Supplier
Select a supplier to block\unblock
Change request forwarded to second master data specialist for approval. Approval is done.
After approval purchasing block flag is set to ‘X’
We can see purchasing block flag is set to ‘X’ for Surya and Co.
4. Related Content
© 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.
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.