About MDM 5.5

[Former Member]

Hi,

I would be very grateful to you if you answer the following questions:

1. Can we have an illustrated difference between Qualified field, Qualifiers, Product families & Data Groups?

2. Whether cross compatibility for different ERPs will be provided or not? (for Siebel, PeopleSoft etc)

In case of MDM 3.0, it was supposed to be developed <b>on Project Basis</b>.

3. Can we build a legacy system on top of Central Repository? If yes, how? Is Reverse Engineering possible?

4. Will there be separate repositories for IT scenarios, GDS & Catalog publishing?

How data is harmonized in SAP MDM 5.5? What is the difference between Syndicator, GDS & SCM?

(Don't they have overlapping functionality?)

Thanks in advance.

Cheers,

<b>Satyen</b>

[Former Member · Accepted solution]

1. Can we have an illustrated difference between Qualified field, Qualifiers, Product families & Data Groups?

The product families enables the repository content to be efficiently published not only to paper, but also to non-paper media like web. Whereas, datagroup are used to break the entire set of objects(pdfs, images etc) in the repository into the meaningful subgroups. This can compared with taxomany, which is used to define the heirarchy of categories.

2. Whether cross compatibility for different ERPs will be provided or not? (for Siebel, PeopleSoft etc)

In case of MDM 3.0, it was supposed to be developed on Project Basis.

There is no out-of-box support for integrating Siebel or peoplesfot etc.

3. Can we build a legacy system on top of Central Repository? If yes, how? Is Reverse Engineering possible?

I am not sure of what do you mean by building legacy systems. But MDM provides a set of java and com based api's to build applications using central repository.

4. Will there be separate repositories for IT scenarios, GDS & Catalog publishing?

How data is harmonized in SAP MDM 5.5? What is the difference between Syndicator, GDS & SCM?

As far as my knowledge goes there is no separate repository for IT scenarios, GDS and catalog publishing. GDS stores the trade item data in MDM repository iteself.

MDM data is harmonized by using the syndicator/Import manager and XI(for connecting to different systems).

Syndicator is a tool to export a subset of the repository data(could be anytype of master data) to other systems in either XML format or

text file. GDS console is used for enhancing and synchronizing the data with data pools.

I am not sure of the context for SCM here.

Sreekanth

[Former Member · Accepted solution]

> 4. Will there be separate repositories for IT

> scenarios, GDS & Catalog publishing?

> How data is harmonized in SAP MDM 5.5? What is the

> difference between Syndicator, GDS & SCM?

>

> As far as my knowledge goes there is no separate

> repository for IT scenarios, GDS and catalog

> publishing. GDS stores the trade item data in MDM

> repository iteself.

Though GDS is an application built upon MDM platform and uses hence its repository this repository can not be used for other purposes than GDS. In other words, this is a private GDS repository and if you want to leverage product data for other purposes you have to build another MDM repository.

In regards to IT scenarios it actually depends on your business scenarios. It may be one repository used for harmonization and central data management or two different. Anyway it's one repository per object family (Customers, Products, Employees and so on)