consolidate the master data with sap mdm · new suppliers and are candidates to be uploaded into of...

SAP MDM CONSOLIDATION

0

CONSOLIDATE THE MASTER DATA WITH SAP MDM

Exercise / Solution

SAP MDM CONSOLIDATION 1

Consolidate Suppliers and Products

The SAP Discovery System uses SAP MDM to store the suppliers and products master data of the “CoolCorp” company. The supplier and product master data are used by the purchase order business scenario. In this exercise, we will assume that the “CoolCorp” company acquired another company named “SmartComp” , as a consequence a new list of suppliersand products needs to be consolidated into MDM. The following steps describe how the suppliers and products of the “SmartComp” will be extracted from Excel files and mapped to the CoolCorp MDM repository and uploaded to SAP MDM.

Prerequisites Previous basic knowledge of MDM data modeling The ESA-BOX repository is loaded and running. To verify, go to this link , if you see a list of suppliers then

your repository is loaded and running: http://iwdfvm2160:51000/webdynpro/dispatcher/local/ESADiscoveryWD/SuppliersListApp?productId=T20060&productQuantity=3600&productName=COOL%20GIZMO

If ESA-BOX repository is not loaded and running, take steps in Quick Guide (under Prerequisites on SDN.) Download required files from SDN under SAP Discovery System > Introductory Exercises > “Download

MDM files”. Extract the file to Desktop, folder name MDM. Move this folder to Desktop of the Discovery System.

Part 1: Import Suppliers into the MDM Supplier table

The first part of this exercise is to import the Suppliers from the “SmartComp” company to the “CoolCorp” company.The table Supplier, in the MDM repository, holds a list of suppliers with their details. The mapping setting of the import manager tool determines which suppliers in “SmartComp” company already exist in “CoolCorp” company.

Procedure1. “SmartCorp” suppliers master Excel files:

a. Log into your Discovery System directly or using Remote Desktop Connection.b. Under your Desktop > MDM folder, you have two Excel files named suppliersToImport.xls and

productsToImport.xlsc. The Discovery System does not include MS Excel. If you were to have Excel, opening suppliersToImport.xls

would show you the below list of Suppliers of the SmartComp” company. The first two suppliers already exist inside the MDM repository of the “CoolCorp” company. It means that during the upload process, MDM has to determine that these suppliers are duplicates and not upload them. However the last two Suppliers in the list are new Suppliers and are candidates to be uploaded into of the “CoolCorp” MDM repository.

2. Build the mapping of the Supplier Master Data between the SmartComp Excel files and the CoolCorp MDM repository. In this section, you will map the Excel columns to the MDM repository fields of the Supplier table.


2

a. Open the SAP MDM Import Manager tool (shortcut is on the desktop)b. Connect to MDM Repository window: Choose repository “ESA-BOX”, User Name “Admin” and do not enter

a password, click “Next” See picture below.

c. Choose type “Excel”, Choose Client system “PROJECT”, select the file supplierToImport.xls from your hard disc. In case you chose the MDM as a client system, you will not be able to see the Key mapping field in the import mapping tab.Files located on Discovery Server in folder “D:\Workshop Exercise\MDM”


3

d. The Import Manager tool opens and you see the “Source Hierarchy” that is the supplier Excel file (SmartComp company data) and the “Destination Hierarchy” that is the MDM repository (CoolCorp company data)

e. Expand the “Sheet1$” node in the source tree and select from the drop-down “Sheet1$”. Expand the “Suppliers” node in the destination tree and select from the drop-down “Suppliers”. See picture below:

f. You have to clone the SupplierID field of the source because you will need to map the SupplierID twice. To clone the SupplierID , stand on the SupplierID node of the source tree, right-click and select “Clone Field”. See picture below:


4

g. Now select the tab “Map Fields/Values”. It is the tab where you map the Excel fields to the MDM repository fields. See picture below.

h. You can start mapping all the fields. Starts by mapping the “SupplierID <Clone>” field to the [Remote Key] destination fields using “Map” button. Then map all the other fields using “Automap” button. Note that you could make further adjustments using “Unmap” and “Map” selectively. See picture below:

i. Map field value. Select the “SupplierStateCountry”, map the “USA” source value to the “USA” destination value, see picture below:


5

j. Select the tab “Match Records” tab. Our matching rule is simple. We are recognizing two suppliers as identical if they have the same ID. Select SupplierID[DF] from the “Mapped destination fields” list , click the “Add” button. See the picture below to see the result:

