The process routine takes the loaded EFI data and updates the data in RTA—just as if the fuel tickets had been entered into the RTA system manually. The difference is that instead of taking a few hours, hundreds of transactions can be processed in only a few minutes! As long as there are no problems with the transactions processed, the vehicle meter reading, fuel usage, and fuel cost will be updated.
...
Once the EFI transactions are processed, be sure to review them for any process errors.
You can do this by selecting ‘Filter by: Last Known Upload’ and filtering for the date range you just completed. Then look at the column ‘Process Error’. If a transaction has an error you may need to manually load the fuel entry or adjust a vehicles odometer.
Read the chart below to view the errors
...
Error Message
...
What It Means
...
What To do
...
METER_EXCEEDS_ALLOWABLE_MILEAGE_LIMITS
...
The fuel entry was added but the odometer on the transaction is higher than what the system allows and was not updated
...
Double check the actual odometer of the vehicle and manually update it.
##Find More Error Messages##
##ADD SCREENSHOTS##
Read the chart below to view the errors
Message | What it means | What to do |
|---|---|---|
Vehicle Not Found | The Vehicle Number or Card Number coming from the Fuel System Does not match an RTA Asset Number or Cross Reference Number | Three General Fixes:
|
Inconsistent Fuel Type | The Fuel Transaction Fuel Type Does not match the Primary Fuel Type set in the Asset Record | If you did not initially set the Fuel Type in the Asset File then set it. See Setting the Fuel Type from the Fluids Panel in the Asset File |
Fuel quantity greater than tank capacity | The Fuel Transaction has a greater fuel quantity then the Vehicle can physically hold (Tank Size) | If the Asset did not have a tank capacity setup initially you will want to do this first. See Setting the Tank Capacity from the Fluids Panel in the Asset File OR There may be truly be an issue with the Fuel Transaction |
Meter exceeds allowable mileage limit | The Miles/Hours/Kilometers traveled for the Fuel Transaction Exceeds the “Maximum” Factor (Typically set behind the scenes to 3X) based on the Expected Average MPG Set in the Asset File | First if the Asset was not set with a suggested Average MPG then you will want to make sure you have a good number in each Asset Record. Setting the Average MPG from the Fluids Panel in the Asset File This also may reflect an odometer issue in the Fuel Transaction itself or an Odometer issue in the Asset File |
Mileage high for average mileage | The Miles/Hours/Kilometers traveled for the Fuel Transaction Exceeds the “High” Mileage Factor (Typically set behind the scenes to 1.5X) based on the Expected Average MPG Set in the Asset File | First if the Asset was not set with a suggested Average MPG then you will want to make sure you have a good number in each Asset Record. Setting the Average MPG from the Fluids Panel in the Asset File This also may reflect an odometer issue in the Fuel Transaction itself |
Mileage Low for average mileage | The Miles/Hours/Kilometers Odometer Reading coming in from the Fuel Transaction is less then the current Fuel Meter Reading in the Asset File. | This is usually indicative of a Fuel File loaded out of sequence. For Example Loading Wednesday Fuel file before loading Monday’s of the same week. The Wednesday readings have already updated. Thus pulling Mondays fuel at lower readings would throw these exceptions. OR again is could be an Odometer issue either in the Asset File or the Fuel Transaction File |