Many data records in StreamV contain table driven fields. Table driven means that the values in a field are limited to a specific list of values. Table Driven fields are usually loaded or validated using Prompt Lists or Validation tables.
The operator can select from a list of the values in each table by clicking on the prompt button (…) that is displayed next to the field, pressing the Expand/Prompt Key (F3 or F4) when the cursor is positioned in the field, or clicking on the pull down arrow next to the field if the field is presented as a combo box.
The list of valid values for table driven fields can come from the following places;
1. Defined in the application software. This source for values is used when the field controls system behavior within a specific part of the application. Example -Payment type: Check or Wire. You cannot change this.
2. Defined in the application data dictionary. This source for values is used when the field is limited to specific values that are used across the whole application. Example – Order Status: Sales Order, Quote, RTV, Loaner. You cannot change this.
3. Defined in a “parent” table: This source for values is used for site specific data that is “your” data. Example: The Product Line field in the catalog is restricted to values in the Product Line table. You may change this data (see note 1).
4. Defined in a “Gencode” table: This source for values is used for site specific data that is data you want to limit on your system. Most fields in the system can have a site specific “Gencode” table setup for them to control what users may enter in a field. You may change this data (see note 1).
Since these values are used when creating other data records you must have these table values setup prior to creating the records that point to them.
Note 1: If you delete a value from a parent table or Gencode table after that value has been used in another record, for example you delete a product line after you have setup a catalog record pointing to it, you will cause errors to occur during processing. This is also true in reverse. If you setup a Gencode table after creating records that use it you can