MDM projects that implement a custom data model, or extensions to the standard models, will need to include a site-specific strategy to document and migrate changes.

1. The data model for a repository can be exported from the console as a complete schema and selected changes then imported into a target repository. This feature, delivered with SP4, is the only way to reliably transport incremental changes to your MDM data model.

2. Validation Expressions and MDM security configuration are two areas of custom configuration that cannot be migrated from the console. These will need to be manually re-applied to the target repository.

3. Maps saved via the Import Manager and via the Syndicator can be saved to the file system and migrated with relative ease into the target repository. This requires the source and target tables be absolutely identical.

4. MDM does not currently provide a physical report that documents the meta model — the metadata for the model, validation expressions, security, port configuration, etc. The Java API however completely exposes the meta model, with the exception of expressions. The following specification can get you started on building your own MDM meta model report.

By: MD in searchsap.techtarget.com

Easy Point-in-time backups of MDM Repostiories are possible in several ways. Each of these operations is available as a CLIX command, to be scripted for your favorite OS command line:

* Master Slaving: Create a Slave Repository mounted on a separate MDS instance. Synchronize (refresh) it at your desired interval. This provides a live read-only mirror of your original repository. Normalize the slave to get a writeable copy.
* Archiving: Create periodic archives of your repository. This generates “.a2a” files in the “/Archives” folder of your MDS installation. Note that the filenames are datestamped, but not timestamped. Rename or relocate the files if you need to generate archives more than once a day.
* Duplication: Create a duplicate of the repository to make a writeable clone available e.g., for training use.

By: searchsap.techtarget.com

If your MDM scenario has a significant number of data-entry capable end users, then take some time to integrate MDM with your corporate LDAP. This will greatly simplify the process of maintaining MDM users and defining their roles and capabilities. At a minimum, your users will thank you for not having to remember yet another application-specific password!

You will need to modify mds.ini for each MDS instance to include this section. Example:

[MDM LDAP]
LDAP in Use=false
Server=Your.LDAP.Server (e.g. ad.yourcompany.com)
Server Port=xxx
Base DN=OU=Portal,DC=ad,DC=yourcompany,DC=com
Admin Name=PickAName
Admin Password=PickAPassword
Admin Identifier=cn
User Identifier=sAMAccountName
MDM Roles Algorithm=GroupMapping
MDM Roles Attribute=MemberOf
Fallback in Use=True (Falls back to MDM Password for non-LDAP Users)
Fallback Roles=
Fallback User=
Fallback Password=
Allow Referrals=False
Trace Level=1
MDM Email Attribute=Mail

By: searchsap.techtarget.com

MDM Realtime Interview Questions with Answers

1) What platforms are supported with SAP Master Data Management?

2) How integrated is SAP NetWeaver MDM 5.5 with SAP NetWeaver and applications?

Ans. SAP NetWeaver MDM 5.5 is an integral part of the NetWeaver stack. In the current feature release, enterprise application integration, both SAP and non-SAP, is accomplished through SAP XI. Interoperability with other systems is possible via SAP NetWeaver MDM 5.5’s APIs (including ABAP whose development is currently in process). Tight, native integration is part of the SAP NetWeaver MDM 5.5 roadmap and further pre-built integration points will be rolled out as we progress along the development path. SAP MDM 5.5 SP2 will provide view-only iViews for SAP Enterprise Portal.

3) Is the Product Catalog Management application part of the SAP NetWeaver Integration and Application Platform? Does print publishing belong to this platform as well?

Ans.Yes, these are all part of the SAP NetWeaver platform and print publishing is an extension of the capability to product content management. By definition, this is the case since the former A2i xCat application, now further augmented and known as SAP NetWeaver MDM 5.5, is part of the SAP NetWeaver MDM family of products.

4) How will MDM fit into Enterprise Services Architecture? Which Web services will be provided and when?

Ans.MDM is integral to SAP’s ESA strategy. The initial list of documented Web services with MDM 3.0 were provided with MDM 3.0 information release. These refer to the ability to access master data information in MDM as a service to create records, etc. New web services will be available as per the roadmap. With SAP MDM 5.5 in conjunction with SAP Exchange Infrastructure, one can create web services by exposing MDM functions using MDM JAVA or .NET APIs.

5) What tools are available to integrate SAP MDM and other non-SAP applications and platforms?

Ans. SAP MDM 5.5 exposes its core functions using published JAVA and .NET APIs. Any integration between MDM and other non-SAP software can be handled using APIs. Also, MDM functions can be exposed as web services using APIs in conjunction with SAP Exchange Infrastructure. Broader integration between SAP MDM 5.5 and other SAP NetWeaver components will be available through product roadmap.

6) What options are available for resending from MDM within XI or R/3 in case an update fails?

Ans. If the failure lies with XI or R/3, the same XML can be reprocessed (no resending is required). If there is a validation or data problem, the records needs to be identified and modified in MDM Data Manager Client and the Syndicator batch will resend them as they were updated since the last syndication.

