on 02-08-2007 7:20 AM
Hi,
Could you please share your knowledge on Keymapping concept in MDM?.
Thanks in advance
Best regards
Devaraj PK
Hello Devaraj,
Bascially, the key mapping option is used for storing differnet keys (of the same record) of different systems within MDM. This is necessary as records are created / reffered to not with their "display" values,but with their "key" value in the source systems.
An example illustrates this:
Let's say you have 2 source systems A and B, which you stored customer records in. In System A the customer 1 has the ID ABC in System B, costumer 1 is also stored, but with the ID 1234. If you now merge this record in MDM to have "one single source of truth" you have to store these 2 diffrent keys & source systems in the key mapping option. Cause if you modify the record in MDM and want to distribute the changes to System A, you have to use a different key than if you're reffering to the same costumer in System B.
You can also find more information in the Data Manager Reference Guide: https://websmp208.sap-ag.de/installMDM
Hope this helps,
Andreas
- please reward helpful answers -
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In Import Manager I am using key mapping for a different purpose.
Say we want to load a city table which has state and city-codes.
If one can make a group field of State and City codes and map it to 'Remote key' of that table, then the table gets loaded correctly if matched on remote-key.
Otherwise one will get only last city for each state.
Bottomline is whenever we need to load a table on the basis of a group key and destination side(MDM) there is no such group field,Remote-key is to be used for mapping and loading.
Hope it helps.
I
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.