SAP SRM MDM Catalog 3.0 - (Data Loading) and UI Overview

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.
com
2010 SAP AG 1
SAP SRM MDM Catalog 3.0
(Data Loading) and UI Overview
Applies to:
SAP SRM MDM Catalog 3.0
Summary
This Document illustrates step by step procedure with example screenshots on How to set-up data loading
into SRM MDM Catalog Application and a brief overview on UI Manager.
The Document will provide best of knowledge and guidance to learn Initial Set-ups, Pre-requisite
configuration, Data Loading and Mapping exercise in SRM MDM Catalog Import manager.
Also this knowledge house will help to understand implications of certain changes in UI Manager.
At last this publication shows the testing part of Integration from MDM Catalog to SRM System with transfer
of Products / Services.
Additionally, the NOTES section provides certain interesting points to be noted and Automation
Re-usability of Mapping in SRM MDM Catalog
Extra carefulness while re-using Mapping in SRM MDM
Automatic Import functionality and set-up steps
Author: Chandan Roy Choudhury
Company: Fujitsu Consulting, Infosys Technologies, IBM
Created on: 26 Dec 2010
Author Bio
Chandan is currently Acting Project Manager on SAP SRM7.0 Implementation and
Functional Lead for SAP SRM7.0 Competency in IT-Consulting.
He is certified in SAP SRM and SAP MM, he has total 8+ years of experience in Consulting.
Chandan Started his career with Domain Experience in Automotive Industry IFB - was core
team member from IFB during ERP (SAP) Implementation by PWC. He has Global exposure
through client facing roles and specialization in SAP SRM by working with clients from US and Europe, was
awarded with Bravo' - the most prestigious award from IBM on Performance Recognition.
He proved to be a true leader while working in Infosys for account on 'Source to Pay' using SAP SRM - was
awarded 'Most Valuable Player' for Contribution and Team Management capability in the Organization
Chandan was engaged with SAP Labs being in Partnership with Infosys for SAP SRM7.0 Validation prior to
launch, had extensive involvement in Implementation of Prototype for Business Lines in Material and Service
Procurement, Supplier Collaboration, Contract Management etc. using SAP SRM7.0.
The contribution and effort was recognized from SAP Labs through award ' Best Performer of the year'.
Chandan Leaded the Team for Functional Upgrade in Business Line 'Strategic Sourcing' and 'SRM MDM
Catalog' Implementation using SAP SRM 7.0 for Major Healthcare industry in US
Currently consulting for company 'Fujitsu' and acting Project Manager for SAP SRM 7.0 Implementation in
Middle East. Scope of the implementation is entitled to Public Tendering, Registration of Supplier and
Supplier Self Service using SAP SRM7.0. Apart from Project Management Chandan presently holds the Role
for 'Functional Lead' for SAP SRM Competency in the consulting firm 'Fujitsu'
Academics: B.E in Mechanical Engineering, a 'Distinction' holder from university(VTU).
SAP SRM MDM Catalog 3.0 (Data Loading) and UI Overview
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 2
Table of Contents
Case Study: ........................................................................................................................................................ 3
Import Scenario Set-up and Steps ..................................................................................................................... 3
Start Mapping ................................................................................................................................................... 25
Match Records .................................................................................................................................................. 43
Import Status .................................................................................................................................................... 44
UI Change ......................................................................................................................................................... 47
Final Check (Integration from MDM to SRM) ................................................................................................... 49
Error handling and Loading a 2nd Supplier catalog file .................................................................................... 53
Error Handling ............................................................................................................................................... 57
Understanding the Import Status Tab ............................................................................................................. 62
OCI Mandatory Fields ....................................................................................................................................... 67
Notes ............................................................................................................................................................. 71
Related Content ................................................................................................................................................ 82
Disclaimer and Liability Notice .......................................................................................................................... 83

