Fuel Data Load (Automated Fuel Tickets) |
The Fuel Data Load tab enables you to define and process an upload from an automated fuel system and review the number of transactions accepted and rejected during the processing.
You can arrange for the automated fuel dispensing system to transmit as many files as is convenient, from any number of locations. The fuel dispensing system is not polled. You must arrange for the system to transmit and store the files on the hard disk of a computer.
The amount and cost of fuel represented by each fuel transaction are charged to the equipment unit identified on the transaction. See Actions the system takes when it processes uploads from an automated fuel system.
The field in the top section of this tab defines the data that displays.
Run ID
The sequential identification number assigned to each fuel transaction upload. The run description displays in the field to the right of the ID.
Data in the fields in the bottom section of the tab define the upload of fuel data and display the results of the upload process. Unless otherwise indicated, these fields are required.
Run description
Enter a unique description of the run, or file upload. Using the date or other identifying information may be beneficial for identification purposes.
Use hyphens (-) and not slashes (/ or \) to separate the date elements. For example, MM-DD-YYYY.
User ID uploading
The User ID uploading field defaults to the currently logged in user.
Enter or select a different user ID, if needed. The user name displays in the field to the right of the ID.
Fuel file name and path (Required)
Enter the fuel file's name and file path. This name is loaded into the database. This field allows up to 256 characters.
You must include the drive location (ex. "C:\") and directory path (ex. "...\<deployment>\<folder>\<file name>" if the file is not stored on the current drive and directory. The file must also be accesible to the Application Server. The file name CANNOT have the same name as another file used by the Application. To avoid naming conflicts, it is recommended to add an extension of "AFD" (Automated Fuel Dispensing) to all files to be used by this screen. An example of this naming convention, using a location and date for the file name, would be "<location name>MMDD.AFD".
Note: If the file upload specified an Account ID, this ID will be used in processing. If an Account ID is not specified, the equipment's assigned Account ID is used.
Upload start date and time
This display-only field contains the date and time the upload began.
Processing started
This display-only checkbox will be checked if processing has begun for this Run ID.
Processing completed
This display-only checkbox will be checked if processing has completed for this Run ID.
Accepted tickets
This display-only field shows the number of transactions that were accepted during the Run ID processing, including any that may have generated an error.
Rejected tickets
This display-only field shows the number of transactions that were rejected during the Run ID processing.
Special action (Update or Edit mode only)
Select an action to resolve any processing errors. This field is only available to users when in Update mode.
Available actions include:
NONE: No action will be taken.
CONTINUE PROCESSING: The System will continue processing transactions. This option may be selected if, for some reason, the initial processing of all transactions was not completed - indicated by the Processing completed checkbox not containing a check.
REPROCESS REJECTED: The System will reprocess rejected transactions that have been corrected by the user.
REVERSE PROCESSED: The System will reverse previously entered values. Once a Run ID has been reversed, it no longer can be updated or edited. Transactions must be reprocessed under a new Run ID.
Note: When an automated fuel ticket is reversed, the unit price from the equipment ID's most recent fuel ticket is used.