MDM

[Former Member]

HI,

New to MDM, I request for what is the purpose of MDM briefly and tcodes

Regards,

nagaraju

[Former Member · Accepted solution]

Hi Nagaraju,

SAP MDM is Data Management System means maintaining record in such way that, MDM is single point of truth for all the system with in Enterprise.

What we do actually in real time is.

First, we do get the data from SAP, Siebel, or Legacy System to SAP MDM.

And; we do consolidate the data in SAP MDM, which we had from different system.

Master Data Consolidation: consolidate the entries on global fields, and re-distribute the data to the original systems. In that scenario NO DATA is created in MDM. The added value is related to the fact that data will be consistent across the corporation. You may imagine that the difficulty here is to figure out which information should "win" in conflict cases. Here you need a good cleansing tool, with relevant matching strategies.

Then, we do Harmonization the data to all the systems using schedule or batch process from SAP MDM.

Master Data Harmonization: here the master data is copied from each client system into MDM. A matching needed in order to identify duplicates, and build the MDM translation tables that will allow to know where the data is, and which records correspond to the same real "object" in your different systems (Key Mapping Tables). In that case each single system just works as before, and the added value of MDM is that you know EXACTLY where you data is, and how many "real objects" you have across your systems.

Central Master Data Management: is the final leap. Here you go again one step further, and you start creating centrally data in MDM, and distribute it to the different client systems.

in SAP only few transactions are available for Master Data Extraction:

MDM_CLNT_EXTR: to extract standard master data in the form of IDOC's

MDMGX : To extract customized master data(custom table data extraction) in to XML file.

I hope it helps you.

Regards,

RDNPrasad.

[Former Member]

Hi Naga raju,

Adding to Krutharth , Also u can refer

http://hosteddocs.ittoolbox.com/RD021507b.pdf  Deploying SAP MDM if helpful.

http://en.wikipedia.org/wiki/Master_Data_Management

http://www.sap.com/platform/netweaver/components/mdm/index.epx

http://msdn2.microsoft.com/en-us/library/bb190163.aspx

http://www.cio.com/article/106811/Demystifying_Master_Data_Management

http://www.businessintelligence.com/print_research.asp?id=97

The following web-sites which give u detailed knowledge on MDM.

(This web-site gives introduction to MDM, Master Data Operations, Master Data Integration,MasterData Quality )

http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm

/people/nitzan.levi/blog/2005/06/20/the-story-of-mdm55

/people/sap.user72/blog/2005/06/14/worlds-fastest-and-shortest-introduction-to-netweaver-mdm-55

/people/ravikumar.allampallam/blog/2005/09/06/mdm-client-content-manager--different-modes

http://www.sapnetweavermagazine.com/archive/Volume_03_(2007)/Issue_02_(Spring)/v3i2a12.cfm?session=

http://www.sap.com/platform/netweaver/pdf/BWP_SB_Data_Unification.pdf

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9018dc62-23a8-2910-b7ae-9023670c...

MDM on help.sap.com

http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm

SAP mdm how to guides:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/5024a59a-4276-2910-7580-f52eb... [original link is broken]

MDM elearning:

https://admin.sdn.sap.com/irj/sdn/mdm-elearning

https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/bf0f8d87-0d01-0010-aa8b-f2c46a70557b [original link is broken] ( with screenshots)

1)https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60559952-ff62-2910-49a5-b4fb8e94f167

2 ) http://help.sap.com/saphelp_nw04/helpdata/en/0a/5f723bc34bf17ee10000000a114084/content.htm

I think it may help u

Regards

Hari

[Former Member]

Hi Nagaraju,

To make it clear i''d liek to share something about data and MDM.Data is the food for any system to run and master data is the heart of that system.Master data is that crucial information on which all your business process run.If your master data is not in proper shape the analytics run on them will be incorrect as a result the business decisions taken will be wrong and this will result in a complete failure of your business.

There are many ERP systems existing today but very few provide an effective,systematic and fool proof method to preserve a single version of truth odf your master data.

SAP MDM address this problem and so is here today to bring all your master data under one roof.

So,in general,benefits of keeping Master data in 1 place is

Conformance/Auditing

Single view of customer

