Import values when destination field looks into a Main lookup

[susanne_lindfeldt]

Hi experts,

We have modelled partner functions in mdm 7.1 as a tuple within the purch org tuple. The tuple consists of 2 Fields "partner function type" and "partner function account number". The account number which is equal to a vendor number is looking into the Main table Vendors to check The vendor Number. My question is now, when we want to import a file where we have all The values needed - vendor number, purchasing org, partner function type and partner function account number - how should we map it in import manager? When mapping source account number to destination account number it requires value mapping but value mapping is not possible...

Any help...

[Former Member · Accepted solution]

Hi Susanne,

Try following steps.

1. Enable the key mapping of Vendor Main table in Console.

2. Load Repository with update indices and In Data Manager--> Load the Vendor Number in Key mapping of all vendor records.

3. Now in Import Manager Value mapping will occur automatically.

Please have a look in Import Manager Reference Guide, How to import Lookup Main Records.

BR,

Alok Sharma

[Former Member]

Hi Susanne,

Greetings to you!

Question 1: Does your import file have the ECC Vendor number in it - or is the ECC Vendor number generated after you do the import?

Question 2: Are you storing the legacy vendor number in the key mappings?

During an initial conversion where you don't have the ECC vendor number, it may be necessary to handle the partner functions in a separate pass, after the all of the ECC Vendor numbers have been generated.

[susanne_lindfeldt]

Thanks a million! It was the key mapping we had missed here. Now it works fine!

[michael_theis]

Hi Susanne,

you cannot import the data at once. If you import into a lookup main field, you have to ensure that the records that you want to use as lookup main already exist in the repository:

So if you try to import a single source file with

- Record A having no lookup main

- Record B having a lookup main to A

=> this won't work.

Options are either to split the file into two files so that Record A is imported first, then Record B; or to import the single file twice: the first run sets up the main table, the second run adds the lookup main references.

Best regards

Michael