SAP TECHED ’07

TEST DRIVE SAP SRM-MDM CATALOG 2.0 MDM255 Exercise / Solution ADRIVIT BHATTACHARYA, SAP DAVID MARCHAND, SAP RAKESH MENON, SAP PARITOSH SHARMA, SAP

SAP TECHED ’07

1

TEST DRIVE SAP SRM-MDM CATALOG 2.0 SRM-MDM Catalog is the new Catalog Application bundled with SAP SRM since 2006, replacing previous catalog applications (partner solution, SAP CCM). SRM-MDM Catalog 2.0 has been launched to the market on August 20th 2007 (unrestricted shipment), after completing a successful 6 week-ramp-up program. Exercise Deep dive into SRM-MDM Catalog 2.0 and learn how to complete a typical catalog content management scenario for A to Z.

Process Flow Step 1 Prepare repository with reference data (Categories, Suppliers, Unit of Measurement, Product Groups, Images) Step 2 Import Supplier catalog and map automatically (using predefined map) Step 3 Import Supplier catalog and map manually. Create and manage attributes

Step 4 Manage relationships between catalog items. Step 5 Configure the end-user search user interface Step 6 Search your catalog with the end-user search user interface

Files and Folders Use the shortcut on the desktop and navigate to session folder MDM255 / Student_##, where ## is your assigned student number.

SAP TECHED ’07

2

Step 1: Prepare your repository with reference master data Purpose is to populate the secondary tables with relevant data, namely “reference data” to ensure data compliancy and automatic mapping when supplier catalogs will be loaded. This consists of looking after the following tables:

- Categories - Suppliers - Unit of Measurement - Product Groups - Images

Step 1: Prepare your repository with reference master data

Start MDM Data Manager from your desktop

Choose your repository from the MDM server.

MDM server must be “IWDF2321.wdf.sap.corp” Repository must be TECHED_STUDENT_## where ## is your student number. If you cannot find your repository on the drop down list, ask the speaker to check if the repository is uploaded and running.

SAP TECHED ’07

3

Connect to your repository

Make sure you have selected your TECHED_STUDENT_## repository Language is English (US) User is Admin Leave password blank (Note from Product Management: leaving password blank is not a recommend SAP “best practice”. It is just much more practical as I tend to forget all my passwords)

Check the repository does not contain any entries in the catalog items table

Repository does not contain any catalog items yet.

SAP TECHED ’07

4

Select Table “Categories” from the drop down box as shown

Select the taxonomy mode

Add child category to the root node “Categories”

SAP TECHED ’07

5

Build your taxonomy so that it looks as shown

Add node “Office Supplies” as child of “Categories” Add node “Computers” as child of “Categories” Add nodes “configure your computer!” and “computer components” as children of Node “Computers”

Switch to Records Mode

Select a category from the list

SAP TECHED ’07

6

Right click on that category you have selected

Go down to the list to “Edit Key Mappings”

Enter the key mapping for the remote key “UNSPSC”

Find the key from the Table below. Repeat this step for each end-leave category.

SAP TECHED ’07

7

Select the table Suppliers

Enter a new record for that table on the right pane

Edit key Mappings For each supplier, Edit key mappings and enter key = Supplier ID as value (based on screen shot above)

SAP TECHED ’07

8

Select Table UoM ISO Code from the list

Enter a new record for that table on the right pane

Edit key Mappings For each UoM, Edit key mappings and enter key = UoM ISO Code as value (based on screen shot above)

SAP TECHED ’07

9

Select Table Product Groups from the list

Enter a new record for that table on the right pane

Edit key Mappings For each Product Group, Edit key mappings and enter key = Material Group Code as value (based on screen shot above)

SAP TECHED ’07

10

Select table Images from the list

From the records pane, right click to add a new record

SAP TECHED ’07

11

Edit Data Group

Add Data Group as Child

As shown there

2 data groups have to be listed on that screen” HP and Lyreco.

SAP TECHED ’07

12

Select Data Group “HP”, then click on Add

Select the images from your student_## folder

Click on OK

SAP TECHED ’07

13

Import the images

Check the images in the Data Manager

SAP TECHED ’07

14

Step 2: Import Supplier catalog and map automatically (using predefined map) Purpose is to import a supplier catalog (ie: a list of catalog items from a supplier) in an XLS format into the MDM server, using the MDM Import Manager. We will be using a predefined map, to automate the mapping of the content directly into the appropriate fields of the repository.

Step 2: Import supplier catalog and map automatically (using map)

