MDM 321 – SAP Netweaver Master Data Management

Symptom
You use SAP NetWeaver Master Data Management. You want to load master data from a SAP Remote System (R/3, ERP, CRM, SRM) into your MDM repository.You use MDM’s local extractor (transaction MDM_CLNT_EXTR) for this purpose.
Other terms
MDM, MDM_CLNT_EXTR, MDM_BATCH_EXTRACT, Inbound, Import, Master Data Extraction
Reason and Prerequisites
SAP NetWeaver MDM is currently not able to pull data from SAP systems into its storage. A SAP Remote System needs to push the data to MDM.
Solution
This note provides an overview of the local extractor (transaction MDM_CLNT_EXTR) and its handling, known and related issues, and so on.Please refer to the attached document as well as the related notes.
If neither the document nor the related notes seem to solve your issue, open an OSS message that contains the logon data [...]

Symptom
We are trying to connect MDM Import Manger with Type = Port at the “Connect to source” screen and it is failing with error message “Could not retrieve source file for port…”.
Other terms
0000676967 2009
Reason and Prerequisites
Various ways could lead to this situation, for example:
1) Momentary “disappearance” of the NFS which host the Distribution folder.
2) Unsuccessful node failover in the cluster.
3) A human moving the file from the Exceptions into the Ready in order to try to re-import.
Solution
Please try the following solution in order to solve this issue:
1) Save the erroneous file structure (the file from structuralX folder) into temporary folder.
2) Stop MDM server.
3) Rename the mds.ini file to any temporary file name. This is to enforce MDM server to crate a new mds.ini file.
4) [...]

Symptom
You would like to delete one or more Import maps from the MDM Import Manager
Other terms
Import Manager, MDM, Map, Delete
Solution
The simplest way to delete a map in the Import Manager is in the
following way:
1. Log on to the Import Manager.
2. Press “File->Open…”
3. Select the map you would like to delete from the available maps.
4. Press “Delete”.
5. Conform deletion of the map by press “Yes”.

Symptom
Import Server fails to load the file with the following error message: “Can’t find even one field that is mapped.”
Other terms
651900 2009 mdis
Solution
The issues is that the wrong delimiter is defined.
For example:
The source file has a “;” (semi-colon) for a delimiter but the port is set up as “|”. Please change the delimiter in the port to match the source file (or visa-versa) and the file will then be imported correctly via the Import Server.

Symptom
The import server fails and the following error, or similar, is written in the log file under the distribution folder:
Error: The import map is not complete:1. Missing the XML Root Element.2. There are multiple root elements defined in the xml schema.Solution: Please select the proper root element via the IM GUI then save the map.
Other terms
mdis import server automatic
Solution
Connect to the source as you did previously and open the map. Once the
map has been opened save the map again and then rerun the import server.

Symptom
Import Change File using CST+ doesn’t work.
Other terms
schema Migration, Transport,
Reason and Prerequisites
The MDS is hosted on a UNIX box and the Console (WIN application) can not brows to the UNIX file system.
Solution
1 – In MDM 7.1 SP03 the “File Open” dialog is changed to a list of files in the Transport/Inbound directory. So with SP3 there will be a permanent solution.
*** In the mean time ***
2 – Please set up a share from the CTS+ host system (UNIX) to the
/Transport/Inbound location.
If the MDM Host is the same UNIX system it is sufficient to set the
DEPLOY_OUTBOX parameter direct to the MDM Inbound location.
(You could use a WIN2UX sharing system like Samba)
The MDM Console needs to have read access to any folder the CTS+ system
is deploying the file [...]