cancel
Showing results for 
Search instead for 
Did you mean: 

MDM - SRM

Former Member
0 Kudos

Dear All,

We are currently in the design phase for SAP SRM implementation. There are 2 countries that are currently operating on SAP R/3 and that will be included in the SRM implementation.

In order to harmonize the master data of these 2 countries we plan to use SAP MDM. What we believe is that not the full capabilities of MDM will be required in our case. Materials and vendors are the two contents for the Master Data Harmonization.

What we want to know is whether MDM is really required for Master Data Harmonization.

If MDM is not used, how can the central repository for Master Data be managed? In our case we need to harmonize the master data from different countries. For example a material may have the material code "1" in Country X and the same material may have the code "2" in Country Y. We need to mark this item as, let's say, "A" in the central repository. Is this possible without MDM?

Thanks in advance,

Emre

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Emre:

I've seen some scenarios like these, when the customer doesn't really "see" the benefits for MDM. Under your circumstances, you could use Equivalence Tables and manage the translation...

Please remember that in this case, you would be responsible of managing those tables (on each side of the landscape, because translation should be back and forth) and also you should manage the integrity. As you say, you should consider if this management is worth enough MDM.

Besides Data Harmonization, you could also use MDM as the SRM Catalog (using the OCI interface) and Central data management, meaning that you can centralize all data stuff on one single instance and assure that changes will be reflected all over your landscape.

If you were to add new systems, on MDM you won't need to work a lot. In the case of maintaining multiple equivalence tables, you would have to make sure you update all tables accordingly.

I hope that helps

Greetings!

Alejandro

Former Member
0 Kudos

Hi Alejandro,

Thanks for your reply.

We don't have central master data management in our scope. What we need is to assign to each master data a "global" code, but not to change the original master data code. So it is a homogeneity model rather than uniformity model.

In this case do you still think that MDM is not too much for us? We need to keep the efforts on MDM side at as minimum level as possible.

Best regards,

Emre

Former Member
0 Kudos

Hello:

Perhaps you should only consider maintaining the equivalence tables, if you think that's not too much work.

MDM might be too much if you are not considering all the other IT scenarios

Greetings!

Alejandro

Former Member
0 Kudos

Hi Emre,

Using MDM, you can achieve the perfect harmonisation scenario.

However, in your case as central data management is not in the scope, then MDM shall be to big a thing for storing mapping or equivalenc tables.

However, have you considered the scenario where at both places the same data is referred but have inconsistencies in their respective properties. In that case, its always better to have a central repository and all other systems then can be in synchro with this data. Changes in any system are reflected in all the systems.

I have a doc which shall brief you on MDM and its capabilities. Shall forward it you. Leeme know ur email address.

Hope that helps!

Regards,

Tanveer.

<b>Please mark helpful answers</b>

Former Member
0 Kudos

Dear Tanveer,

Thanks for the reply.

Do you also know an approximate effort estimation for MDM implementation? We will harmonize materials and vendors master data, nothing else.

Best regards,

Emre

Former Member
0 Kudos

Hi,

Hope that the docs help you.

The effort estimation in MDM implementation depends mostly mainly on the complexity of master data.

Also, when implementing MDM, you shall find many technical bottlenecks as MDM is a new product. These all impact the efforts estimation.

I guess the question can be well answered by someone wo has been part of few MDM implementations. That shall help them to come up with specific metrics.

Hope that helps!

Regards,

Tanveer.

<b>Please mark helpful answers</b>

Former Member
0 Kudos

Hi,

MDM has a concept called "Remote Keys". In your MDM Repository, you can have a unique MDM specific ID for your Material, but can assign Material Code "1" for System X and "2" for System "Y". This way, whenever you syndicate your data, you can send back the appropriate code based on your System.

Regarding implementation effort, as Tanveer mentioned, this depends mainly on the complexity of data and possibility of using the standard pre-delivered repositories (If not, a custom repository needs to be built based on your requirements).

Hope this helps,

Regards,

Rajani Kumar

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Emre,

The company I work for is starting a similar project of MDM/SRM. It'll be very nice if we can exchange emails about yours implementation experience... What was your decision? You implemented MDM or chose to use equivalent tables?

Thanks in advance,

Gustavo