cancel
Showing results for 
Search instead for 
Did you mean: 

import server - map MATMAS05 - MAKTX (material description)

Former Member
0 Kudos

hi,

I do have a problem with mapping the description field in the MATMAS05 idoc via the import server.

The description is the MAKTX element. this element is part of E1MAKTM segment. This segment is contained in the E1MARAM segment.

The E1MAKTM segment can and does appear moretimes since it appears for more languages. To map these correctly I created a pivot table.

To be able to lookup the pivot table values from within E1MARAM, I joined the E1MARAM id with the id in the pivot table. Next step is doing lookup from within the E1MARAM segment to values within the pivot. The various languages of the MAKTX field can now be mapped to the respective language of the description field in the MDM repository. This all works in the import manager, and the import is run the description is in the repository.

When processing the idocs via the import server. The message "mapping to complex” appears. I guess it is because of the join. Is there an other way to get the description mapped? Even when splitting the process in two runs, and having a separate run to get the description in, I still need a join to update the right material with the right description.

Thanks for any thoughts on this,

Wim

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

in your case mapping is the problem

Possible Solution is :

1.if you are using only one language then map with only one description and avoid unneccasry description mapping with multiple language. which ever you require map only those description language.

2. split mapping in your case you require material number as well.So you need to create mara seprate map with material number and make materail number as unique and remote key. and In match record tab make material number field in maching field. do importing

i hope above possible solution will help you.