Automatic Editing and Error Handling › Automatic Editing Criteria › Edit and Code Tables › Overview

Overview

Existing edit and code tables can be optionally associated with map fields. Automatic editing uses the edit and code tables for a field on mapout and mapin as follows:

• On mapout, the code table (if any) is used to convert stored data to its decoded form for display at the terminal.
• On mapin, the edit and code tables for a field are used as described:
  • The edit table (if any) is used to validate operator input. An edit table can contain either valid or invalid values:
    • If the edit table contains valid values, data input in the map field is valid only if it is listed in the table
    • If the edit table contains invalid values, data input in the map field is valid only if it is not listed in the table
  • The code table (if any) is used to convert data typed in a field to its encoded form for storage. In this way, the code table also validates data unless NOT FOUND is used to pass incorrect data through.

A given map field can have a maximum of one edit table and one code table enabled for it. Edit and code tables cannot be specified for a field that is associated with a group element unless all its elements are defined with usage DISPLAY.

The arrangement of values in a table, the searching algorithm for a table, and the relationship between a table and a map load module that uses the table are determined by the IDD DDDL statement that defines the table.

The definition of tables is discussed in the appendix “Generating Edit and Code Tables".