Required Fields

Some data records in the system contain fields that must be loaded in all cases.  These required fields may or may not be table driven fields (normally table driven fields are required but there are some exceptions).

There are different types of data fields that the system may require

      Parent Fields:  Some records like customers point to parent records or table data.  For instance, each customer must have a valid payment terms code assigned to it.  The Terms code must match one of the terms codes that are present in the Terms Table.  Other examples of parent information include product lines, product groups, shipping methods, divisions, departments.  Parent fields are a type of table driven field.

      Gencode Table driven fields:  StreamV allows you to create generic validation tables for standard and custom fields.  These tables are normally created using the Gencode file.  When Gencode validation tables are present, the information in the associated fields must match the entries in the table (or must conform to the table configuration).

      Other Table Driven fields:  Discussed in the prior section.

      Key field information:  Many data records must contain information that makes them unique.  Examples include the customer and vendor account number fields, the invoice number in the accounts receivable invoice files, and the item number in the catalog and inventory files.  

      Other required fields.  Some records contain information that is not table driven but is required for processing.  Examples would include the reorder quantity in inventory, and the credit line field in the customer file.  Other examples would include fields that must be loaded with Y or N, but that are not table driven, and fields that are loaded or edited using a check box (which resolves to Y or N or 0 or 1).  These fields vary by data file and are usually described in the startup documentation for each area of the system (i.e. AP, CRM, WMS)


Checking for Orphan Data