k. The import manager tool detects that 2 suppliers have no match (D9999 and D9991) and 2 suppliers have an exact match (same supplierID). Now you have to decide what to do when there is an exact match or no match. When there is no match it means that it is a new supplier that needs to be added our repository. To do so select “Create” from the “Default Import Action” command for “Match Type” equal to “None”, see the picture below:

In case the match is “Exact”, it means that the supplier already exists and you don’t need to import the suppliers, leave the action as “Skip”.


6

3. Execute Supplier Import to the Supplier table:Now that we have mapped the entire fields, set the matching field and the import action, you can move to the “Import Status” tab. Make sure that it is written “Action items: Ready to import”.

Click on the execute icon “!” in the menu, see picture below:

Save your mapping as “SupplierFromExcel_toSupplierTable” by clicking on File -> Save.Exit the MDM Import Manager.

Result:

Open the SAP MDM Data Manager tool, select the supplier table and you will see the 2 suppliers (NEW SUPPLIER2 and NEW SUPPLIER1) that where imported from the “SmartComp” Excel file to the “CoolCorp” MDM repository supplier table


7

Part 2: Import Suppliers into the SupplierProductLink table

Now you have to import the Suppliers into the SupplierProductLink table. The table SupplierProductLink is a lookup table used as a product field in the product table. It is used in order to assign different product ids per product depending of the supplier. Each product’s supplier uses a different product id, we call this product id the “External product id”.Now that you are more familiar with the process of mapping , this part will be less descriptive.

a. Open the MDM Import Manager

b. Choose type “Excel”, Choose Client system “PROJECT”, select the file suppliersToImport.xls from your Desktop.

c. Expand the “Sheet1$” node in the source tree and select from the drop-down “Sheet1$”. Expand the “Suppliers” node in the destination tree and select from the drop-down “SupplierProductLink”.

d. You have to clone the SupplierID field of the source because you will need to map the supplierID twice. To clone the SupplierID , stand on the SupplierID node of the source tree, right-click and select “Clone Field”.

e. Now select the tab “Map Fields/Values”. This is the tab where you will map the Excel fields to the MDM repository fields. You can start mapping all the fields. Starts by mapping the “SupplierID <Clone>” field to the [Remote Key] destination fields. And then the SupplierID field to the Supplier[DF] destination field.

f. Map field value. Select the “SupplierID”. Click on the “Automap” button that is between the “source values” and the “destination values”. See picture below:

g. Select the tab “Match Records”. Our matching rule is simple. Select Supplier[DF] from the “Mapped destination fields” list , click the “Add” button.

h. The import manager detects that 2 suppliers have no match (D9999 and D9991) and 2 suppliers have an exact match (same supplierID). Now you have to decide what to do when there is an exact match or no match. When there is no match it means that it is a new supplier that needs to be added our repository. To do so select “Create” from the “Default Import Action” command when “Match Type” equal to “None”. See picture below:


8

i. Execute Supplier Import to the Supplier table:You can move to the “Import Status” tab. Make sure that it is written “Action items: Ready to import”.

Save your mapping as “SupplierFromExcel_toSupplierProductLinkTable”

Result

Open the MDM Data Manager tool, select the SupplierProductLink table, you will see the 2 new Suppliers D9991 and D9999.


9

Part 3: Import Products into the MDM Products table

In this part you map and import the products of the “SmartComp” company to the “CoolCorp” MDM repository. You are importing also the relation between product and supplier. This relation shows which suppliers supply a specific product and in this relation you have a field called “ext_productId” that holds the product id used by each supplier.

1. “SmartCorp” products master data Excel files:

a. If you were to have Excel, opening productsToImport.xls would show you the below list of Products of the SmartComp” company. It shows also the relation between supplier and product. For example the product APPLIANCE is supplied by the supplier GN-103 (AT&G) and by the supplier C8000. In the MDM repository, APPLIANCE already exist and is already supplierd by supplier GN-103 (AT&G) but is not supplied by supplier C8000. Appliance has a different “external product id” for each supplier.You have also 2 new products. “TOY1 new” is supplied by C8000 and “TOY2 new” is supplied by D9999 (supplier that was added previously)

2. In this section, you build the mapping of the Product Master Data between the SmartComp Excel files and the CoolCorp MDM repository. , you will map the Excel columns to the MDM repository fields of the Products table.

a. Open the SAP MDM Import Manager tool (shortcut is on the desktop)b. Choose type “Excel”, Choose Client system “PROJECT”, select the file productsToImport.xls from your hard

disc.

c. Expand the “Sheet1$” node in the source tree and select from the drop-down “Sheet1$”. Expand the “Products” node in the destination tree and select from the drop-down “Products”. See picture below:


