I am sure you know this situation: You have found a bug in the SAP MDM and you want to create an OSS message. The first question of the guy answering the OSS is: Can you send me all details about your MDM environment and also all the log files and an archive of the repository. To gather all this information it takes a lot of time and you can be sure that you will forget some essentail information.

But there is a tool which does all the work for your: the SAP MDM Info Collector. This tool provided from SAP.

You have to copy the whole folder in \usr\sap\ folder and configure the Java Virtual Machine path in the start script.

After that you can run the start script and you can see the info collector.


To download the info collector just open note 1522125 and follow the instructions

Hinweis 1522125 – MDM Info Collector: Snapshots zur Offline-Analyse anlegen


In order to plugin easily some search components, result set components and item details components without any programming you can use the so called master application. This application allows you to connect these components without any effort.

Following link can be plugged together


The component names must equal to the names configured in the WD Config.

Also the action MDM_WD_TEST_APPLICATION must be added to a role which is connected with the user.

After that you will get a view with all that components connect with each other.


This post tries to guide you, how to configure webservices in combination with SAP Master Data Management.

Prerequisites are that at least following components are deployed to your SAP Netweaver AS:


First of all you need to create a destination using the link http://<host>:<port>/mdm/destinations. If no trusted connection is implemented you need to enter here a valid user for the repository.

This destination allows you now to connect to your MDM Server.

After that you need to create your webservice. Via the link http://<host>:<port>/mdm/wsgenerator you can create your webservice. This webservice can then be deployed on your SAP Application Server.

If you try then to execute the webservice via the Webservice Navigator (http://<host>:<port>/wsnavigator) you will get an error message call „connection_3005-Cannot connect with MDM using destination“. The solution is to configure the user for your application in the right way. By default the „Admin“ user is used. In order to change it go to the Netweaver Administrator (http://<host>:<port>/nwa) and go to Configuration -> Infrastructure -> Java System Properties. Then go to Application and search for your Webservice application and select it. Then you can find in the tab Properties the user and password which is used to authenticate against the MDM. Change this user and password to a valid combination and it runs.


During the development of a SAP Netweaver MDM Application you often need the record ID in order to do some debugging or something else.To retrieve the record ID for a normal table you creat a webservice with a retrieve operation, use the webservice navigator to execute this webservice and in the end you get the record ID. A pretty long way for such a simple piece of information. But especially for the PDF table or other internal tables there was no way to retrieve this via a webservice.


There is also a more convenient way of retrieving this information: You can use the Data Manager!!


Just a simple adaption in your registry enables a tooltip in the data manager:


  1. Go to windows registry (regedit)
  2. HKEY_CURRENT_USER -> Software -> SAP -> MDM 7.1 -> Client (select Client)
  3. Add new ‘String Value’: ‘Show RecordId In Tooltip’ with the value ‘True’.

If you restart the Data Manager you will see the record ID of each record as a tooltip over the first column normally indicating if a record is protected or not:

Impressum Suffusion theme by Sayontan Sinha