Translating field values using a table: Overview

XXX I think an this should be checked/tested to make sure it works as described in Fusion. I also think we should explain the differences between the 2 methods (listed under Related topics). How do I decide which method to use?

One use for tables is to translate field values, or change one field value to another. You might want to do this if, for example:

• Certain values are to be abbreviated.

• A field is often extracted incorrectly because of punctuation.

• You need the output data to have a uniform format.

• You want certain field values to be replaced by spaces in the output.

When a field value corresponds to a key value in the specified translation table, the system translates the field value to the corresponding value. If a field value is missing from the translation table or does not have a corresponding value in it in the Translation column, the value is not translated.

Using a translation table for a field is different from specifying an invoice-related validation table. Using a translation table, a field value is converted to a corresponding value if it is found in the table, and no error status is set if it is not found. Using a validation table, the field is given an error status if it is not found in the table. You can specify the same table in each place to achieve both functions.

The system translates fields immediately after extraction, which means that the system applies validation routines (if you specify any) to translated fields. This means that you can use tables to correct common format errors or unrecognizable punctuation marks, or to remove unnecessary digits before validation.

Related topics

Translating field values using an invoice-related table (instructions)

Translating field values using a table from DOCUMENTS system specifications (instructions for document specifications)