2010 SAP AG 3
Case Study:
Customer is interested for utilizing SAP software for preparing a Product/ Service Catalog to be used for
Business. Business Users should be able to choose intended product / service and compare them between
various suppliers for Price, Features and Images etc.
Customer would like to leverage SRM MDM Catalog3.0 software as part of SAP SRM7.0 Business Suite to
use for Catalog application, Additionally Strategic Sourcing department additionally wants to link the
Contracts (as Resulted from Sourcing Process) to the Products / Services in the Catalog System so that
Existing Contracts are utilized instead of ad-hoc purchasing , this will enable business to save cost and
maverick spending.
Customer would also like to explore the integration between the Catalog system and existing SRM/ECC
system.
Customer needs consulting to set up Data for MDM Catalog system and use the Catalog for Go-Live initially
for 2 Major suppliers and then Roll out to other Suppliers. In this fashion existing Punch-out catalogs also
can be replaced with SAP SRM MDM Catalog in future.
Below is the step by step guide from beginning to end to set-up and use MDM Catalog3.0 system to meet up
the above requirement. Prior to start the below set-ups System Admin will need to install SRM MDM
Catalog3.0 in the System and check consistency for successfully installed components i.e MDM Console ,
MDM Import Manager, MDM Data Manager and UI.
Import Scenario Set-up and Steps
Below is an example where a supplier catalog needs to be loaded into SRM MDM Catalog 3.0 system so
that Business Can use the data(Products offering from Supplier).
Steps:
Before Importing Supplier Catalog to MDM Import Manager we need to Synchronize below Data from SAP
SRM to SRM MDM Catalog:
1. Product Categories
2. Currencies
3. UOM ISO Codes
Also we will need to Load (Maintain) Suppliers and Purchase Organization prior to Load of Supplier Catalog
Data.
Reference: overview of Customizing tables and their assignment to MDM port codes

MDMGX transaction can extract the data to Local Desktop and the same can be imported then to SRM MDM
Import Manager
Proceed as below:
SRM system (SRDCLNT200)
2010 SAP AG 4
Execute Trn: MDMGX

2010 SAP AG 5

Choose for Remote System Type SRM in Multi Selection for Port name
(code)
2010 SAP AG 6

However, its needed to get downloaded at simpler path e.g: desktop otherwise download (extract) may not
happen
2010 SAP AG 7

The above Import may fail for the first time.
Put the below file in C:\Program Files\SAP MDM 7.1\Import Manager after renaming the extension as .exe

The above file will parse (read) the xml file and the Import will work successfully.
Login To Import Manager and Open the Mapping.
2010 SAP AG 8

Choose import map for LT_CURRENCIES from standard this will get auto mapped (as by standard)
2010 SAP AG 9

Go to Match records Tab
Remove all the matching fields and Redo matching with Remote Key

2010 SAP AG 10

Select Default Import Action as Create

Check Import Status
2010 SAP AG 11

2010 SAP AG 12
Similarly do for LT_PRODUCTGROUPS and LT_UOM

2010 SAP AG 13

For Product groups automatically Remote key appears and need not be added from value matching

2010 SAP AG 14

Import steps for 3
rd
file (UOM)

Click ok
2010 SAP AG 15

2010 SAP AG 16

2010 SAP AG 17

Once the Data (MDMGX Extract: Product groups, Currencies and UOM ISO codes) are Imported then Check
the Data in Data Manager
Login to Data Manager and check the data in the 3 tables
And
Currencies Data

Note: In order to view the decimal places (precision) on the Catalog UI, maintain the required number of
decimal places as an integer value in the Decimals field of the currencies table. This can be done during
the Import process by adding a new field to the Source XML to maintain the decimal place and mapping it to
2010 SAP AG 18
destination Decimals field in Currencies table. Another alternate is to do it in Data manager manually for
those currencies that are being used in the implementation
Product Groups Data

UOM ISO Codes

As there is only one Purchase Organization and only 2 suppliers to be used for Catalogs for Customer using
SRM MDM Catalog -so we can maintain them manually in SRM MDM Data Manager
Proceed as below:
For Customer the P.org to be referred is O 50000638 as in PPOSA_BBP for Purchase Organizations in
SRM
2010 SAP AG 19

NOW, P.org will have 4 char by default in console for p.org table (p.org code width)Change it to 20
* To change any field we need to unload the repository-->make the changeLoad repository with update
indices

2010 SAP AG 20

Press F5 for refresh

Now login to Data Manager and Maintain the P.org

Also Add Supplier in Data Manager.
Note: If you have many suppliers to be maintained, import the same from Excel sheet using Import Manager
2010 SAP AG 21

As in BP

Now, Import the Supplier Catalogs
Login to Import Manager
2010 SAP AG 22

The file looks like
2010 SAP AG 23

