Daily Shipment Feed
RAILTRAC® has the ability to process keypunched shipment entries as well as process shipment records inserted into a database table called RT_TRIP_IMPORT. This insert routine is programmed by the client by extracting the records or bill of lading system.
RAILTRAC®
produces an exception file for shipment records that do not pass validation
criteria imposed by the import routine. An alarm is then visible on the EDIT
Shipment function which allows transportation staff to display the bad record,
make any changes necessary to process it, and update the database.
The shipment record loaded to RT_TRIP_IMPORT should contain at a minimum:
| Data Entity |
Max
Length
|
Comment |
| Railcar Init/No. |
10
|
Car Initial space padded to left (4 max). Car Number zero padded left (6 max). |
| Shipment Date |
8
|
YY/MM/DD (Year 2000) displays "00" |
| Route Code |
20
|
RAILTRAC can derive route from origin/consignee combinations. If the RAILTRAC® route code is not deliverable, substitute origin ID or city name. |
| Consignee No |
14
|
This is a ship-to specific customer number. Lease tracks, terminals, other origins need a consignee number also. |
| Product Shipped |
10
|
Product code of what was shipped |
| Product Quantity |
6
|
Quantity shipped in railcar |
| Quantity UofM |
3
|
LBS, TON, GAL, etc |
| Other |
NA
|
Other fields can be passed to RAILTRAC® and stored: Order No, Customer PO, BOL No, Third Party Shipper, Product Lot No, Industry Use Code, etc |
Copyright
© Bourque Data Systems, Inc. All rights reserved.
