Remote Keys - customer extension scenario
Have a query , while using remote keys in the customer scenario - if we map the customer number field to the remote key then the customer number is considered as the key & in the edit keys option shows for example cust 123 in mdm mapped to cust 123 in R/3.
Now if the R/3 customer 123 has been extended across company codes 100 & 101 in R/3 for example - while importing data we use the (customer number + company code) as a combination to import data , the customer gets created in MDM as cust 123 company code 100 , cust 123 company code 101.
However, the issue is that the remote key is enabled only for one customer (the first record that is loaded) and as the remote key has to be unique it cannot be mapped again for the second line item and therefore that item remains unmapped.
What is the best way to handle this scenario - so that the line items are created for each company code at the same time the remote key should also be maintianed for each of these records .
All suggestions wil be rewarded !!
Michael Theis replied
yes, according to your scenario the modelling using a multi-valued look up is the best way to do.
Regarding the import error, well, it's hard to say what could be wrong here. Do you have more information about the error? Did you have a look at the Import Logs? Maybe - as you have changed the repository to add the company code data - you should run a verify check/repair with the repository and of course load the repository with the update indices option.