7) How easy is it to maintain the front-end when the data model changes?

Ans. The effort depends on the number of fields required for the front-end. Fields that are added have no impact. Fields that are deleted (and maintained in the front-end), need to be removed. Fields that are renamed need to be updated.

Is it possible to develop web forms (outside of EP6) that link to standard Java MDM APIs and communicate with the MDM repository?

Ans.Yes it is possible as you are not limited to the use of iViews that exist. Your own application-specific iViews can be created. You can also access the server with direct calls to the API from the java environment.

9) Is it possible to assign the saved search criteria to a role or person to restrict what he or she can view in the search?

Ans.The saved search option is client computer specific. That means that a user’s search criteria are available only to the user and not to other users. Therefore the saved search is not an option in this case. Using role constraints you may achieve the required results.

10) Are adapters/extensions available in MDM for integrating monitoring tools? (ie. does Tivoli register if an exception occurs in MDM?)

Ans. MDM currently does not trigger external processes on errors. The system uses logging capabilities to register errors and there are specific log files for the various components of the system. If the monitoring system/s can be triggered on changes to the log files then the system can be monitored.

By: http://www.sapmdm.co.in/

Q: Can we specify the “Ready” and “Archive” folder to be folders other than the folder under MDM program folders. One example is to specify a folder in a remote server as the “Ready” folder.

A: Yes. Configure these values in mds.ini file.
Ex:
Archive Dir=C:\PROGRA~1\SAPMDM~1.5\Server\Archives\
Distribution Root Dir=C:\PROGRA~1\SAPMDM~1.5\Server\Distributions\

These folders can be anything as long as MDM Server has access to those directories in the Remote Server.
After you set the property for Distribution Root, then create the Port in Console.

Q: Is it possible to configure some notification mechanism before import server overwrite records in MDM server? For example, before import server overwrites some records, a mail is sent to somebody for a confirmation?

A: In the Import Map, you can configure the workflow to launch once the data is imported.
Configurations->Options in Import manager.

When you create the workflow, the Start Step of the workflow, select Check out records. The second step is to send the notification for someone to review.

For this you have to configure the mail server property in mds.ini file.
This property has to be set for every repository in mds.ini file

Mail Server=mail.domain.com

The MDM architecture can be described as follows:

●      A user-centric data access layer provides user interfaces to support end-to-end master data maintenance processes. Specific portal iViews enable task-oriented UIs for occasional users without the need for local installations. These generic iViews are highly configurable and provide workflow integration to the Universal Worklist (UWL). In addition to these portal-based UIs, MDM features high-fidelity Microsoft Windows-based user interfaces to support specific key user activities (MDM Import Manager, MDM Data Manager, MDM Syndicator and MDM Publisher).

●      The MDM Server is the central storage location of all repositories and contains functions such as the engines for searching, matching and validating. Repository schemas can be flexibly designed in a model-driven approach utilizing the meta-model of MDM. The MDM Server provides the latest in-memory technology to guarantee instant data access and fast search results.

●      SAP NetWeaver MDM features the following integration portfolio including required SAP NetWeaver products to communicate with business applications (SAP or non-SAP):

○       The MDM Import Server and MDM Syndication Server support the automated loading and distribution of master data to and from the MDM Server in close cooperation with SAP NetWeaver Process Integration.

○       Technical monitoring of the MDM Server components using CCMS and ABAP APIs is supported by the SAP NetWeaver Application Server. Three types of APIs in combination with generic Web Services provide efficient access for developers embedding MDM into applications or building composite applications.

○       To improve data quality in BI, MDM features integration content and direct connectivity with BI.

○       Enterprise Search connectivity is provided to integrate MDM into company-wide searches.

SAP NetWeaver Master Data Management (SAP NW 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 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:

1. Content Consolidation – centralised cleansing, de-duplication and consolidation, enabling key mapping and consolidated group reporting in SAP BI. No re-distribution of cleansed data.
2. Master Data Harmonisation – as for Content Consolidation, plus re-distribution of cleansed, consolidated master data.
3. 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.
4. 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 Desktop Publishing packages.
5. 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.

Q: What is the main purpose of MDM Data Manager? What are the functions it perform?

A: In data manager we can do host of activities:

Creating/change/delete records.
Defining hierarchy/taxonomy table in respective modes. Linking of Attributes
Performing drill down search and free form search
Data governance:writing validations n assignments.Executing them.
Creating workflows and executing steps of workflow
Matching mode used for matching n merging of records in MDM once rules and strategies are defined.
Family Mode and Publish mode for creating catalogs.
Several others..refer to data manager reference guide for MDM.

Q: Is there an export feature in MDM Data Manager that would enable to obtain an excel extract of record details which also include validation result
columns ?

A: The export feature of the data manager, exports just the fields of the repository in an excel. However for this requirement, there can be a workaround. Create a status flag and assign it your validation result. As this status flag is now a part of your repository you can export it.