Import of Multilingual hiarchy

Question

Hello,
I am facing the problem to import a two language hierarchy into a MDM hierarchy table. I used the Import Manager and a flat excel file with two columns. One for english one for german.  Each field holds three values seperated by semicolons. So I want to have a hierarchy with three levels.
Splitdelimiter in my Import map is ";" and I split each column into a hierarchy and map it to my destination hierarchy table. Here are two fields to map to Name[eng] and Name[ger].
After performing the import the hierarchy looks exactly as wanted in english, but there are no german values. These values didn't make it so only the green english values are displayed.
What is the correct was to import this simple demand?
Answers will be rewarded
Nicolas

Answer 1

Hello,
I have the same problem. I'm working with MDM Version 5.5 SP5 ( 5.5.42.90)
I need to import a second language into the Hierarchy
-> I’m following the description (below) of the SAP Library
-> the Import Manager shows on the import status tab that it wants to do the import of the second language
-> no error appears for the import, everything seams normal, second language values are automatically value mapped
=> but it just doesn’t import the second language.
In Import Manager the following configuration is done:
Set the property for "Expand Multilingual Text Field" to As Multiple Fields
In despair I tried different things :
Import of both languages together , separated ;
Matched over Hierarchy name alone, remote alone, the two together, also with the two languages.
I even tried the import with changed hierarchy display field to “Hierarchy code” and not “Hierarchy name”.
I did the import with system language and login language in the second language.
No way to get the second language into the table, just manually in Data Manager.
Has anyone experience with multilingual import into the Hierarchy?
Thank you very much for helping me.
Best regards
Su
SAPLibrary: Import Multilingual Data Into Lookup Tables
If necessary, CREATE the hierarchy from the current language layer Name field that contains the hierarchy information (for example, using the Split Hierarchy command).
Note: Hierarchy: Only one language layer Name field contains the hierarchy information.
Map the current language layer Name field
Map/Add the entire set of hierarchy values
Note : Hierarchy: Now supports mapping of internal nodes
Map the other language layer Name field(s)
No value mapping necessary
Note: Hierarchy: Map Value button previously could not be unchecked for hierarchy field and so Name field had to be value mapped.
Map the [Remote Key] field
Record match using:
1)  The Name field
2)  The [Remote Key] field (if the Name field was not value mapped)
3)  The combination of both
Note: [Remote Key] previously not available as a record matching field, and so Name field had to be used for record matching.
To UPDATE one or more language layers of existing records
Map the other language layer Name field(s).
No value mapping necessary
Note: Hierarchy: Map Value button previously could not be unchecked for hierarchy field and so Name field had to be value mapped
Map the [Remote Key] field.
Note: [Remote Key] previously did not exist, and so current language layer Name field had to be mapped.
Record match using the [Remote Key] field and set the import action to Update (All Mapped Fields)
Note: [Remote Key] previously not available as a record matching field, and so Name field had to be used for record matching. Hierarchy: Can use [Remote Key] field for record matching because Map Value button can now be unchecked for hierarchy field and so Name field no longer needs to be value mapped.