cancel
Showing results for 
Search instead for 
Did you mean: 

Import Manager Mapping Issue

Former Member
0 Kudos

Hi MDM Experts

(Scenario is manual not using XI)

I was trying to import data into Material Repository (Standard Business Content)

manually,

1. I extracted data from ECC system for MATMAS05 and Lookup data to presentation server (Desk Top).

2. Used Import maps from standard Business contents.

3. Loaded Look-up tables.

3. Wnen I perform loading Main Table from Import Manager, I am getting issues w.r.t Field Values, the Maps are trying to map CODE (Soures Value) to Descriptions (Display Fields, Destination Values), for UOM, Material Type, Material Group... but all these values are already imported to the respective look-up tables then why I need to do manually map again. Is it because as I am not using XI am I loosing some convertion.

Regards

Vickey

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Vickey,

This is just to establish Lookup table and Main table relationship. You can perform import of main table data without populating lookup table data, in such case you need to add the values present in the main table lookup field. But everytime you are required to manually add the new entries, in contrast once you populate the lookup table data then everytime you import the data it maps automatically to the lookup values present in the repository which is the case when you are working with Import Server for automatic process.

Regards,

Jitesh Talreja

Former Member
0 Kudos

Thanks for the response,

Consider I have this issue for the field MTART, I get the following error,

"Map 'MTART <IDOC.E1MARAM>' field value(s)"

If I see my Mapping under source value I have FERT (CODE) and in the Destination values I have all the Descriptions Fineshed Material, Raw MAterial...

In order to overcome the error I have to manually map FERT with Fineshed Material.

SO my question is why the mpping not happening at Value level, this is repeating for all other look up fields in tha main table.

Any thoughts....

Former Member
0 Kudos

HI Vickey,

During the first time import ( Import of the lookup table) of say Material Type, you might have imported the value as fineshed materials.Now when you are importing the main table, the value that the source has is FERT. But corresponding to that the look up table holds the value as fineshed material.Now need to tell the system that this FERT corresponds to the Fineshed material via value mapping.

Value mapping is a mandotory step while you are importing values of any look up table.

And it will not happen automatically.

It has to be done manually using either the automap button (If the values are same in this case if both have FERT or fineshed materials) or map button (if values are different as in this case FERT and fineshed)

Hope it helps.

Thanks,

Minaz

Former Member
0 Kudos

Thanks for the reply...

This is fine with look up table rows are few, how about if I have large volume of values like UNSPSC Codes / SG1 Codes having lots of data.

Former Member
0 Kudos

Hi Vickey,

As mentioned earlier this step has to be done manually.

For large data, best practice is to maintain the source and destination values same ie. in your case both sides maintain it as FERT or fineshed (also same data type) so that you can use the automap feature to map all the values in one shot.

Hope it helps.

Thanks,

Minaz

Former Member
0 Kudos

Vickey,

the default repository has both code & text as display fields.

while importing data turn off description(text) as display field & import the data in

Once data loading is done , bring down the repository and turn ON all display fields.

Now if only code is display field, you can use automap in value mapping (IM ) and no-need for manual mapping.

-Sudhir