Gasboy CFN Series - Manual (Page 19)

MDE-4602 Gasboy CFN Series Card Encoding Manual · November 2006 Page 15
Site ID Field - Fueler ID Format only Card Field Descriptions
Likewise, if the entries are required in the ICR program or the system parameters, they will be
requested regardless of whether they are encoded on the card's Restriction Code.
Site ID Field - Fueler ID Format only
If you use Site Controller II/III, the site ID is a six-digit number configured in the system
parameters of your site. Its purpose is to uniquely identify the site. It is a number assigned by
you and can be changed by using the SYS_PAR configuration program. See the applicable
Site Controller Configuration Manual for additional information.
Fueler ID Field - Fueler ID Format only
The Fueler ID field is used only by Site Controller II or III. If used, the fueler ID is a two-digit
field (0-99). The fueler ID is assigned to a cluster (see the applicable Site Controller
Configuration Manual for additional information on clusters). Once the fueler ID has been
recorded by the site, all ICR and Fuel Point transactions from that cluster will have the fueler
ID inserted into the clerk ID field of the disk journal transaction record. Transactions stored in
the site memory will not record the fueler ID.
Code Number Field - Code Card Format only
If the Code Number field is used for Site Controller I, the length of the field must be 10 digits.
If it is used for Site Controller II or III, it can be 1-19 digits, except that it cannot be the same
as the configured club card account field length (see the applicable Site Controller
Configuration Manual or Manager's Manual). When the code is read, the site searches the code
file or LOOKUP table for the data loaded for that code. If the data has been loaded, it is used
in place of card data for the transaction.
Field Type Field - Fuel Point Card Format only
The Field Type field is used only by Site Controller II/III with a Fuel Point Reader. If used, the
field type is a three-digit field. The field type on the card is compared to the field type in the
Fuel Point vehicle module's Reader Entry field to determine how the data encoded on the card
should be handled. Generally, the field types on the card and the vehicle module are set to
match, to ensure that the card data is being used as intended. If they do not match, the
transaction is aborted. However, if the card field type is zero, the card data will be accepted for
any field type encoded in the vehicle module's Reader Entry field. Conversely, if the vehicle
module's field type is zero, the card data will be accepted for any field type encoded on the
card. If both field types are zero, the transaction will be aborted.