MDM Key Mapping

Hello Experts,
Please help me to understand the Key Mapping concept in context to SAP MDM.
How the key mapping values get created while importing the data through the import manager and what role key mapping playes while importing the reference or look up data for the first time.
Thanks.

Hello Rajan,
As all of us one of the main functions of MDM is to eliminate duplicates ok?
now let consider that you have 2 offices one at US and another in India. lets say that you use citi bank both in india and US to do the transcations, of course there are also some other banks that you deal with.
As you know any transcation that you do with CITI bank(US) is not same as CITI bank(IND). Which means even though the bank is same these two are 2 different entities.
know lets built a table for list of banks that you do transcations both in india and US
BANKS-US
   bank num - 1     bank name - barkalays
            - 2                 south american bank
            - 3                 millenium bank
            - 4                 Citi bank
            - 5                 american express
Bank - IND
   bank num - 1        bank name - sbi
   bank num - 2                    ING Vysa
              3                    citi bank
              4                    punjab national bank
now when we are import all these data into MDM citi bank will be always a duplicate records. BUT IT IS NOT ACTUALLY DUPLICATE since it record1 of citi bank belongs to US and other belongs to IND.
So inorder to over come this one what I create tha remote system ( we can create this in remote systems table under admin node ) in MDM where i name all the data coming from US as BANK-US and from IND as BANK-IND
now when we import data into MDM we log in into respective remote system for example if I am to import data from US i specify my remote system as BANK-US and similarly with india and import data. So now when you see the data in data manager you can find only 1 records of CITI bank.
now if you want to see which citi bank it is right click press "edit key mapping" there you can citi bank record of both the systems.
Similarly the same concept applys for objects also i.e when similar record belongs to two different objects

Similar Messages

Display MDM key mapping information in EP Item Detail iViews

Hi,
in my repository I have the main table 'customer' including key mapping information for several client systems (master data consolidation scenario).
The customer data is diplayerd in EP using the Item Details iView. I'd additionally like to display the key mapping information in Item Details iView, for example as a separate tabstrip. Is this feature already supported by the Item Details iView? How can I implement it?
I'm using MDM 5.5 SP3 / EP6.0 SP14.
Thanks in advance,
Martin

Hi Martin,
Currently iView do not support the functionality to disply the key mapping information.
Workaround I implemented is that, added a field "source system" to main table with type lookup. Added lookup table "source systems" with list of names of client systems. This helps user search data based on client system name.
I hope this is helpful.
Abhay

MDM key mapping: multiple fields?

Hallo,
is it possible to base key mapping on more than one fields?
From what i see key mapping is based on one field only...
Regards,
Marco

Hi,
is it possible to base key mapping on more than one fields?
From what i see key mapping is based on one field only...
yes, for that your field in Maintable should be Display field. So if you have two fields in Maintable then both of these fields can be used as key mapping in import manager while importing Data, in Match records tab, you can also have option of using these fields as Split or Combine as per your requirement on the basis of which you want to insert data into MDM Data Manager.
Hope it will Help you,
Rewards if Useful.....
Mandeep Saini

Can Key Mapping details be available as a serach parameter in MDM DM?

Hello Experts,
Is there any way that we can display or search certain Records in Data Manager/Portal based on the Key Mapping details (Remote System/Key Value assigned for any remote system).
The scenario where I am trying to apply this is:
I have say lacs of records in MDM and i have merged certain records into a new record (Record1) and assigned key mappings to this record1 to point to System1 and System2.
System1 has the key value as ABC and System2 has value set as DEF. If any user wants to now find the merged record based on the key value of system2 (i.e DEF), how will he proceed?
Kindly advice.
Thanks and Regrads,
Elizabeth.

Hi Elizabeth,
In MDM Data Manager, once the record is merged you can see only one record in place of all merged records.
In your case ABC from system1 and DEF from system2 are merged into ABC.
So in data manager you can just search the record based on ABC but not DEF.
However, if you select the record ABC and right click and select Edit key mappings, then you will see both the records and its respective system.
So the work around is using syndicator, send the records in excel sheet or CSV file where you can send both the merged records with merged values.
The users can make a search in that CSV file with DEF as well.
Regards,
Sravan

