SAP R3 - XI - MDM Scenario for customer master

[rajesh_chavan]

Hi Experts,

We are working on ?consolidation and harmonization customer master data from SAP R3 using SAP MDM. We are suing SAP PI (XI) as an integrator / middleware. We are extracting Look-up values using "mdmgx" program and "mdm_clnt_extr" to extract main table data. We have few doubts,

1) While extracting "Look-Up" values from SAP R3, Do we have to extract ?Code? and ?description? both or either one of them. For eg. For country look-up table "DE" or "Germany"

2) Can we use standard business content as it is? Because if we have to extract both values then we have to alter standard business content to store that values (Look-up)

3) What to syndicate for Look-up data in main table. "Code" or "description" or "BOTH"?

Matter is urgent?

Satisfactory answers will be rewarded points?

Cheers

Rajesh Chavan

[Former Member · Accepted solution]

HI,

1) While extracting "Look-Up" values from SAP R3, Do we have to extract ?Code? and ?description? both or either one of them. For eg. For country look-up table "DE" or "Germany".

While Extracting you may extract both the fields - Code and Description , provided if you are using these two fields in your MDM Repository.

I would Suggest to extract both fields since its more meaningful.

2) Can we use standard business content as it is? Because if we have to extract both values then we have to alter standard business content to store that values (Look-up)

Standard Repository will never give you a permanent solution for you r Business Needs.a repository should always be flexible .So A Customized One is recommended.

3) What to syndicate for Look-up data in main table. "Code" or "description" or "BOTH"?

Syndication is purely based on your target system.

Say if you syndicate to ECC , Code is needed

For BI, both Code and Description is needed.

Thanks,

Felix

[Former Member]

Hi Rajesh

It all depends on the requirements. Since code is mandatory field u need to import this from R/3.If u have say country name defined as field in MDM repository u need to import this also. alternatively whatever is imported from ECC still while creating the map,doing the field mappings you can decide for which fields you want the values to populate in MDM and say back to ECC while syndicating.

hope it helps

Regards-

Ravi Kumar

[Former Member]

Hi,

as all of our colleagues mentioned, it's a matter of how you want to use the repository. Usually, manual input is necessary to do some Harmonization, so I would recommend to use lookup tables with description to ensure the integrity of the data.

You're talking about Consolidation and Harmonization, so probably of different systems. Be aware that when you syndicate the codes to different remote systems, you need to maintain the codes also in your lookup tables, so you might have for value "DE, Germany" (the display fields in your lookup) a code "DE" for system A and also another entry for system B, Automap in Import and Syndication won't work without.

Hope this helps

Regards

Jutta

[Former Member]

Hi Rajesh,

Alok is right as far as you do not want to use a customized rep,But however if your requirement is such that the main table records are not coming with complete information and some of the data enrichemnt has to be done in MDM

for eg: When you are importing data into MDM say only you are populating som eof the necessary fields such as Material No,Old material id etc.

and you need that the remaining fields be populate in MDM using some workflows which are used by Data custodians.

Then the fields like Country may have to be filled by the data custodians by picking an appropiate value from the lookup

For that you can design your lookup in such a way that both the code and the name field are dsiplay field

So that when you pick that value from the dropdown from main table you know exactly that De stands for Germany and Us stands for America.

It all depends on your req ,for this you may have to use a customised rep.

If you are looking for jsut and R/3-XI-MDM integration scenario then waht Alok has mentioned is sufficient.

Hope it helps

Kindy reaward points if found useful

Thanks

Simona

[Former Member]

For all three questions only one answer:

Only Code is required field so maintain that field only.

Use stsndard content as it is.

If you dont have description field in lookup table in MDM, there is no need for description value.

and in R3, when we use that filed only code value is required.

Reward if useful.

BR,

Alok