MDM 321 – SAP Netweaver Master Data Management

Symptom
What does “Multithreaded Matching” mean? Does it mean the matching tasks can now utilize multi CPU cores?
Other terms
612386 2009
Solution
Multi-threading means a single matching request can be spread across multiple threads.
It is available in 7.1 SP 2, and 5.5.64.
NOTE about current multi-threading:
1) Does not help the transformation process when starting a matching
request.
2) Is essentially blocked in 5.5 when using token equals.
3) Reserves one core for other system request(you need to have more
than 2 cores to use this feature).

Symptom
The settings for all fields are set to “Ignore” and not to “Inherit Default” for Null Interpatation.
Other terms
618119 2009
Reason and Prerequisites
When a new map is created the ‘Inherit Default’ option is automatically
selected. Most likely whenever the map was created the ignore option was chosen in place of the ‘Inherit Default’.
Solution
Unfortunately the only way to “fix” this is going field by field that
you want the Nulls to overwrite the data and manually change them to
inherit default.

Symptom
After mapping a source field value to a destination field value and saving the map – when you reopen the map the value\s are mapped to a different value from the one you mapped originally.
For example: The value 123XL has been manually mapped to the value XL123 and the map saved. However in the repository the key mapping value for 123XL is XL, so upon reopening the map the value will be automatically mapped to its key mapping, XL, and not the manually mapped values of 123XL.
Other terms
O666716 2009
Reason and Prerequisites
Key mappings override manual mappings.
Solution
Delete the unwanted key mapping\s from the remote key of the record value via the Edit Record Key Mappings option in the Data Manager for the said table.

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 running the Verify/Repair the GUI clients exhibit strange behavior or the data appears to be incorrect in the reposiotry.
Other terms
attachment 649634 2009 image blob binary object
Reason and Prerequisites
The repository was loaded immediate after running Verify/Repair.
Solution
After running the Verify/Repair option from the ConsoleALWAYSload the repository with theUpdate Indicesoption.

Symptom
The Import Manager shows an error message while trying to choose the field name “NUMBER” (the fields type is Text) as a matching field.
The error message (appear in a pop up): “Unable to retrieve records for table ‘import’”
Other terms
0000686420 2009
Reason and Prerequisites
The issue is caused by the xml source file element containing a dot (’.’) within its name.
For example: element name = “Art.nr.”.
Import Manager currently does not support an element (which will become a field) to use ‘.’ as part of the name. This statement is for all MDM versions 7.1.02.96 (currently the latest version) and bellow.
Solution
As a workaround, you can substitute the ‘.’ with any other character, both in the XML file and the XML schema.
For example: element name = “Art_nr_”

Symptom
A field (Look-up or multi-value attribute) which contains multiple values (separated by delimiter) is not split properly and can only be mapped to one value instead of multiple-values as desired.
Other terms
655255 2009 lookup
Solution
Define the multi-value delimiter to the proper character.
For example: Please check that the setting in the Import Manager is set as shown in the attached screenshot. By setting the multi-value delimiter to “;” the values will be separated into individual values which you can then map accordingly

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.