Supporting extended MICR fields

By default, eight MICR fields that use indexes 1 through 8 are supported. To support any additional extended MICR fields (for example, fields 9 through 15), the database must be configured.

Seven extended MICR fields are in the ITEM table in the database: FIELD_9 through FIELD_15. By default these fields all have VARCHAR data types with a length of one. If left as-is, they default to unsupported, which means the Transaction Server does not save any information in these fields during capture or load processing.

To enable an extended MICR field in the database, change its length to be greater than one. The Transaction Server detects the length and saves information to those fields as it receives it. For example, to add support for extended MICR fields 10, 11, and 14, apply the following SQL statements to the database after it is built. 
ALTER TABLE FTM.ITEM ALTER COLUMN FIELD_10 SET DATA TYPE VARCHAR(32) FOR BIT DATA;
ALTER TABLE FTM.ITEM ALTER COLUMN FIELD_11 SET DATA TYPE VARCHAR(28) FOR BIT DATA;
ALTER TABLE FTM.ITEM ALTER COLUMN FIELD_14 SET DATA TYPE VARCHAR(16) FOR BIT DATA;
REORG TABLE FTM.ITEM;
Notes:
  1. The fields can be any length, but no longer than 255. The fields don’t all need to be the same length. Choose a length that reflects the maximum amount of the data that is expected for each field. Choosing the maximum length of 255 might seem the safest bet, but it causes excessive database storage to be wasted for each item stored. If the Transaction Server receives any information for one of these fields that exceeds the specified length, it truncates the field.
  2. Any MICR field whose length was not modified remains unsupported. This configuration requirement applies to only field 9 through field 15. Do not attempt to modify the lengths of fields 1 through 8.

After the MICR field lengths are altered, the Transaction Server must be restarted for the changes to take effect.