MDH and CMDM

[Former Member]

Hi,

Could anyone explain what is the exact difference b/w Master Data Harmonization and Central Master Data Management? I read the documentation but couldn’t really differentiate the point-to-point difference between these two functionalities. For E.g: Part 2a & Part 2b in MDH looks similar to Part 2 of CMDM

Thanks and Regards,

Sam Mathew

[Mark63]

The main difference is that Master Data Harmonization is focused on managing globally relevant (identifying) master data attributes, whereas Central Master Data Management is finally aimed at handling all master data attributes centrally. Therefore, local maintenance is not foreseen in Central Master Data Management.

Kind regards,

Markus

Message was edited by: Markus Ganser

[Former Member]

Thanks Markus. Would you please give me an example for MDH?

[Mark63]

Master Data Harmonization Example:

While the consolidation of objects is necessary for quality master data management, it is not in itself sufficient for the needs of enterprises operating large distributed IT landscapes on a global scale. Consistent maintenance and distribution — which leads to the permanent harmonization of master data — is also required. Through the use of global attributes (for example, name, address, or banking information) companies can ensure that all systems receive the same master data during distribution. Thereafter, these distributed objects can be enriched with additional attribute values in the Master Data Clients (for example, pricing data which is only relevant in the local procurement system).

[Mark63]

Master Data Harmonization Example:

While the consolidation of objects is necessary for quality master data management, it is not in itself sufficient for the needs of enterprises operating large distributed IT landscapes on a global scale. Consistent maintenance and distribution — which leads to the permanent harmonization of master data — is also required. Through the use of global attributes (for example, name, address, or banking information) companies can ensure that all systems receive the same master data during distribution. Thereafter, these distributed objects can be enriched with additional attribute values in the Master Data Clients (for example, pricing data which is only relevant in the local procurement system).

[Mark63]

Master Data Harmonization Example:

While the consolidation of objects is necessary for quality master data management, it is not in itself sufficient for the needs of enterprises operating large distributed IT landscapes on a global scale. Consistent maintenance and distribution — which leads to the permanent harmonization of master data — is also required. Through the use of global attributes (for example, name, address, or banking information) companies can ensure that all systems receive the same master data during distribution. Thereafter, these distributed objects can be enriched with additional attribute values in the Master Data Clients (for example, pricing data which is only relevant in the local procurement system).

[Mark63]

Master Data Harmonization Example:

While the consolidation of objects is necessary for quality master data management, it is not in itself sufficient for the needs of enterprises operating large distributed IT landscapes on a global scale. Consistent maintenance and distribution — which leads to the permanent harmonization of master data — is also required. Through the use of global attributes (for example, name, address, or banking information) companies can ensure that all systems receive the same master data during distribution. Thereafter, these distributed objects can be enriched with additional attribute values in the Master Data Clients (for example, pricing data which is only relevant in the local procurement system).

[Mark63]

Master Data Harmonization Example:

While the consolidation of objects is necessary for quality master data management, it is not in itself sufficient for the needs of enterprises operating large distributed IT landscapes on a global scale. Consistent maintenance and distribution — which leads to the permanent harmonization of master data — is also required. Through the use of global attributes (for example, name, address, or banking information) companies can ensure that all systems receive the same master data during distribution. Thereafter, these distributed objects can be enriched with additional attribute values in the Master Data Clients (for example, pricing data which is only relevant in the local procurement system).

[Former Member]

So am I correct in understanding that MDH is distribution of master data to all Master Data Clients based on global attribures and CMDM is for centrally creating and maintaining master data?

[Mark63]

Yes. CMDM also includes distribution of centrally maintained master data to the connected Master Data Clients.