KeyGeneration

[Former Member]

Hi All,

What is the purpose of KeyGeneration property in remote system ?

Please explain me that How it is useful in while importing and syndicating the data?

Thanks

Narendra

[Former Member · Accepted solution]

Hi,

Key Generation property of the Remote System automatically generates the key for the records present in the repository if this property is not enabled then you have to manually assigned the key for each record.

Key Generation contains three values:

None - No Keys wil be assigned to the records

Range - Specify the range for the keys

Qualified Range - Allows you to select the Lookup flat table from the drop down and you can specify the range for each and every value of that lookup table.

Regards,

Jitesh Talreja

[Former Member · Accepted solution]

Hi Jitesh,

Are these keys are available in edit mapping option of data manager?

I think these keys are used to identify the remote system,then one key is enough to do so.

why we need specify range and qualified range?

Thanks

Narendra

[Former Member · Accepted solution]

Hi Narendra

why we need specify range and qualified range?

I will give simple example for this.

The Range might be required when you are having 2 R/3 systems and thus 1 R/3 system will have materials in range of 10000 to 50000 and second R/3 system will use 50001 to 900000.

The Qulaigied range will be required if you wish to have the key based on some condition like based on plant type etc.

Hope this helps,

+ An

[Former Member · Accepted solution]

Lets say, for example, you have one MDM system representing your global landscape, and you have four systems to which you will syndicate records. For each record in MDM you need one global key that you can use to search and sort on in MDM. Additionally, each system that you syndicate the record to will maintain it's own key. Whether it's the same key as MDM, or a different key that MDM generates, or a different key that the system generates itself, you still need to have a key. Because of this, it's beneficial to store a "key mapping" in MDM that stores the keys in each of the partner systems for a given record.

MDM has the capability to generate keys based on the remote system and a specified range. One common example would be to have a remote system that is R3 which has different material number ranges based on material type. So if the record is a HALB, then you want the material number to fall within the range 10000-19999 (obviously thats not a realistic range, but just an example). In the console you can configure the key generation such that during syndication it will generate a number based on the remote system and the material type, so you can maintain different ranges based on material type.

One thing to keep in mind is that this number won't be stored in the searchable data model. For example, if you have a field for ECC material number, it will not be populated based on the key generation. The only thing that will happen is the number will be syndicated into the XML file in the desired field based on your syndication mapping. If you want that number to be stored in the MDM data model for searchability, then you need a workaround to populate that field. This can be done with XI, the ABAP API, or an outbound interface from R3 back to MDM.

Edited by: Harrison Holland on May 13, 2008 4:40 PM

[Former Member · Accepted solution]

Thanks to All

[Former Member]

Please go through the URL to get the complete understanding of key generation :

http://help.sap.com/saphelp_mdm550/helpdata/en/42/ea344f106b3ee4e10000000a1553f7/frameset.htm

Under Console Guide->Repository Maintenance->Other system Tables->Remote system table->Key Generation

Hope this will help you out.