Choose Source as Below

Choose Destination as Catalog Items

Move to Map fields Tab
2010 SAP AG 24

2010 SAP AG 25
Start Mapping
1. Supplier in Destination is name field, so will have to be mapped to supplier description in Source
Mapping Structure.
Note: This is good to start following (Referring) the Destination fields one by one to MATCH with the Source Field
Destination Field name Source Field Name
Supplier(Display i.e. DF in Console) Supplier Name
Supplier Part Number(DF) Supplier Part Number
Short Description Short Description
Product Group(Description) UNSPSC code(Product Group)
*Also you may use Join functionality here,
otherwise this is suggested to be directly mapped if
the Product Group Description is available as a
column in the Main worksheet. More explained in
the Product Group mapping section.
Category Category
Price Information
Lower Bound
Purchasing Info Record
Purchasing Organization
Price Information(Not in source need to add)
Lower Bound
Purchasing Info Record
Purchasing Organization
Unit of Measure Unit of Measure
Order Unit Order Unit(Not in source need to add)
Minimum Quantity Minimum Quantity (Not in source need to add)
Minimum Quantity UoM Minimum Quantity UoM(Not in source need to
add)
Price Information(Other Fields)
Price Base Quantity
Price base Quantity(UoM)
Price Information(Other Fields) (Not in source
need to add)
Price Base Quantity
Price base Quantity(UoM)

1.Supplier name

Click on Map
2010 SAP AG 26

Once the Field Mapping is over, we will need to match the Value, for example for field Supplier name we
found there are 2 suppliers as found in Value i.e. 1.Pitney Bowes and 2.Orbis
So, we need to match (Automap) in Value Conversion and Mapping Tab

2. Supplier Part number

Note:
Value Conversion is applicable for Few Cases, for instance Text and Integer fields that are not marked as DF
(In console) value mapping is not applicable:
3. Short Description
2010 SAP AG 27

4. Product group Join option if source file is not having Product Group description
Product Group is a description field (e.g: office supplies) in Console where as Source file has this as
UNSPSC code (e.g:LOCOFFIC3)
So, we will need to join the UNSPSC field to description fields (in a different tab or, in the same tab in excel
with description)
Note the Join did not work out (seems to be a bug) once the Excel file was imported as the Product group appeared as
Blank in data Manager for the Imported Entries.
This is suggested to have the Product Group Description as available as a column with data in the Main work sheet itself
and mapped directly from there.
However, explaining the Join Process in the below paragraph to show how its done.

Creates an entry as
Without any field

To get the field right click Look upDescription field
2010 SAP AG 28

Doing this Description field from Product group worksheet will be available for Field mapping
This looks as below now:
2010 SAP AG 29

Map now

Click Automap now
2010 SAP AG 30

4. Category
Note: Category is a Hierarchical field and has got Parent-Child relationshipso we will need to create a
Hierarchical Structure in Source by using Split Hierarchy option-Map to Category in destination Select
all Values in Source and Add as Child to Destination in Value Conversion and mapping

2010 SAP AG 31

2010 SAP AG 32
Map

Value Conversion and Mapping

Click on Add

5. Price Information
For Price Information fields(Lower Bound, Purchasing Info record and Purchasing Organization) or similar
fields which is not there in Source we will have to ADD Field to Source so that we can do mapping
2010 SAP AG 33

2010 SAP AG 34
Map now:

Maintain as 1 in converted value

6. Similarly steps for other 2 fields

Keep Purchasing Info Record as Null and maintain Procurement for P.orgAutomap
2010 SAP AG 35

Click on Automap
7. Long Description

2010 SAP AG 36
8. UOM (Unit of Measure)

MAINTAIN EACH as description to match in Automap

Now Unit of Measure in Source also will have to be mapped to Order Unit in destination, so Source field
needs to be cloned

2010 SAP AG 37

Map

Automap
9. Similarly For

We need to add 2 fields, otherwise will bring value null
Note: For Minimum Quantity you mad add the field as the field is not there in the source file.
But for Minimum Quantity UOM we will need to clone from Order Unit field other wise will carry no value in
source if we add manually. By cloning we will receive value of Order Unit from the Excel to the cloned and
renamed field Minimum Quantity UOM to Automap in Value conversion.
So, Add field Minimum Quantity
2010 SAP AG 38

