Skip to Content
avatar image
Former Member


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,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Sep 11, 2006 at 02:43 PM

    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



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      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,


      Rajani Kumar

  • avatar image
    Former Member
    Jun 15, 2007 at 05:57 PM

    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,


    Add comment
    10|10000 characters needed characters exceeded