RF control files

The receipts.ini RF control file must be modified to manage the field mapping configurations for UCC/EAN 128 and 2D barcodes. For UCC/EAN128, all supported AIs (Application Identifiers) must be specified into eanai.ini, along with the application database field mappings for the AI data strings. This is not required for 2D barcodes.

For UCC/EAN128 barcodes if you need to support multiple storers with the same RF control files.ini files, the system allows multiple AIs or data identifiers to be mapped to the same Infor SCE WM database field. For example, Storer A can have the AI associated with a Manufacturing Lot Number mapped to Lottable 03, while Storer B can have the AI associated with Unit Weight mapped to Lottable 03. Each storer would have a unique barcode template name in the Owner record.

The application produces a warning message during the setup of the RF control files such as receipts.ini if you map two AIs to the same database field. In the instance where a single UCC/EAN 128 label contains both of the AIs that are mapped to a single database field, the last AI read is updated. No error is produced and the second AI data string overwrites the first AI data string.

2D barcodes can be used further in the receiving process including when it comes time to capture a large quantity of serial numbers with just one scan during the serial capture part of the receiving process. 2D barcodes are able to compact so much data into a small surface that one small 2D barcode symbol can easily contain 10,000 serial numbers (for example).

The application does not support mapping a single AI to multiple database fields.