For Minimum Quantity UOM CLONE either UOM or Order Unit

Map

2010 SAP AG 39
10. Other fields for Price Information

Now as the fields is not getting Auto mapped so we can choose from Destination Values and Do mapping to
Source Values manually

For we dont have Source
Fieldsso will have to have them in Source

Map
2010 SAP AG 40

Similarly

2010 SAP AG 41
11. Important: Creating Compound Field for Price Information
Prerequisite: All price Information field should have been mapped properly as we have done before
Now for creation of Compound Fields Right Click on source (anywhere)

This will do an Automatic Field Mapping from Source to Destination for Look up Qualifier Price Information
Note: For any Qualifier table being referred to from Main table, the Compound field enables the data link by
capturing the non qualifier fields (Lower Bound, Purchasing Organization & Purchase Info Record) and
maintaining the link to the Qualifier fields (Amount, Currency, Price Base Quantity & Price Base Quantity
UOM). By doing so we can maintain multiple price information records for one catalog item record by adding
multiple non qualifier entries and maintaining the relevant qualifier field data.
For example
Catalog Item
Record detail
Non Qualifier fields Qualifier Fields
Supplier Supplier
Part
Number
Lower
Bound
Purchasing
Org
Purchase
info
Record
Amount Currency Price
Base
Quantity
Price
Base
Quantity
UOM
Infosys 100 1 5000789 50 USD 1 Each
Infosys 100 101 5000789 45 USD 1 Each
Infosys 100 1 5000790 100 USD 1 Pack
Note: For lines 1 and 2 having same catalog item records, scaled price is maintained by having a different Lower Bound
value. Here for item quantity from 1 to 100, price per unit is 50 USD and for purchases abover 100 quantity, price
per unit would be 45 USD
Third record is for a different Purchase Org for the same part number. In the Catalog UI all the 3 price combination would
be displayed for the same part number
2010 SAP AG 42

We need to Complete the Value mapping For the first time ADD the record OR,if it is already available
then do an Automap

2010 SAP AG 43
Match Records

For Matching records select Supplier(DF:display field) and Supplier Part Number and Do as Add as
Combination to make sure that they together act as unique key during matching
Note: We can have additional keys in the mapping to maintain multiple records for the key combination. For
instance Supplier, Supplier Part Number and Short Description as the key would enable having multiple
records with same part number but with different short description

Above scrshot shows that for the FIRST TIME Load 65 records are new(Match type=None)
Select Import Action as Create

2010 SAP AG 44
Import Status
Make sure there are NO ERRORS and status shows Ready to
Import

2010 SAP AG 45

***** Go to Data Manager and Validate if the Records are loaded successfully

2010 SAP AG 46
Check Category by hierarchy mode
option
Come back to Record Mode
Check the Field Values (one by one) for ONE record whether populated properly based on Import
2010 SAP AG 47
UI Change
For Change to Category from Hierarchical Display in UI
Note:Choose the user as maintained in Webservice

Also we can add Supplier part number in the UI Display and Place the Field beside Short Description to
appear in the shopping cart.
2010 SAP AG 48

2010 SAP AG 49
Final Check (Integration from MDM to SRM)

2010 SAP AG 50
Sel
ect an item and click on Add to Cart

2010 SAP AG 51

The Product is Transferred from SRM MDM Catalog with all Necessary Data and the Shopping cart has no
Errors and ready to be proceeded further.

Similarly for Loading other Import files(Other Supplier catalogs)
Note:
For using a saved Import Map we need to use to upload files with
A. Same file extension(e.g:.xls)
B. Same worksheet name(s),However the file name can be different.
2010 SAP AG 52
C. Same Column names in an worksheet. If additional columns are added in source worksheet, field and value
mapping has to be performed and Import map updated
D. The Prerequisite Config data required for 2
nd
Supplier Catalog i.e Product group and Description, Currency ,
UOM iso Code,Purchasing Organization,Supplier were already imported / available in Data Manager if
not,then import/maintain.
Also the excel should contain new Product Category in the worksheet.

Make sure the New supplier is maintained in Data manager in Suppliers Table (Referring the data from BP
Trn in SRM) prior to Import.

2010 SAP AG 53
Error handling and Loading a 2nd Supplier catalog file

