cancel
Showing results for 
Search instead for 
Did you mean: 

MDM import server automap

0 Kudos

hi all,

i have a problem here:

all creation and update in MDM is an automation process (delta updates) via MDM import server.

there always new values created in lookup table via import server.

However, when a new main record is sent for delta update containing a new lookup value that is not handled by the default mapping, how do we able to automap this new lookup value by itself(without import manager)?

FYI, all process in MDM is done in backend, no middleware, no webservices.

Thanks,

Shanti

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

either you were not sure what ur actual problem was or we are wasting time here !!!

plz let us know how u got this solved in the config file ;D

Edited by: Adrivit on Apr 5, 2011 12:51 PM

Former Member
0 Kudos

Hi Shanti

What do you mean by you got it solved by a config file? What config file is this and how did you get this solved?

Regards

Henning

0 Kudos

hi all,

when you're in import manager, open ->configuration->option->Default MDIS handling

Please take note that it works for import server, not import manager.

Regards,

Shanti

Former Member
0 Kudos

Hello Shanti

Don't forget that you working with master data!

Standard order for data import is:

- update LUT values

- update main table records

But is not fact that help you use automapping

in many cases automapping doesn't work correctly

for example:

- for some attributes

- if you want to map short source value to long destination

- for measurement

- for multivalued destination fields or attributes

Regards

Kanstantsin Chernichenka

0 Kudos

hi, i found the way to handle this already via config file.

Former Member
0 Kudos

not sure , what you mean here !

u need tp have EXISTING lookup values in the LUT , to be able to map them in the IM when importing new records !

so as a first preparatory step (before u actually start mass uploads)

you should have a list of all the possible values that you expect in the lookup to be mapped and saved as ur map.

if anything new comes up you should pull that same sample file u used the previous time for mapping , add the new values , open the old map , map new values and save it. (this will have the old value mapping + new value mapping)

if u dont pull the old file (with old mapped values) - only the new value will be now mapped and saved and u will lose the old mappings

hope this is clear !

thanks

-Adrivit

This process is for only LUT , QLUT only