Key Mapping

[Former Member]

hi friends

i have used key mapping In MDM, But still i have some sort of confusion in this key mapping.

can any one give small and simple example about this?

where exactly it will use?

Thanks in Advance

bharat.chinthapatla

[Former Member]

Hi Bharat,

In MDM key mapping plays a important role when a company is having many remote systems like Legacy ,SRM ,CRM ETC. and they are sending their data to MDM for integration or cleanizing key mapping tells that to which system that data belongs and where to send back after processing.

this is done in the following way : In console you the key mapping field yes for the unique field as "Yes" .In data manager when you click on the record in record mode and select edit Key mapping you can see your unique field and the system name to which it belongs after merging the duplicates when u select the merged record you can see its key mapping where it will show two system names and also the unique field value.In syndication you have to map the field for the key mapping which helps in sending record to the respective system from where it came.

Regards

Anita

[Former Member]

Alok,

When would you use the keymapping feature for attributes? Can you give some examples ?

-Vinay

[Former Member]

hi,

Key Mapping:

1. It Specifies whether or not MDM should maintain key mappings for the table. we will enable key mapping property/Table Detail pane in the console.

2.A remote system’s objects are mapped to master data objects within MDM using key mapping. A key mapping maintains the relationship between the remote system’s identifier (or key) for an object and the corresponding master data object in MDM.

3. A key in MDM is a remote system-specific and object-type-specific unique identifier. Different remote systems can have their own separate collection of keys. Within a remote system, each type or collection of objects can have its own separate collection of keys as well. Key mappings are subject to the requirement that two different objects of the same type from the same remote system cannot have the same key value.

Example:

flow the links.

http://help.sap.com/saphelp_mdm550/helpdata/en/43/e0265c425702d3e10000000a1553f7/frameset.htm

http://help.sap.com/saphelp_mdm550/helpdata/en/43/e0265c425702d3e10000000a1553f7/frameset.htm

http://help.sap.com/saphelp_mdm550/helpdata/en/43/e0265c425702d3e10000000a1553f7/frameset.htm

hope this may help you,

Regards,

Srinivas

[Former Member]

Hi

The key mapping option is used for storing different keys (of the same record) of different systems within MDM. This is necessary as records are created / referred to not with their "display" values, but with their "key" value in the source systems.

EX :

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 XYZ 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 different 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 referring to the same costumer in System B.

For more details go through this link

https://websmp208.sap-ag.de/installMDM

in that go to Data manger reffernce guide page no 593

or in console 249

I think it may help u

Regards

Hari

[Former Member]

Hi Bharat,

Remote key mapping trigger you have to do at Console level with yes.

When in import manager you are doing mapping from source system to destination system.

In source system you have to select the main table for example vendor then you have to clone this field and you have to map this main vendor field to destination field vendor field and reote key of destination to the clone of the vendor field.

This mapping will help you in data manager when you merge two records at that time you will get pop-up with the key mapping and with the remote system.

Hope this will help you.

Regards,

Saurabh

Note: Reward the points, if found helpfull.

[Former Member]

Hi Bharat,

A remote system’s objects are mapped to master data objects within

MDM using key mapping. <b>A key mapping maintains the relationship

between the remote system’s identifier (or key) for an object and the

corresponding master data object in MDM.</b>

A key in MDM is a remote system-specific and object-type-specific

unique identifier. Different remote systems can have their own separate

collection of keys. Within a remote system, each type or collection of

objects can have its own separate collection of keys as well. Key

mappings are subject to the requirement that two different objects of the

same type from the same remote system cannot have the same key.

Remote system objects of a particular type can map only to MDM

objects of a particular type. A key can map to only one MDM object.

However, an MDM object may map to multiple keys from the same

client system. When an MDM object maps to multiple keys, one of the

keys is marked as the default key. The default key is the one that is

used when syndicating a reference to the mapped MDM object.

Plz reward points if u find this helpful.

Regards:

Neethu

Message was edited by:

Neethu joy