Choose the New Supplier catalog ( In the same template as of First Supplier) and Click on Finish
Utilize the earlier saved Import map (which was used and saved for the first supplier catalog import)

2010 SAP AG 54

Check For Import Status (Ready to Import / Errors (if any))
Note:
Additional Options there are lot of options (flexibilities) to use for in Import Manager examples are like below:
Configuration Options
We can use below feature for Configuration options while Importing Data

2010 SAP AG 55

Here we can save the Configuration option(e.g.: To do an Automap automatically for import file using a
saved mapping so that the user will not have to click on Automap manually for records values those are
eligible for Automapping)
A) Options while in Field mapping
Field Mapping options

Similarly options are there for Value Conversion for Source values
as below
2010 SAP AG 56

We can Replace / Apply operator / Change Case etc. to a Source Value to have converted value.
Also options are there for Source Hierarchy to use for

Options to use Partition By for Field/ value for Available Fields(i.e. the fields which were mapped from
Destination
2010 SAP AG 57

Error Handling
After loading the file and opening the earlier Saved Map Go to Import Status Tab and see if any error is
there prior to import.

The error is Could not convert value 'FP07DQ - Dk. Blue tote with Customer hot stamp, commonly
referred to as a half tote (HT) and w/lid attached.' in field 'Short Description'
Locate the Field Short Description in Source where the error is appearing from

2010 SAP AG 58
We can see that the Green Dot is missing for this value and so could not be converted.
Check the Property of the Field in Console to understand WHAT MAY BE the reason for the conversion
for this Value w.r.t Field Property

So as above by checking in Console the length of the field Short Description is set to 100 Char by default
Cross check with excel

2010 SAP AG 59

So, 106 (length of excel data short description has crossed Max limit 100 as in console
To rectify the above we have the below options:
To overcome the above we have the below options:
a. Truncate the Short descriptions to 100 characters(auto truncation by MDM tool)
b. Increase the Size of the field in Console by this we can have the Short descriptions incorporated but the
look in MDM UI will not be good as they will appear as Long Hyperlinks(you can see in below screenshot that
short descriptions appear as hyperlink (blue text)
c. To have short texts maintained within 100 characters

Lets see the option a.

Note: the earlier Value gets changed to Green Dot (Converted successfully)

Check back the Import Status
2010 SAP AG 60

Note: Sometime if some values are not automapped then go back to Match Records tab and remove the
Matching fields -- go to Map fields and check/manually perform Value mapping (we may need to
Automap/Add etc.)

Also check
Any special characters in Input that needs to be handles by Value Conversion e.g.: if the excel data
contains !@#$%^&*)() and any New line( i.e. /n) OR, linefeed(/lf) - then do at the Field level if all data for
that field contains such characters OR, do at a field value level for a particular field value(which contains
extra characters)
2010 SAP AG 61

At Value Level:

Once the Status is Ready to import Perform the import Activity
Note: Make sure the file being imported is not stored in a directory having long path and has MDM as a word
in the path

2010 SAP AG 62
Understanding the Import Status Tab

This means How many Fields from Source has been mapped to Destination.
17/22 means 17 fields from Source (Fields Originally in Source file plus 5 Fields (Fields Added during
Import mapping process).

This shows Table joins and the Look up fields those were referred
Join that was made:
Look Up that was referred:
2010 SAP AG 63

Fields those do not require Value Mapped is shown above
e.g.:

Supplier Part number does not require Value mapping

2010 SAP AG 64

The above shows the Field which require Value Mapping

The above shows Fields Used for Record Matching.
Note: we need to use combined key (Supplier and supplier part number for example) in case of Supplier Part
Number same across two different suppliers, the combined key would define a unique record for matching
and identifying the record in MDM system. Additional keys can be added as a combination key for matching
records
Its suggested always to make use of Combined Key

The above shows WHAT Type of Match
Match type:
None-NONE = record from source do not exist in Destination and will have to be created
Single-Exact= One unique record from source matches to one unique record in destination, the options can
be to Update / Replace the record
Single-Partial = One unique record based on key information (e.g.: supplier-supplier part no combined key)
matches to one record in destination with Partial key (e.g.: Supplier with Supplier Part number after removing
hyphen in between. Supplier 100 with supplier part number A-200 would match to destination supplier 100
with supplier part number A200 (I.E without hyphen).
Best Practice is not to take any action for such entries (Action=None)
Single-Conflict = to be filled in
2010 SAP AG 65
Multiple-Extract = One record from Source matches to Multiple records exactly in Destination. Usually this is
a problematic situation that needs Data review in Destination and Correction to be done manually in Data
Manager. Action=NONE until the correction is made.
Multiple-Partial = One unique record based on key information (e.g.: supplier-supplier part no combined key)
matches to Multiple records in destination with Partial key (e.g.: Supplier with Supplier Part number after
removing hyphen in between. Supplier 100 with supplier part number A-200 would match to destination
supplier 100 with supplier part number A200 (I.E without hyphen).
Multiple-Conflict = to be filled in
Filtered-Source= this denotes any filter Applied on the source data to limit the number of records being
matched. This feature can be used to import ONLY Selected sections of source data.
E.g.: If we have data from multiple vendors, this feature can be used to restrict the update to a selected
vendors data. E.g. Data from Supplier A, B and C If we apply filter to Supplier A. Only records from Supplier
A would be processed during the import.
Filtered-Destination = this denotes any filter Applied on the Destination data to limit the number of records
being matched. This feature can be used to restrict the number of records from destination that would
participate in the import process.
E.g.: If we have data in destination for multiple vendors, this feature can be used to restrict the update to a
selected vendors data. E.g. Data from Supplier A, B and C If we apply filter to Supplier A. Only records from
Supplier A would be processed during the import.

The above shows the number of records with the corresponding action to be performed during import run.
Update Null Fields = Based on the key mapping and record match, the data elements of fields will get
updated only if the destination data element is null for that record. If it contains a value already it will not get
updated by the source value.
Update (all mapped fields) = this will update all the mapped fields irrespective of having Null Value at
destination
Delete Destination = Based on filter condition applied during record matching step, system would identify the
records that are delta and excess in destination. For such records, this action can be used to delete the
records from the system.
Example: Catalog refresh where Vendor provides records which are currently active on his catalog, the
inactive records that have EARLIER been loaded in the system have to be deleted.
Create = Records to be created when the source records are not being matched to any record in destination.
Skip = Records to be skipped even though there would be a match applicable. This can be done by the
record matching action for all records or selectively for specific records in the pane as shown below.

2010 SAP AG 66

Replace = this option can be used for match type Single Exact where you want to delete and reinsert the
record. Exercise caution with this option because it changes the GUID, In case of Update it does not change
the GUIS, In typical example for option Check product data again in catalog in web service, any shopping
cart item for which price is changed in catalog SRM checks the catalog with item GUID to validate price
changes. If replace option is used and catalog item GUID is changed this feature in SRM will throw the error
Item not found in catalog.

2010 SAP AG 67
OCI Mandatory Fields
Product Category, Supplier, Order Unit, Price UOM, Minimum Quantity (needs to be set as e.g. 1)
For the above we will need to make sure Field Mapping and Value Mapping are correct
e.g.: Though Import Status was showing ready to Import , However for Product Group we find as below that
there is no value available in Destination to Map for Product Category Packaging_SuppliesProbably this
was missed out to Import/Maintain initially

Go to Data Manager and Maintain manually:
Supplier name check:

2010 SAP AG 68

Do an Unmap and Map again for the field to fetch the new value from Data ManagerAutomap then

Check Supplier Name
2010 SAP AG 69

Check UOM:

Check for Price UOM
2010 SAP AG 70

So we are all set!

2010 SAP AG 71
Notes
1. Can we re-use the mapping so that we dont need to do mapping each and every time importing a file having
data in same structure?
To be able to do thisExport the mapping file and Upload back and then re-use for next time Imports.
For Example when we need to use the mapping from Dev (MDM) System to use the same in QA (MDM)
system then proceed as follow:
Dev System: Import manager (open any file)FileExportSelect the Mapping that we need to re-
useClick on OKSave to System

Login to QA System Import ManagerOpen the Import file which we need to importFileClick on Import
and select the Mapping file that was saved earlier

2010 SAP AG 72

Now click on open Map

2010 SAP AG 73

Then system will automatically all the fields that were instructed from the Mapping.
2. Do we need any cross checking after re-using the mapping file before we finally click on import button for
Delta Imports (Update)?
-Yes , this is suggested to check the value conversions(whether all values are converted and fields value like
Price Base Quantity, Minimum Quantity etc. are assigned 1 as value. Sometimes the automapping might
have got missed map them manually if required in Value Conversion if Automapping is not working, for
example: Automap may not work for source value USD to automap for destination value internal value
(united stated dollars) so in this case choose USD and internal value (united stated dollars) and click on
Map manually as clicking on automap did not work.
3. How to manage images through Import using Hyperlink (to avoid Manual mapping)?
Business Example: The contents of SRM MDM Catalog need to be assigned with Images which can be
linked from Data Manager (Manually one by one) OR, can be uploaded from Import manager. We are
showcasing the 2
nd
example for Auto Mapping.
Process Steps:
a) Showcase MDM Catalog capability to process and display images stored on a server using the Hyperlink
option of the product
Pre-requisites
a) Store the images on a HTTP based web server accessible over the LAN/WAN to the MDM server
b) Capture the image file names and logical path to the image For instance
http://webserver:port/Imagerepository/<image_file_name>
c) Create a catalog items import file with the Supplier, Supplier part number, key fields for data management
and one column that would have the image file name
d) Put the images in the Designated Folder in the web server
2010 SAP AG 74
e)
f) We will need to call the Hyperlink like below to refer to an Image from the Import File to the Location (Where
the Images are stored).

