LookUps are generally used to convert or look up

• customer numbers
• sizes
• colors
• merchandise categories
• branches…

within a transformation. All Lookup functions are documented.

In the interaction of ValueProvider and LookupTableTypes, global or partner related remappings are possible.\. For 1-to-1 lookups, both Key→Value and Value→Key recoding is possible.

Conversions can be created automatically using the mapping function AddLookupKeyValue.

How to quickly add a list of key value pairs to a lookup table is explained in Load key-value pairs from clipboard.

Usually lookuptables are set up in a way that new lookup values are entered automatically as soon as they are requested with a lookup function in the mapping. A task is also created, i.e. a mapping rule may have been violated if the lookup value is expected to be mandatory. Then the missing lookup value can be selected from the value provider in the corresponding value table and assigned or a new one can be created.

Unused value table entries can be removed with the RemoveLookupEntries job step.

Only one table is required for global remappings. Suitable mapping functions are e.g.:

• LookupGlobalValue
• LookupGlobalValueNoAuto
• LookupGlobalKey

For partner-specific Lookups¹⁾, with the appropriate settings on the value table type and using the following functions, the partner-specific tables are automatically created, if they do not already exist, filled with the foreign keys to then be able to be provided with the desired lookup values.

Mapping functions for partner specific remappings are:

• LookupPartnerLocationValue
• LookupPartnerLocationAddLookupValue
• LookupPartnerLocationValueDescription
• LookupPartnerLocationAddLookupValue
• LookupPartnerLocationValue
• LookupPartnerLocationValueDescription

Note: See Lookup functions