10

d. You have to clone the Internal product id field called Int_ProductID of the source because you will need to mapit twice. To clone the Int_ProductID, stand on the Int_ProductID node of the source tree, right-click and select “Clone Field”.

e. Now select the tab “Map Fields/Values”. This is the tab where you will map the Excel fields to the MDM repository fields. Map all the fields like in the picture below.

Map the Int_ProductID<clone> field to the [Remote Key].

Map SupplierID to “SupplierLink”. SupplierLink field is a lookup table where each supplier holds his own product id (called external product id).When you stand on the SupplierID field , make sure that the all the source values are mapped to destination values.

f. Map “Ext_ProductID” to “ExternalProductID” and “Int_ProductID” to InternalProductID [DF]” and click Automap to map the rest of the Fields.


11

g. Since SupplierLink is a “Lookup” field, it points to the table SupplierProductLink where for each supplier we a specific product id (called “external product id”). The field that holds the “external product id” is called qualifier. You have to set some parameters for being able to update the SupplierLink field. Right-click in the SupplierLink field, select “Set Qualified Update”, then select Update as in the picture below.

h. The following window opens. Here you decide what to do if you have a new product’s supplier like C8000 that is a new supplier for product APPLIANCE. If it is a new product’s supplier then you want to create it , set “New links” equals to “Create”. If the product’s supplier already exists, we will update the qualifier fields (external product id). Set “Existing links” equals to “Update(All Mapped Qualifiers)”. Set the setting like in the picture below, then hit “OK”:

Note: Since every supplier supplies one set of the same product, there is no need to set the ExternalProductID as a matching qualifier. If the same supplier has different products ID’s for the same source product, Matching qualifiers field should be set with ExternalProductID. (For additional information please refer to MDM 5.5 SP3 Import Manager Reference Guide”


12

i. Now you can move to the next tab “Match Records”, select the “internalProductID” as a matching field. For match type equal to “None”, set the import action to Create. This setting will create the products that exist in the source and not in the destination (like “TOY1 new” and “TOY2 new”).

ii. For Match Type equal to “Exact”, set the import action to “Update (All Mapped Fields)

i. Before importing the product data, go to the MDM Data Manager tool in order to see the data that exists before the import. Here in the picture below are the products and there suppliers before the import. Noticed that APPLIANCE is supplied by 4 suppliers (C1000, C1001, GN-103, GN-105)


13

j. Now you execute the import in the MDM Import Manager tool

Save your mapping as “ProductsFromExcel_toProductsTable”

Result:

Look again at the product data in the MDM Data Manager tool. You need to refresh the screen by reselecting the product table. Now you see that the APPLIANCE product is supplied by 5 suppliers. The supplier C8000 was supplying the product APPLIANCE for the “SmartComp” company, now supplier C8000 is also supplying APPLIANCE to the CoolCorp company.You have also 2 new products called “TOY1 new” and “TOY2 new”.“TOY1 new” is supplied by C8000 and “TOY2 new” is suppliers by D9999. D9999 is the new supplier that comes from “SmartComp” company.


14

Part 4: Run the Purchase Order business scenario and see the new data that was imported.

At the following link you can see the new product “TOY2 new” that can be supplied by “NEW SUPPLIER2”http://iwdfvm2160:51000/webdynpro/dispatcher/local/ESADiscoveryWD/SuppliersListApp?productId=T99991&productQuantity=3600&productName=TOY2%20new

At the following link you can see that the product “APPLIANCE” can now be supplied by “KONNOR”http://iwdfvm2160:51000/webdynpro/dispatcher/local/ESADiscoveryWD/SuppliersListApp?productId=T20000&productQuantity=3600&productName=APPLIANCE

Part 5: Information about the MDM Business Package for the SAP Enterprise Portal:

For your information, SAP has an Enterprise Portal business package for MDM withpredefined MDM iViews. The predefined MDM iViews are an easy way to search the repository from the Enterprise Portal UI and display the results. The connection from the portal to the MDM repository is used through a predefined MDM System where the host and port of the MDM repository is defined.

The picture below shows two predefined MDM iViews, the upper on is a MDM Search text iView and the lower one is a MDM result set iView. No programming has been involved to create this UI, it has been created from the Enterprise Portal by configurations.


15

Copyright 2005 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,

OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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 Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented

and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 in several other countries all over the world. 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.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages..

SAP assumes no responsibility for errors or omissions in these materials

consolidate the master data with sap mdm · new suppliers and are candidates to be uploaded into of...

Documents