g) Have a column like Image Files in the import file and Put the Names of the Images
2010 SAP AG 75

h) Launch the import manager client and select the import Excel file prepared in step (g)

i) Click Finish and select the source and destination tables using the dropdown. Navigate to the Map
Fields/Values tab and start the field and value mapping process

j) Map the key fields Supplier (DF) and Supplier Part Number (DF) to the destination. Perform the value
mapping as well

2010 SAP AG 76

The following section describes the Import process to achieve the same result as is done using Data
Manager while maintaining a Hyperlink to an existing Catalog item record

k) To map the Hyperlink to Images, add the following fields to the Source
a. Hyperlink Type = Rendered (Value of field)
b. Mime Type = JPG (Value of field)
c. URL Description Clone from field <Image File> in source

l) Map field Hyperlink Type to Hyperlink field in destination.
Note: Rendered option would make the image to be displayed on the Catalog UI, while the Link option would place a
hyperlink to the image on the Catalog UI. To view the image, user needs to click on the hyperlink and image would
open in the new window.
2010 SAP AG 77

m) Navigate to Hyperlink Qualified table section on destination fields and expand it to view the 3 qualifier fields.
Map the source field Mime Type to destination Hyperlink qualifier Mime Type

n) Map the URL Description clone field from source to the Hyperlink qualifier field URL Description in the
destination

