MDM 321 – SAP Netweaver Master Data Management

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
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
The MDIS does not import the source file even though it has been running a long time and the Import Manager crashes with an “Out of Memory” error message using the same file.
Other terms
cpu excess
Reason and Prerequisites
The issue occurs because of the incorrect selection of the source table.
For exmaple: The “Customer” map is using “Customer_Account” as the selected source table even though “Customer_Account” is not a repeatable node. By doing this, the process of retrieving flat records becomes enormously complex and requires tons of memory.
Solution
The solution is to select a repeatable node in the source file as the selected source table. In the above example it is “Customer_Account.Customer”

Symptom
When importing a delimited text file with delimiter semicolon (”;”) the Import Manager throws the next error message at the “connect to source” stage:
“Number of field values does not match the field columns. Line # [Pos #].”
Reason and Prerequisites
* The following reason and solution are valid only if apostrophe (’) or inverted commas (”) are been used inside the import source file.
Apostrophe (’) and inverted commas (”) are special characters for the
Import Manager and you experience correct behavior of Import Manager.
Those characters are special in a matter that they need to be imported in pairs.
The Import Manager will not allow importing word or phrase that start with apostrophe (’) and finished with inverted commas (”) and vice versa.
Solution
Please make sure to surround the word with [...]

Symptom
Import Manager gives error “Can not generate XML Schema”
Other terms
XSD,
Reason and Prerequisites
The problem is that the XML file has a directive for loading DTD.
For example:
<!DOCTYPE BMECAT SYSTEM “bmecat_new_catalog_1_2.dtd”>
MDM does not support DTDs.
Solution
Remove the DTD line and make sure
there is only one root element in the XML file, then the file loads
properly.
The better approach is to create the xsd an upload to the
repository, then use XML Schema instead.