MDM Exception: Key mapping value must be unique. You cannot overwrite key

"ServerException: Key mapping value must be unique. You cannot overwrite key mapping values."
I received such exception when code tried to manipulate Key Mappings of the record.
error was not happen on mdm 5.5 but on 7.1 it sometimes appears.
What is probable reason of this?
How to resolve this ?
Code is approximate so:
 String[] keys = keyMapping.getKeys();
 if (recordKeyMapping.containsKeyMapping(remoteSystem)) {
 recordKeyMapping.replace(remoteSystem, keys);
 else {
 recordKeyMapping.addKeyMapping(keyMapping);
 //Persist
 targetRecord.update();
//where methods are:
 public void replace(RemoteSystem remoteSystem, String[] keys) {
 KeyMapping keyMapping = getKeyMapping(remoteSystem);
 if (keyMapping == null) throw new IllegalArgumentException("Can't update keys: key mapping for the system '" + remoteSystem + "' is not found");
 else {
 keyMapping.setKeys(keys);
 public void addKeyMapping(KeyMapping keyMapping) {
 RemoteSystem remoteSystem = keyMapping.getRemoteSystem();
 for(int i = 0; i < keyMapping.size(); i++) {
 addKey(remoteSystem, (String) keyMapping.get(i));
Edited by: Vladimir Grigoryev on Oct 5, 2010 11:26 AM

Hello -
I am not sure on that coding part. but is it like are you trying to retrive Key Mapping from Memory accelerator. Here this information always needs to be read from Database.
I am sure you also maintained the required attribute for key mapping as in Property in Console should be set as "Yes" and other relevant things properly .
Here also go through the below link for more insight from tools perspective.
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30843106-5539-2b10-75a9-da483911b0d9
http://help.sap.com/javadocs/mdm/sp06/com/sap/mdm/data/KeyMapping.html
It may help
Rgds
Deep

Key Mapping MDM

I am interested in knowing if anyone has interest in the ability to visualize graphically and manage key mapping external to the MDM. Would you want the capability to automatically update the MDM from the graphical model? Is there a similar capability offered by SAP or another organization?

Hello Rama:
First you have to create Client Systems on the MDM console, of type Inbound/Outbound.
Then Enable the Keymapping feature for the table you are using (on MDM). Choose your repository, on the right pane choose the table, and on Table Details, choose Keymapping = Yes.
When importing data on Import Manager, map the desired source field into the Remote Key field on MDM.
When syndicating, depending on your client system, the right key will be retrieved, if for instance, customers are duplicated on both systems (r/3 and sql server) you'll get the corresponding key for each one.
I hope that helps
Regards
Alejandro

MDM iviews in Portal throws error in key Mapping

Hi,
I have EP7 with SP15 and MDM 6.0, recently upgraded. Before upgrade we have an application which uses the MDM iviews and maps the fields of one table to other and displays in some other iview.
The application was working fine before upgrade of MDM. But after upgrade, the mapping seems not working.
My scenario is as : Using MDM Search iview, I search records from MDM repository, Main Table. This result is displayed in MDM Result iview. From this result iview, I select a record. From this selected record, a field is mapped to the other table. The mapped record, then, is displayed in MDM Details Iview.
After MDM upgrade, whenever we select a record from the result of table 1,the mapped iview throws erros :
Error occurred: Error performing search. com.sap.mdm.internal.protocol.manual.ServerException: Illegal value for parameter, com.sap.mdm.internal.protocol.manual.ServerException: Illegal value for parameter (see log for details)
when serached log : it says error in <table 1>-Key mapping <table1> is first table.
We have used EPCF eventing for MDM iviews.
has anyone out there faced same issue ?
Please let me know your views.
Regards,
Abhijeet

Hi Abhijeet ,
check the below wiki
findout anything is needed related to keymappings
"if Keymapping is selected, your Result Set iView only displays fields that are related to key mapping.This step depends on the search table selected and the schema of the repository that you are connected to"
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/set%2biviews
check the search table and schema of repository properties you connected
Koti Reddy

MDM API to read the Record Key Mapping table

Hi,
Does anybody know what class/method I can use to read the Record Key Mapping table?
For the Business Partner table the Key Mapping table has this columns:
Default / MDM Partner ID / Remote System / Key
I have everything but the Key. How can I read it?
Thanks in advance,
Diego.

GetKey Mapping is one of the available Web Services as of SP4.
Else you could use the Java API to get the Key Mapping.
CatalogData class has the following method
GetKeyMapping
public java.lang.String[][] GetKeyMapping(java.lang.String agency,
 java.lang.String table,
 int[] recordIDs,
 boolean isDefaultKeyOnly)
 throws StringExceptionRetrieves the key mapping for each record.
Parameters:
agency - the agency name.
table - the table name.
recordIDs - the list of records.
isDefaultKeyOnly - True to retrieve only the default value, False to all key values.
Returns: the key values for each record.

SAP MDM 7.1 Vendor Number and key mapping

We are importing data for vendors whcih DO NOT have any VendorNumber now. (they have some the VendorNumber but not one which can be used in the field Vendor Number.)
We have to generate the VendorNumber during oar - better - after the import.
There is not problem creating is after the import with a simple assigmment statemen which contains some rules.
So far so good.
The pitfall in creating the number AFTER the import is that NO remote keys are generated.
Any idea how to create these keys AFTER or DURING import IF hte venoder number is assigned during or after import?

Hi Lutz-Peter,
Any idea how to create these keys AFTER or DURING import IF the venoder number is assigned during or after import?
During Import, if you have local keys for each of these remote system, you can maintain it using Remote key concept.
But you must have one Matching field(Global ID) for this. Since you are creating Vendor key centrally in MDM using MDM Data Manager. Are you exporting data to different remote systems after creating Vendor number centrally in MDM(which can acts as Global ID) If yes then after data created into Remote systems, you can bring Local ID of remote system with this Global ID during import. 1stly, for this your main table property Key Mapping = yes should be enabled in MDM console.
So during import you should open MDM Import Manager by selecting required Remote system, you will get one more field in target Remote Key, map this target field with with source Local ID field along with other fields like Global ID etc. So in this you will have your Remote Key for Remote systems.
However Remote Keys depends on how are you creating Local ID(remote Keys) for remote systems, i mean in Remote systems itself or through MDM Syndicator using Remote system Key Generation concept.
Regards,
Mandeep Saini

MDM API for key Mapping.

Hi All,
Can anyone tell me how to use MDM API for updating key mapping ?
I want to create a webservice which will take customer,client system and key for updating key mapping in mdm.
Can anyone give me clue on this

Hello Rama:
Under Java you can do these things:
Delete key mapping:
CatalogData.DeleteKeyMapping(ClientSystem : String, Table :
String, RecordID : int, Keys : String[])
Argument Description
ClientSystem -> Client system name
Table -> Table name
RecordID -> Record ID
Keys -> Remote keys to remove
Set a new keymapping:
CatalogData.SetKeyMapping(ClientSystem : String, Table :
String, RecordID : int, Keys : String[], DefaultKeyIndex
: int)
Argument Description
ClientSystem ->    ClientSystem name
Table ->           Table name
RecordID ->        Record ID.
Keys ->            Remote Keys you want to add
DefaultKeyIndex -> Index entry into the key parameter
indicating the key value as the default.
I hope that helps
Alejandro

Remote System and Remote Key Mapping at a glance

Hi,
I want to discuss the concept of Remote System and Remote Key Mapping.
Remote System is a logical system which is defined in MDM Console for a MDM Repository.
We can define key mapping enabled at each table level.
The key mapping is used to distinguish records at Data Manager after running the Data Import.
Now 1 record can have 1 remote system with two different keys but two different records cannot have same remote system with same remote key. So, Remote key is an unique identifier for record for any remote system for each individual records.
Now whenever we import data from a Remote System, the remote system and remote key are mapped for each individual records. Usually all records have different remote keys.
Now, when syndicating back the record with default remote key is updated in the remote system that is sent by xml file format.
If same record is updated two times from a same remote system, the remote key will be different and the record which is latest contains highest remote key.
Now, I have to look at Data Syndication and Remote key.
I have not done Data Syndication but my concept tell if there is duplicate record with same remote system but different remote keys both will be syndicated back. But if same record have two remote keys for same remote system then only the default remote key is syndicated back.
Regards
Kaushik Banerjee

You are right Kaushik,
I have not done Data Syndication but my concept tell if there is duplicate record with same remote system but different remote keys both will be syndicated back.
Yes, but if they are duplicate, they needs to be merged.
But if same record have two remote keys for same remote system then only the default remote key is syndicated back.
This is after merging. So whichever remote key has tick mark in key mapping option(default) , it will be syndicated back.
Pls refer to these links for better understanding.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/80eb6ea5-2a2f-2b10-f68e-bf735a45705f
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/7051c376-f939-2b10-7da1-c4f8f9eecc8c%0c
Hope this helps,
+ An

Key Mapping activates Versus Import Manager

Hello,
I have Key mapping activated in the console and Supress Unchaged Records activated in my syndication map.
Case : I import files (suppliers catalogs) to MDM via Import Manager manually. I am not sure about it, but since I activated Key mapping property,
I noticed that for each supplier ID in the Supplier table, a lot of remote keys were created. Previously I only had one remote key for each supplier and now I have a list of other supplier's ID. ( Existent or nonexistent supplier IDs). This becomes an issue for my import, because when I try to import a file where the supplier id does not exist in the MDM ( this scenario used to block my import and this is what a expect, as supplier is a key in my mapping), the system automatically maps that nonexistent supplier to other supplier.
Can you help me to understand if this is caused for the key mapping property ? Any Idea ?
Thank you very much
Luciana.

Hello Stanley,
The remote keys are form the same remote system.
My story is : When I am importing a file , suppose my file has an invalid supplier ID. ( this means this supplier is not in the lookup table Suppliers)
1)The import manager will give me a message such as : Map Supplier ID Values. This behavior was expected.
2)I decided to test the automap. The invalid supplier was not mapped to a different value. I am ok with that.
3)If the user ( dont ask me the reason ;-)) decides to map that invalid supplier ID to a different one, he/she is allowed to do so. I remember when the key mapping was not activated this option did not exist. The map and automap button was deactivated.
What I am trying to make sure is : a remote key will be created for invalid suppliers ONLY if I choose to map it with a different supplier ID.
Do you have any comments about it ?
Thank you very much
Luciana.

Key Mapping - Automation

Hi , I have a following scenario that I want to automate within MDM :
Vendor data coming from 3 remote systems ( say p-Carrd , Legacy Supply management and Invoice system) .
1. Have loaded vendor data from all the systems in MDM using import manager .
2. Have applied rules for match and then merge for likely identical records
3. Now I want to see the key mappings for the merged record to determine say what are the source records have been merged into a single record so one way is I could add the id of source systems for this MDM record but that is manual .
Is there any way to automate this i.e. whenever I merge records and clieck on view key mapping I should have all the source system ids and remote systems appearing .? Key mapping is enabled for main table i.e. Vendor master
Regards,
Amit

Hi Amit,
first before importing any records, you should add your different source systems to your repository in MDM Console. You can do this in the Admin section. Having done this you can already import your source files for your source system. This step will automatically create a key mapping entry that can be seen in MDM Data Manager. Make sure that you map the actual key field of your record to the destination Remote Key field in your import map. If you now merge records from different source systems in MDM Data Manager, the merge will automatically append the remote keys of the different systems to your merged record.
Best regards
Michael

Remote Key Mapping - Maintanance

Hi All,
I have Auto Id field in my repository; I would like to maintain this as my remote key value in my key mapping table ( automatically) in the following scenarios:
1. Initial Loading
2. On going ( from portal)
3. Manual creating a record
The issue is, since its auto id - not available until unless it get created?
Do I need to syndicate all and loop back as Import and update remote key??? or any webservices and so?
thanks,
Alexander.

Hi Raja
You are correct on the approach. This can be done by automatic syndication of the newly created records from any of the channels( excel import, Portal, MDM GUI) to Outbound ready folder from where the files are copied to Inbound folder and automatically imported back in MDM. Steps to be followed can be-
Create ports for syndication and auto Import
The syndication map should contain mapping for Auto ID and any other unique field for reference. Assign this to Outbound port above.
The map used for importing should contain mapping of Auto ID to remote key for the record.Assign this to Inbound port above.
Define/set up a batch job for copying the files from Outbound Ready folder to Inbound Ready folders.
hope this helps.
Ravi

Steps in Key mapping

Hi all,
i have gone through many forum's regarding key mapping.
i can see that the following are used..
--> remote systems
--> key mapping option in table-field properties
--> key mapping option in table properties.
-->key generation(none, range, qualified range) field in remote system properties.
But never understood like in which order we need to define all the above, what is the relation b/w them.
i have gone through some theory in sdn regarding key mapping but unable to get the logic..
can any one one show me with 2 records in 2 tables so, that i can clear my confusion.
Thanks in advance.
Regards
phani

Hi Phani,
first you should understand the basic idea of key mapping. MDM usually wants to consolidate master (objects like vendors, customers, and so on) and/or reference (lookup tables like countries, regions, and so on) data. The idea is to load this data from various remote systems into MDM, compare and match the data, and in some cases merge multiple records into a single one. Let's take an example.
Image you have attache two remote systems to MDM. The first is an ERP system, the second a CRM system. Both system contains countries as reference data. In ERP, your country India looks like
Name = India
Code = INDIA
whereas in CRM it looks like
Name = India
Code = IND
It is obvious that the country is the same, but the systems use a different internal code. Now you load this data into MDM. What do you do? Do you want to create two records having different codes? Or do you want to "merge" the indentical records into a single one. The common decision in MDM is the second one.
But what happens now if you send customers from ERP and CRM to MDM? Usually the Customer message contains the Country CODE but not the Country NAME. From ERP the message could look like:
Customer = Mr. X
Country = INDIA
whereas from CRM the message could look like
Customer = Mr. X
Country = IND
Surely you want to map the different code in both case to the same country "India". That's why you use key mapping in MDM. Key Mapping allows MDM to store different codes for the same data. So in MDM you store just one record, but if you receive and/or send data from and/or to remote systems, you can always ensure that you store and/or send the correct codes.
Hope that clarifies your doubts about key mapping in general?
OK, now regarding your question about "Update NULL fields only":
In Import Manager you have several options for data import. If you import for the very first time (for RS1), your table in MDM is usually empty. That why you need to "Create" the records. If you import the second time (for RS2), your table in MDM already contains data. Depending on the matching field for import, several options are now possible. If Import Manager is not able to match the record you want to import against any other existing in the repository, you have to "Create" the new record. If Import Manager is able to match the record that you want to import with a record of your repository table, you can choose what happens next. "Update NULL fields only" compares the record you want to import with the existing values in MDM. In your case, following info is already part in MDM:
Country = India
Code = INDIA
Remote Key RS1 = INDIA
Remote Key RS2 = NULL
Now the file you want to import contains the following values:
Remote System = RS2
Country = India
Code = IND
Import Manager identifies that only "Remote Key RS2" is NULL. All other fields already have values. As you choose to "Update NULL Fields only", only Remote Key RS2 gets a new value. If you choose a different option, e.g. "Update All Mapped Fields" Import Manager would update the Country and Code fields, too.
Best regards
Michael

MDM Key Mapping

Similar Messages

Maybe you are looking for