{{ images:lookuptables.jpg}} ====== Value Tables ====== LookUps are generally used to convert or look up * customer numbers * sizes * colors * merchandise categories * branches... within a transformation. All [[en:transformation:mappings:funktionen:abfragefunktionen:lookup:start|]] 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. ===== Creating key-value pairs ===== ==== automatically ==== Conversions can be created automatically using the mapping function [[en:transformation:mappings:funktionen:abfragefunktionen:lookup:addlookupkeyvalue|]]. ==== via copy & paste ==== How to quickly add a list of key value pairs to a lookup table is explained in [[en:transformation:lookuptables:loadvalues]]. ==== manually ==== 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. ===== Removing key-value pairs ===== Unused value table entries can be removed with the [[en:prozessdefinition:jobs:jobsteps:allgemein:removelookupentries|]] job step. ===== Global ===== Only one table is required for global remappings. Suitable mapping functions are e.g.: * [[transformation:mappings:funktionen:abfragefunktionen:lookup:lookupglobalvalue|]] * [[transformation:mappings:funktionen:abfragefunktionen:lookup:lookupglobalvaluenoauto|]] * [[transformation:mappings:funktionen:abfragefunktionen:lookup:lookupglobalkey|]] ===== partner-specific ===== For partner-specific [[partnerverwaltung:lokation:lookup:start]]((aka recoding, rekeying, remapping)), 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: * [[transformation:mappings:funktionen:abfragefunktionen:lookup:lookuppartnerlocationvalue|]] * [[transformation:mappings:funktionen:abfragefunktionen:lookup:LookupPartnerLocationAddLookupValue|]] * [[transformation:mappings:funktionen:abfragefunktionen:lookup:LookupPartnerLocationValueDescription|]] * [[transformation:mappings:funktionen:abfragefunktionen:lookup:LookupPartnerLocationAddLookupValue|]] * [[transformation:mappings:funktionen:abfragefunktionen:lookup:LookupPartnerLocationValue|]] * [[transformation:mappings:funktionen:abfragefunktionen:lookup:LookupPartnerLocationValueDescription|]] {{:images:sign_warning.png?nolink|}} Note: See [[en:transformation:mappings:funktionen:abfragefunktionen:lookup:start|]]