Global data synchronization efforts

Accurate reporting

Consolidation after mergers and acquisitions

Reduced effort to consolidate information

Reduced cleansing/mapping of information

Increased efficiency

Reduced costs overall.

with this much details you can refer to the URLs which have detailed infomation about every aspects of MDM:

For detailed overview

http://help.sap.com/saphelp_mdm550/helpdata/en/47/1c5928cd0412b8e10000000a1553f7/content.htm

To know about Key capabilities:

http://help.sap.com/saphelp_mdm550/helpdata/en/46/b8065a4df01517e10000000a114a6b/content.htm

Read reference Guide of various modules of MDM:

http://help.sap.com/saphelp_mdm550/helpdata/en/88/9f9c427055c66ae10000000a155106/content.htm

I hope these documentation will help you in your reading.

[Former Member]

Nagraju,

See link this is bible of MDM: It includes what is MDM, purpose, scenarios, reference guides etc.

MDM SP06:

http://help.sap.com/saphelp_mdmgds55/helpdata/EN/43/D7AED5058201B4E10000000A11466F/frameset.htm

and for tcodes: There is no such tcode in MDM when you use MDM components, but when you will work on integration scenarios same tcodes of ABAP, XI and some from MDM generic extractor, CCMS will be used on R3/XI side not on mdm tools.

BR,

Alok

[Former Member]

Hi Nagaraju,

Master data management (MDM) comprises a set of processes and tools which centrally and persistently define the non-transactional entities of an organization (also called Reference data). The objective of MDM is to collect from, and supply to various processes, unique instances of each entity.

Uniqueness in this context is an aspect of data normalization which eliminates outright redundancy due to collection of instances from dissimilar sources.

The processes include source identification, data collection, data transformation, normalization rule administration, data storage, a service-oriented architecture, and data governance.

The tools include data networks, file systems, a data warehouse, a data mart, an operational data store, data mining, data analysis, and data visualization.

The selection of entities considered for MDM depends somewhat on the nature of an organization. A common case is the commercial business, for which MDM applies to such entities as customer (Customer Data Integration), product (Product Information Management), employee, and vendor. MDM processes identify the sources from which descriptions of these entities can be collected. In the course of transformation and normalization, the descriptions are conformed to standard formats and data domains, so that duplicate instances of any entity can be removed. The result of these processes would generally be an organizational MDM repository, from which, all requests for a certain entity instance produce the same description, irrespective of the originating sources and the requesting destinations.

The term recalls the concept of the master file from an earlier computing era.

Regards,

Sravan

[Former Member]

Hi,

Master data is the core data of an enterprise that exists independently of specific business transactions and is referenced in business transactions. It builds the foundation for the smooth execution of business processes and well-informed business decisions. Master data represents business objects rather than business transactions and is rarely changed over a long period of time. The following objects are among a company’s most important master data objects:

● Product

● Customer

● Supplier

● Employee

SAP MDM

SAP Master Data Management (SAP MDM)enables master data on customers, partners and products to be consolidated and harmonized across the enterprise, making it available to all staff and business partners. A key component of SAP NetWeaver, SAP MDM ensures data integrity across all IT systems.

The SAP NetWeaver Master Data Management (SAP NetWeaver MDM) component of SAP NetWeaver creates the preconditions for enterprise services and business process management. The functionality represents customers, products, employees, vendors, and user-defined data objects in unified form. With SAP NetWeaver MDM, customers can manage master data and supplemental content, such as texts, PDF documents, high-resolution images, or diagrams in a central business information warehouse.

SAP Master Data Management (SAP MDM) is a component of SAP's NetWeaver product group and is used as a platform to consolidate, cleanse and synchronise a single version of the truth for master data within a heterogeneous application landscape. It has the ability to distribute internally and externally to SAP and non-SAP applications. SAP MDM is a key enabler of SAP Enterprise Service-Oriented Architecture. Standard system architecture would consist of a single central MDM server connected to client systems through SAP Exchange Infrastructure using XML documents, although connectivity without SAP XI can also be achieved. There are five standard implementation scenarios:

Content Consolidation - centralised cleansing, de-duplication and consolidation, enabling key mapping and consolidated group reporting in SAP BI. No re-distribution of cleansed data.