Start MDM Import Manager from your desktop

Select your student repository

SAP TECHED ’07

15

Select the XLS file to load from your student folder on the server

Select file “Content – Lyreco_Teched.xls”, click Open then Finish

Check the content of that XLS file in the Import Manager, by selecting the folder “Source Preview”

SAP TECHED ’07

16

To automate the mapping process, select a map from your student folder on the server

Select file “lyreco_content.map”, click Open

Save the map as “lyreco_content”

SAP TECHED ’07

17

Open the map you have just saved.

The system will automatically map the fields. This may take up to 30 seconds. No time to take a coffee here.

Select the folder “Import Status”

SAP TECHED ’07

18

Click on Execute Import

If the Execute button is greyed and cannot be clicked, ask the speaker to have a look and check the error message which is written in the Import Status folder. Most likely, this is due to a missing mapping of some values.

Content is imported successfully, if everything goes well.

Check the Import report

SAP TECHED ’07

19

Check the imported content in the Data Manager (Table Catalog Items)

SAP TECHED ’07

20

Step 3: Import Supplier catalog and map manually. Create and manage attributes Purpose is to import a supplier catalog (ie: a list of catalog items from a supplier) in an XLS format into the MDM server, using the MDM Import Manager.

Step 3: Import Supplier catalog and map manually. Manage Attributes

Start the Import Manager and select the file to load from your student folder on the server

Select file “configurable_computers.xls”

Switch the layout for a more usable environment

Select the source table

Select the table “configurableItems” as source. It corresponds to a folder in the XLS file

SAP TECHED ’07

21

Select the destination table

Select “catalog items” as destination table. You like to import the items from the XLS file as catalog items in the MDM repository.

Select the “map / fields values” folder

Map fields from the left pane to the corresponding ones on the right pane

SAP TECHED ’07

22

Once completed, check your mapping look as shown

Do not forget to map the values!

Values are mapped in the bottom panes for each selected mapped field. If key mappings have been entered properly, most of the values should map automatically.

Some fields require manual value mappings: - Item Type: SK2 has to be mapped to “configurable sales packages” - Manufacturer values have all to be added (select all values and click on Add) - PriceInfo has to be mapped with value “1, NULL, NULL”

If you are missing some values mapping, an explicit error message will be shown in the Import Status folder (check later at execute import time)

Add attributes and values while importing

4 attributes have to be added (starting with 1, 2, 3 and 4). To add an attribute, select it from the left pane, then click on Add

SAP TECHED ’07

23

Check the attribute parameters then click on OK

Select all values from the bottom left pane.

And click on Add

SAP TECHED ’07

24

Repeat the last 4 steps for all 4 attributes

Then select the folder “Match records”

Select “supplier part number” as the matching field

Select Action “create record”

SAP TECHED ’07

25

Execute Import

Eventually, an error message will appear if there are missing values mapping

Content is imported successfully.

Going back to the Source preview folder

Select the table “components” as source table.

SAP TECHED ’07

26

Using same techniques as just above, map the fields as shown

Do not forget to map the values as well! Thank you.

Match record by supplier part number in the Match record folder

SAP TECHED ’07

27

And Execute import from the Import Status folder

To manage the attributes that have been created and populated in previous steps, go to Data Manager, select the table Categories and select the Taxonomy Mode

Select category “Configure your computer!” from the toxonomy tree on the left pane.

Select an attribute from the list of the right and right click on it

Select Priority then select “highest” from the list. Repeat this step for all 4 attributes from the attributes list. By setting the priority to highest, the attribue will be made visible on the search user interface.

SAP TECHED ’07

28

Find now all the items imported in the Data Manager, table “catalog items” in records mode.

SAP TECHED ’07

29

Step 4: Manage relationships between catalog items. Purpose is to set up relationships between catalog items. Different types of relationships are possible:

- related items (sibling) - Substitutes (sibling) - Accessories (parent/ child) - Bill of Materials (parent / child) - Fixed sales packages (parent / child) - Configurable sales packages (parent / child)

All these relationships rely on the standard functionality “relationship” from the MDM Data Manager. Refer to the MDM255 documentation to understand all possible options.

Step 4: Manage relationships between catalog items

Start MDM Data Manager from your desktop

The relationships have been modeled in a txt file.

Check the file format from the provide documentation

Import Relationships file

SAP TECHED ’07

30

Select the file form your student folder on the server

Select file”relationships_computers.txt”

Import relationships

SAP TECHED ’07

31

Check the relationships in Data Manager (table catalog items, records mode)

