MDM: how to approach development and other considerations

[Former Member]

Hi Experts,

I am very new MDM, and wanted to know how one should approve MDM implementation..

My queires are:

1) What is ideal condition for a system to be included as part of MDM

2) What are pre-requisite for MDM implementation

3) What kind of expertise or skills you need for implementation

4) How MDM fits with NW'04 and ERP2004 solution.

Thanks and regards,

[Former Member · Accepted solution]

Sudhir,

After Ravi's great explanation, I have only a couple of comments (from my project experience) to add to some of your questions.

The need to distribute data to multiple target systems in near real time is also an important criteria for choosing MDM to be the central data bub. MDM can be a one stop shop for all the master data in your organization.

MDM has very flexible database configuration including security using a console, nice UI for viewing as well as manual data maintainence, Import manager to bring data from multiple systems, consolidate and present a homogenous view, and a syndicator to perform target system based extracts that are net change only.

You have XI available for integration layer. If not XI, you have other middleware available. Java API or COM API act essentially MDM adapters or eways, where you can use MDM system functions to post or retrieve data from repository. UNIX as well as Windows version of server is available.

There are hardware and software prerequisites from the standpoint of RAM and CPU. Service market place has the exact recommendations for these.

Analytical skills, knowledge of DBMS principles, thorough understanding of your own business landscape, and an aptitude to learn- You are good to go If you want to code the API layer, you additionaly need java skills or some other programming skills.

Good luck!

Savi

[Former Member]

Closing old messages, not relevant now.

[Former Member]

Hi Sudhir

1) A MDM project has to take into account Data & Data Processes

What is the current state of the master data you want to store in MDM? In how many systems does it reside? What is the appropriate data schema for the data hub?

Getting data consolidated cleansed and normalized from multiple systems into a standardized structure is not an easy task.

2) You need to make sure that during your project you take care of the "Data flow processes" within your organization. Is the data flow before MDM and after going to be the same? Who in the organization will be responsible for the data that resides in the main hub? Who keeps it clean and up-to-date?

I think that the process questions that need to be considered during a MDM project are much heavier than the actual implementation using SAP MDM (which is an amazing tool). So, while implementing MDM you will also need Data Specialists – people who understand the actual data you are dealing with and the data processes that are relevant for that type of data.

To the best of my understanding & experience a MDM project can have a strong impact on the implementing organization.

Charles

[Former Member]

Hi Sudhir,

After reading the excellent answers posted by RaviKumar and Savitri, I do not have much to add. But, personally I feel, asking the following questions to yourself will always help before thinking about implementing MDM.

1. What are your organisation's Master Data needs?

2. How critical it is to maintain the Master Data centrally and then distribute it back to source systems in your organisation?

3. Is there any process in my organisation that demands the Master Data Management?

4. How does moving the master data maintenance to a central location help/affect my System landscape?

5. Can my organisation withstand the process changes driven by implementing MDM?

Regards,

Rajani Kumar

[Former Member]

Sudhir,

1) What is ideal condition for a system to be included as part of MDM

Whenever there are mutliple systems that are trying to maintain Master Data by their own, and every systems starts maintaining it their way rather than having a common understanding, you end up have duplicate data. That is when MDM comes into pciture. This will act as central place for all the Master Data objects. So, if a system has to be considered to be a part of MDM, it should be using the Master data along with other systems and also there might be some field which only this system might need. So, you maintain the common fields in the MDM system and the system specific field in the respective systems.

2) What are pre-requisite for MDM implementation

If you are asking for a technical pre-req, there are not many. MDM is an application that can be installed on your desktop as well. However, depending in the size of the database you accordingly design your landscape. As of now it does not need WAS for installation, its a stand alone piece.

3) What kind of expertise or skills you need for implementation

If you are planning on to use XI for integrating MDM with other systems, you would need XI skills. If you are planning to use EP to display and maintain (MDM SP3 - Maintenance iViews) data, then you would need to EP skills as well. If you are planning to develop some custom screens you can use the Java / COM API's and access the data.

4) How MDM fits with NW'04 and ERP2004 solution.

If you see the roadmap of MDM, SAP is planning to make the integration with SAP functional products and MDM tighter so that data can be sent back and forth easily. MDM right now is a part of NW04 stack, although it does not follow the standard WAS architecture. SAP R/3 has already some patches available for extracting the data that MDM can use.

I hope these answers your questions. Let me know if you need anything else.

Regards,

Ravi

Note : Please reward points if this helps you.