Lookup tables
What a lookup table is, what it's used for in your integration, and how to request a change.
A lookup table maps a value in one of your systems to the equivalent value in another. It is how a transformation converts a code or name your source system uses into the code or name your destination system expects.
What a lookup table is used for
Common examples include mapping a carrier name to the carrier code your ERP expects, mapping a payment method to a payment code, or mapping a tax code from one system's format to another's. Rather than hard-coding these conversions, HC stores them as lookup tables so they can be reviewed and updated as your business adds new carriers, payment methods or tax codes.
You can see your lookup tables listed in the Control Panel alongside your other integration configuration, such as systems, keys and dedicated queues.
Adding or changing an entry
To add a new entry, for example a new carrier or payment method, or to correct an existing one, raise a request with HC in the same way as any other mapping change. Include:
Which lookup table is affected.
The value as it appears in the source system.
The value it should map to in the destination system.
See Requesting a mapping change for how to raise this with HC.
If a value is missing
An event can fail if it contains a value with no matching entry in the relevant lookup table, for example a new carrier that has not yet been added. If you see this kind of failure, check whether the value is a new one your business has started using, and raise it with HC to have it added. See I received an alert — what now? for general guidance on diagnosing a failed event.