Available Trips
The Available Trips grid of the Planning Worksheet displays trips that meet your restrictions. The most commonly used columns are defined in the following table. The columns are listed alphabetically.
Bill To |
ID of the Bill To company recorded on the order. Note: If the trip involves consolidated orders, this field shows the Bill To for the first order. |
BookedBy |
User ID of the person who entered the order into the system |
Carrier |
ID of the carrier assigned to the trip |
Cmd Code |
Commodity ID code that identifies the cargo |
Cmd Count |
Number of commodities recorded for the trip. The value recorded for the General Info Table setting, cmd_total, controls how the total is determined. There are two options:
The Cmd Count column displays the total number of freight details recorded on the order. |
Cmd Description |
Name of the commodity on the order |
cmp_id |
ID of the company where the first pickup occurs |
cmp_name |
Name of the company where the first pickup occurs |
ConsigneeCity |
City and state/province location of the last drop |
ConsigneeCompany |
ID of the company where the last drop occurs |
ConsigneeCompanyName |
Name of the company where the last drop occurs |
ConsigneeEarliestDate |
Earliest date/time that the final stop may occur |
ConsigneeId |
ID of the company where the last drop occurs |
ConsigneeLatestDate |
Latest date/time that the final stop may occur |
ConsigneeName |
Name of the company where the last drop occurs |
ConsigneeRegion1-4 |
The destination city’s dispatch regions 1-4, which are established in the System Administration application. Dispatch regions are used to categorize loads for operational purposes. |
ConsigneeState |
State/province where the last event is to occur |
ConsigneeZip |
ZIP Code/postal code where the last event is to occur |
cty_nmstct |
City/state where the first event is to occur |
cty_state |
State where the first event is to occur |
DetStatus |
The system determines detention time by tracking the amount of time a driver spends at a stop before departing. After the arrival time at the stop is actualized manually or through a TotalMail form, the system periodically checks to see whether the departure time has been actualized. The color of the indicator corresponds to the detention status of the trip.
Note: For more information, see: |
Dispatch Status |
Status of the trip. The statuses that display depend on how you have defined your views. The statuses are:
|
Driver1 |
ID of the primary driver assigned to the trip |
Driver1Name |
Name of the primary driver assigned to the trip |
EndDate |
Date and time of the last event on the trip |
FinalCity |
City, state/province where the last event is to occur |
FinalCompany |
ID of the company where the last event is to occur |
FinalCompanyName |
Name of the company where the last event is to occur |
FinalState |
State where the last event is to occur |
FinalZip |
ZIP Code/postal code where the last event is to occur |
InStatus |
The status of the tractor’s next trip. Statuses are:
|
L |
Late indicator, which is color-coded to indicate whether a stop on a trip is late, or in danger of being late. The Late indicator displays in one of these colors:
Note: For more information, see Late symbol. |
Latitude |
The latitude recorded in the profile of the company where the first stop occurs. If no latitude is recorded in the company’s profile, the field value is 0.000000. |
lgh_number |
System-assigned ID number for the trip segment |
LghType1-4 |
Trip segment classifications, often used to categorize trips for pay. Note: Trip classifications are user-defined in the LghType1-4 labels in the Edit User Definable Fields window. |
Longitude |
The longitude recorded in the profile of the company where the first stop occurs. If no longitude is recorded in the company’s profile, the field value is 0.000000. |
Mileage |
Total miles for the entire movement |
mov_number |
Numeric system-assigned ID for the movement |
ord_hdrnumber |
Unique numeric ID assigned to an order by the system |
Order |
Order identification code. Note: Typically, this is a numeric value assigned to the order when it is created. However, in some cases, users will override the system-assigned number with a user-defined alphanumeric code. This is common for master orders because it makes the orders easier to look up. |
OrderBy |
ID of the company that placed the order |
OriginCity |
City and state/province where the first event on the trip segment is to occur |
OriginCompany |
ID of the company where the first event is to occur |
OriginCompanyName |
Name of the company where the first event on the trip segment is to occur |
OriginId |
ID of the company where the first event is to occur |
OriginName |
Name of the company where the first event on the trip segment is to occur |
OriginState |
State/province where the trip begins |
OriginZip |
ZIP Code/postal code where the first event is to occur |
P |
The Priority indicator signals the importance of the load. The color of the indicator is determined by the priority assigned to the trip (e.g., the entry made in the Priority field in the order header). The indicator will display in one of these colors:
Note: For more information, see Priority symbol. |
PickupEarliest |
Earliest acceptable date and time that the first event on the trip segment can occur |
PickupLatest |
Latest acceptable date and time that the first event on the trip segment can occur |
PickupRegion1-4 |
The origin company’s dispatch regions. Dispatch regions are established in the System Administration application and are used to categorize loads for operational purposes. |
RevType1-4 |
The order’s RevType1-4 classification codes. Note: Revenue classifications are user-defined in the RevType1-4 labels, accessed in the Edit User Definable Fields window. |
RevType1-4Name |
The order’s RevType1-4 classifications. Note: Revenue classifications are user-defined in the RevType1-4 labels, accessed in the Edit User Definable Fields window. |
Revenue |
Total charges for a pre-rated order |
StartDate |
Date and time that the first event on the trip segment is scheduled to occur |
Status |
Icons indicate the dispatch status of the trip. The statuses that display depend on how you have defined your views. The statuses are:
Note: For more information, see Status column in the Available Trips grid. |
StopCount |
Total number of stops recorded for the trip segment |
stp_arrivaldate |
Date/time the arrival at the stop was marked as completed |
stp_departure_status |
Indicates whether the resources have completed the event scheduled for the stop location. Options are:
|
stp_description |
Name of the commodity associated with the stop |
stp_event |
Event recorded for the stop |
stp_number |
System-assigned numeric identifier for the stop |
stp_status |
Indicates whether the resources have arrived at the stop location. Options are:
|
Tractor |
ID of the tractor assigned to the trip |
Trailer1 |
ID of the primary trailer assigned to the trip |
Trailer2 |
ID of the secondary trailer assigned to the trip |
TrailerType |
The TrlType1 classification for the trailer that is to be assigned to the order, as specified when the order was created. Note: To help your company track revenue brought in by different types of trailers, the system allows you to classify trailers into four trailer categories. These categories, called Trailer Types, are defined by your company for its own use. They are further subdivided into trailer categories. |
Weight |
Total weight of the cargo |