MDM 321 – SAP Netweaver Master Data Management

Symptom
Import Manager (or MDIS) throws a validation error over an XML file which is valid according its XML schema (XSD file).
The validation error message is: “… the primary document entity could not be opened …”
Reason and Prerequisites
This could be caused when the “URI” property of the corresponding XML Schema which contains an invalid value. This URI property could be set per XML Schema under the Admin node via the MDM Console tool.
URIs are used to include information that are not available in the XML schema (XSD)itself. When the XSD is being parsed, the Xerces XML parser will try to use the URL supplied for URI to obtain object instance information. If the URL does not exist, Xerces will throw that error message.
Solution
Clear the [...]

Symptom
You are trying to upload a new PDF/Image file to the MDM PDF/Image Table using the MDM Portal iViews but receiving a “com.sap.mdm.internal.protocol.manual.ServerException: Illegal value for parameter” error.
Other terms
MDM, Portal, iView, PDF, Image
Reason and Prerequisites
When uploading a PDF/Image file to the PDF/Image Table using the MDM Portal iViews, the PDF/Image is uploaded without a thumbnail while the MDM Server is expecting to get it with a thumbnail.
Solution
Make sure that the repository in question has “Allow invalid PDFs” property set to “Yes”.
To do that please perform the following steps:
1. Log on to the MDM Console.
2. Connect to the repository which the MDM iViews are connected to.
3. Right-Click on the repository and select “Properties”.
4. Make sure that the property “Allow invalid PDFs” is set to “Yes”, and for [...]

Symptom
You have been requested by SAP support to upload a special customized .PAR file to your Portal environment.
Other terms
MDM, Portal, PAR, Custom
Solution
In order to upload the custom .PAR file, please perform the following steps:
1. Log on to you Portal.
2. Go to “System Administration”->”Support”.
3. Under “Top Level Areas” select “Portal Runtime”.
4. Under “”Portal Anywhere” Admin Tools” select “Administration Console”.
5. Under “Archive Uploader” click “Browse” and select the custom .PAR file you would like to upload to your Portal.
6. Click “Upload”.
7. Check that you see a confirmation message stating that the archive was successfully uploaded.
8. Log off and log back on to the Portal.
Attached you will find a Step by step screen captures of how to execute the exact same steps.

Symptom
Cannot create a new syndication map of type XML Schema which is embeded in the repository (or with an external XML schema file) since the Root dropdown list is empty/disabled.
MDM Syndicator does not recognize the root element of the XML schema.
Reason and Prerequisites
This could be caused because MDM 7.1 does not support XML schema files which include target namespaces other than unnamed one.
Solution
Amend the XML schema (XSD) file to be a valid one without the schema attributes targetNamespace and xmlns: .
Next major release of MDM (7.3) would include a more complete namespace handling.

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
After importing 3000 records into an empty MDM main table, only 2969 records appear in the Data Manager when looking at the main table.
Other terms
CSN 2790606
Reason and Prerequisites
Import Manager and Import Server actually import 2969 records from the source file although they both declared to import 3000 records. Import Manager has 3000 in the Default Import Action and Import Server log file declared that “Import action: Create: 3000″
Solution
This is MDM Import (Import Manager and Import Server) correct behavior.
The import tool shows a greater number of records since finding duplicated records is preformed only when the Import process is actually executed and its embedded within the import process in run-time. (To find the duplicated record you can import the source file into MS-Accesses.)
In [...]

Symptom
Can not connect using LDAP (User Not Found)
Other terms
AD, Active Directory,
Reason and Prerequisites
The Base DN covers the Groups folder but doesn’t cover the Users folder.
Solution
Set a Base Dn (in the mds.ini file) that covers both the Groups folder and the Users folder.

Symptom
When connecting with an Excel source file to the Import Manager the following error message appears: “Logon error: could not find installable ISAM.”
Reason and Prerequisites
There is a semi-colon ‘;’ in the name of the source file.
Solution
Delete the semi-colon ‘;’ from the name of the source file.