o) Map the Image File field from source to Hyperlink qualifier field URL in the destination. After mapping right
click on the Image File field in source and perform the following.
a. Add a Value Conversion Filter

2010 SAP AG 78
b. In the pop up window to choose the operator select Prepend and provide Operand value as
http://blrkec3125scm/

c. The final converted value for Image File mapped to URL is

p) Once all the fields from source are mapped to destination fields along with value mapping, proceed to match
records stage. Add Supplier (DF) and Supplier Part Number (DF) as combination key to match the source
records to destination

For match type None, it means the records from source do not exist in destination. Select the import action
as Create as shown in the image above
q) Click on Import Status tab to see if all the pre-requisites are met and data is ready for import as shown below

r) Click on the Import icon to trigger the import action
2010 SAP AG 79

s) Login to Data Manager and check if the data load is successful and Hyperlink data is attached to the
individual catalog item records

t) Next step is to validate if the image hyperlink rendered option is displayed on catalog UI as per expectation
2010 SAP AG 80

u) Login to the MDM UI Configuration utility and setup Hyperlink as the image option in the Item Lists and Item
Details views for the user being used to access the catalog and save the settings

Item Details view
2010 SAP AG 81

2010 SAP AG 82
Related Content
Reference: SRM MDM Catalog3.0 System

2010 SAP AG 83
Disclaimer and Liability Notice
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not
supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,
and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or
code sample, including any liability resulting from incompatibility between the content within this document and the materials and
services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this
document.

SAP SRM MDM Catalog 3.0 - (Data Loading) and UI Overview

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP SRM MDM Catalog 3.0 - (Data Loading) and UI Overview

Uploaded by

Copyright:

Available Formats

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.

You might also like