Skip to Content
avatar image
Former Member

Remote Keys - customer extension scenario

Hi ,

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 !!



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Oct 08, 2007 at 11:13 AM

    Hi Anita,

    a single record in MDM may have several key mappings, even for the same system. In your case, you shouldn't run into the unique issue, as the combination of customer number and account group you're use as key, should be unique, too?! SO the question is, how do you import your data. It is correct that during the data import only ONE singe record can be written into the key mapping. So in your case, you should check if you can load the customers multiple times? An alternative would be to exclude the account group from the key mapping and to store it within the repository. Possibilities could be in this case a flat look-up (multi-valued) or a qualified lookup if you have account group specific data for your customer.

    BR Michael

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Anita,

      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.

      BR Michael