Central Master Data Management Scenario

[Former Member]

Hi Folks,

Which is the best way to get the keymappings updated for a situation where the master data is directly created in Data Manager [no web front end and no webservices].

Eg: user gets into DM and creates a material - which has got multiple vendors and vendor part numbers in multiple systems - the plan is to have the vendor partnumbers as keys with diff remote systems all with a common Global ID.

-Vinay

[Former Member]

Hi Vinay,

Without webservices, i think this is the only option that u import it using key mapping to that particular field which u want as ur key.

Regards,

Dheeraj.

[Former Member]

Here is a situation that needs some intelligent answers:

Scenario: Central Master data management. MDM >PI> BI & R/3

No front end. Data entry via DataManager

Master data is entered in MDM and syndicated to PI then to BI & R/3.

R/3 has several Business units [BU's] having different part numbering systems . These part numbering systems in each of the BU is NOT tobe changed [due to business requirements].

In MDM - the requirement is :

a) Each BU should be able to search for thier respective part numbers to get thier GUID & other details, including any possible duplicates

b) Materials across BU's could be identical and should have one GUID .

c) MDM should send the GUID and all respective part numbers for respective BU's to BI for reporting

d) The tricky part is all products should be arranged in MDM based on thier Taxanomy !! So.. MDM would end up sending the basic view of the master data and the taxanomy structure to BI for reporting and just the basic view to R/3 for subsequent local completion.

How would you approach this?

[Former Member]

Hi Vinay,

If I understood your question, you want to get remote keys for your records created in data manager. For that you must have key mapping field as Yes in console.In console, in the remote systems, you must have key generation set to either range or qualified range.If you want that your key generated should be based on some criteria say you have three account groups as A, B and C. You want that the key generated for records having group A should be ranging from 1 to 100, similarly for B from 101 to 200 and for C from 201 to 300. Then you should select key generation as qualified range and your lookup field should be your account group table. In qualified range field, you have to specify the ranges you want in front of the account groups.

If you want your keys should be generated in a range with no other constraints then you should choose key generation as range and specify the range.

If key generation is none then no keys will be generated for that particular remote system.

Do the same for all the remote systems to which you want to syndicate the records.Then map the remote key fields on source and destination side in syndicator. You can see the generated keys in data manager by right clicking on record and then choosing edit key mapping.

Remeber that you can see the key mapping only after syndicating the records once.Before syndication you can't see the keys even in syndication preview.

Hope this will help you.

Regards,

Dheeraj.

Edited by: Dheeraj Kumar on Feb 20, 2008 9:13 AM

[Former Member]

Thanks Dheeraj,

What you just described is self key generation by turning on the key generation in the console. The key mapping I was talking about was the keys of multiple erp systems ..say MATNR of 2/3 systems - these matl numbers [which are already in the erp systems] need to become keymappings in a central masterdata management scenario. Importing a file with the repective matl.numbers as keymapping is one option.. are there any other ideas... [without using webservices]