Liquid Controls DMS Office - Manual (Page 24)

24
A Product.500 record contains specifications for a product.
The Product.500 records are created by LCLoad, but they
can be edited using DMS Office.
If your LCR-II is calibrated for more than one product, the
Fuel Type Code field must reflect the proper FuelType.500
record. The Description field is often changed to the
precise name of the product.
Code
Enter an alpha-numeric value <= 8 characters.
This is the value from DELLOAD.DAT.
Description
Enter an alpha-numeric value <= 35 characters.
Fuel Type Code
This is the Fuel Type Record with the proper LCR-II
calibration for the product. Enter any integer <= 255.
Unit Price
This field can be left blank. Unit Price is pulled from
DELLOAD.DAT and saved in Dispatch.500
Tax Code
This field can be left at zero. Tax Code is pulled from
DELLOAD.DAT and saved in Dispatch.500.
Product Configuration
PRoDUCT ConFIgURATIon
DMS Office’s Product.500 and FuelType.500 label and
configure products, so DMS Delivery can properly receive
meter readings from the LCR-II.
LCLoad creates a product record for every unique product
code found in DELLOAD.DAT’s records and enters them
into Product.500. FuelType.500 is manually populated
with DMS Office.
PRoDUCT.500
Product.500 and FuelType.500 must be set up after running
LCLoad and before launching DMS Delivery.
LCR-II, Fueltype.500 and calibrations
At start up, DMS Delivery saves all LCR-II calibrations (4
calibrations per meter) that exist in the system. In order
to correctly meter product, DMS Delivery needs to know
which LCR calibration to use. FuelType.500 defines each
calibration, and Product.500 chooses a FuelType.500
record (a calibration) for each product.
If the vehicle has a multi-meter system and the meters
share LCR-II calibrations, DMS Delivery will prompt the
driver to choose a meter.
Product.500 after LCLoad
Product.500 after LCLoad and DMS Office configuration
FuelType.500 after LCLoad and DMS Office
configuration