Select one of the items from category “configure your computer” and double click on field “relationship”. Select folder “component item <main item>

SAP TECHED ’07

32

Step 5: Configure the end-user search user interface. Purpose is to configure the end user interface so that it is optimized for best usability depending on the content which has been imported and the business processes which have to be supported.

Step 5: Configure the end-user search user interface

Start MDM Console from your desktop

Connect to repository

In the Console Hierarchy pane, open the navigation tree and select the your TECHED_STUDENT_## repository. Open the context menu and choose Connect to Repository:

Enter user and leave password blank

Enter user Admin (leave password blank) and click on OK to connect to the repository:

SAP TECHED ’07

33

Click on the server name (IWDF2321) to view the list of repositories assigned to the server.

Find your student repository from the list and note the Port value assigned to it.

Define your URL to connect to the Repository from the Web (all in one line)

http://iwdf2321.wdf.sap.corp:50100/SRM-MDM/SRM_MDM? username=User1&password=&server=IWDF2321&port=PORT &catalog=YOUR_REPOSITORY&uilanguage=EN &datalanguage=EN&namedSearch= Replace PORT by the value found in previous step, and YOUR_REPOSITORY by your TECHED_STUDENT_REPOSITORY. Do not mess up. If you mess, it does not work. Note: even you do not mess up, it may not work either.

Example of URL that works

http://iwdf2321.wdf.sap.corp:50100/SRM-MDM/SRM_MDM? username=User1&password=&server=IWDF2321&port=2200 &catalog=TECHED_TEST&uilanguage=EN &datalanguage=EN&namedSearch=

Try your URL The screen that appears is the default configuration for the user interface. In following steps, we are going to configure the user interface so that it looks a bit different, and be more usable considering the content which has been imported.

Open the configuration screen

Link: http://iwdf2321.wdf.sap.corp:50100/SRM-MDM/SRM_MDM

SAP TECHED ’07

34

Enter the server name IWDF2321. No Server password. Click on Connect

Enter your strudent repository code in the Repository field. Enter Master as User Name (case sensitive) Leave password blank (yes I know, there should be a password)

Select User1 from the drop-down list

SAP TECHED ’07

35

Configure the general folder as shown

SAP TECHED ’07

36

Configure the customize display folder as shown (context view)

SAP TECHED ’07

37

Configure the customize display folder as shown (compare view)

SAP TECHED ’07

38

Configure the Customize Search folder as shown

SAP TECHED ’07

39

Step 6: Search your catalog with the end-user search user interface. Purpose is to get familiar with the v2.0 end-user interface, understand the different search methods (keyword, advanced, category browsing, attributes refinement) and be exposed to the new functionalities (relationships, shopping lists, etc…)

Step 6: Search you catalog with the end-user search user interface

Using Internet Explorer, start your URL (as configured in step 5)

http://iwdf2321.wdf.sap.corp:50100/SRM-MDM/SRM_MDM? username=User1&password=&server=IWDF2321&port=PORT &catalog=YOUR_REPOSITORY&uilanguage=EN &datalanguage=EN&namedSearch= Replace PORT by the value found in previous step, and YOUR_REPOSITORY by your TECHED_STUDENT_REPOSITORY.

Initial screen of the user interface

SAP TECHED ’07

40

Keyword search: enter a keyword

And check the results: found 6 items.

SAP TECHED ’07

41

Context Display Mode

SAP TECHED ’07

42

Details of an item

Shopping Cart Preview

SAP TECHED ’07

43

Search the catalog by browsing the category list

Refine the search by selecting values from the attributes

SAP TECHED ’07

44

After refinement, 2 items found

SAP TECHED ’07

45

Check details of the item.

SAP TECHED ’07

46

This item is of item type configurable sales package. Price is calculated based on the assigned components.

Shopping cart preview

Header item with children assigned. Total price is $2000 calculated based on component prices * quantity.

SAP TECHED ’07

47

Some items can be removed from the bundle in the shopping cart preview

Total price will be recalculated after removal of optional item.

SAP TECHED ’07

48

Any item can be assigned to a shopping list

Create a shopping list

SAP TECHED ’07

49

Shopping lists can be called from the dedicated folder

Shopping lists are masks in the MDM Data Manager (table masks)

SAP TECHED ’07

50

Advanced search folder

Search Criteria Folder

SAP TECHED ’07

51

Selected items can be compared

This marks the end of the exercise.

SAP TECHED ’07

52

SAP TECHED ’07

53

Copyright 2007 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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 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 scompleteness 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