Master Data Harmonisation - as for Content Consolidation, plus re-distribution of cleansed, consolidated master data.

Central Master Data Management - as for Master Data Harmonisation, but all master data is maintained in the central MDM system. No maintenance of master data occurs in the connected client systems.

Rich Product Content Management - Catalogue management and publishing. Uses elements of Content Consolidation to centrally store rich content (images, PDF files, video, sound etc.) together with standard content in order to produce product catalogues (web or print). Has standard adapters to export content to DTP packages.

Global Data Synchronization - provides consistent trade item information exchange with retailers through data hubs (e.g. 1SYNC) Some features (for example, workflow) require custom development out of the box to provide screens for end users to use.

For documentation u can refer

help.sap.com

Reward points if helpful

Regards

Nisha

[Former Member]

Hi,

when working in SAP R/3 MDM integration scenario u need these T-Codes

1.MDMGX- For extracting Customizing/Reference/Check table datas .Output is in the form of XML.

2.MDM_CLNT-EXTR : For extracting Main Table Records .Output is IDOCS(DEBMAS-Customer Master Data,MATMAS,CREMMAS).

PI/XI converts these Idocs into XML and post it to inbound ready folder of MDM Repository

3.While using ABAP API(APIs are used to connect and retreive data from MDM Repository ) u need MDMAPIC Transaction to configure the APIs

[Former Member]

MDM stands for Master Data Management.Master Data of an organization drives the Transactions .So Master Data quality directly influences the reporting quality.That is why Master Data Management has become such a prominent domain of expertise.

Organizational challenges are the “people” challenges – the ones that are introduced as a by-product of changing the way people both manage and view information. There are 4 issues to be taken care of broadly.

• The Strategic Vision

• Data Ownership

• Performance-Oriented Management

• Change Management

Operational Challenges

Choosing to deploy a master data management program is a strategic decision that reverberates across the enterprise.

Just like the operational challenges of construction projects are finessed through proper planning and governance, the critical operational challenges of MDM involve instituting the appropriate oversight into a rapidly changing environment, including:

• Data Quality Management

• Data Standards Management

• Data Governance

• Data Integration

Technology Challenges

Master data management is not just software; it is a solution that embodies a management program, linking technology, principles, and policies. Once the governance infrastructures are in place, and the policies have been defined and endorsed within the enterprise, though, there are a number of technical hurdles that must also be cleared for a smooth migration to the MDM environment:

• Selecting and MDM Architecture style

• Transitioning to the new infrastructure

• Performance

The IT scenario consists of the following scenario variants:

�� Master-data consolidation

Allows to identify identical master data objects within heterogeneous landscapes,

merge identical objects centrally, and provide the relevant key mapping information for

further use in business operations or analytics.

�� Master-data harmonizationOrganizations can cleanse master data on materials, retail articles, suppliers, and

customers and leverage the results to perform enterprise-wide analytics, such as

global spend analyses. Consolidated master data is then distributed to the connected

remote systems to streamline business operations based on high-quality data.

�� Central master-data managementOrganizations can consolidate and centrally manage their master data. They can

support company-wide quality standards by ensuring that central control of master

data begins as soon as the data is created.

The concepts embodied by a service oriented architecture (SOA) are often conveyed in the same breath as a master data management solution. And since a services-based approach can incorporate the way we address a number of these challenges, it is reasonable to consider SOA as part of your strategic vision, mostly as a way of integrating MDM within a governance framework.

For example, an assessment of the application architecture may reveal that similar approaches are employed by a number of different applications for the creation of a new customer record. In this case, a “master record creation” service can be configured to accommodate each of those applications requirements, which will both simplify future application development and ease the transition process. Applying this across all application requirements can both support a migration plan for applications as well as support the behavioral transition plan as part of change management.

In fact, because SOA can support the execution of the policies described within the data governance framework, the services-oriented approach can contribute to addressing most of the challenges described in this paper. Data ownership, performance management, data quality and data standards, data integration and the transition strategy can benefit from the identification and configuration of enterprise-wide set of services. By addressing these issues in a strategic manner, one can have high confidence in executing a successful MDM program.