5. Working with Inbound 214 status updates
An Inbound 214 status update file tells you an order’s current status, as completed by the
carrier. You can use the Inbound214Validation General Info Table setting to actualize each
stop and update the date/time and reason code automatically. The reason code indicates
whether the stop was on time, early, or late. Alternatively, you can review the 214 data in the
Process Inbound 214s window and manually update a trip's status based on that data.
To process 214 status updates, the following must be true:

The LTSL EDI 214 service must be running for the 214 file to process through the Inbound
214 folder that was set up during the service installation process.
The default directory is C:\Program Files\TMW Systems, Inc\LTSL EDI Service\Import\214

In each carrier profile, the 214 option must be selected in the EDI section.

Each 214 status code is set up in one of these General Info Table settings:

Inbound214Appointment

Inbound214Arrival

Inbound214CheckCalls

Inbound214Departure

Inbound214MiscDates
The following sections explain how 214 status updates are received, and how they are used to
update stops in the Dispatch application.
What is a 214? ........................................................................................................................................................... 5.2
Understanding Inbound 214 status update files ................................................................................................. 5.2
Processing Inbound 214 status updates ................................................................................................................ 5.3
Setting up the system to generate Inbound 214 files automatically ................................................................. 5.7
Editing labels for the Load Tender Outbound process ............................................................................... 5.7
Recording options for the Inbound214Reason label ............................................................................. 5.7
Recording options for the Inbound214Status label ............................................................................... 5.7
Actualizing each stop automatically .............................................................................................................. 5.8
Inbound214Validation .......................................................................................................................... 5.8
Identifying the EDI appointment codes for Inbound 214 files ................................................................... 5.9
Inbound214Appointment ...................................................................................................................... 5.9
Specifying the arrival update codes that actualize events for Inbound 214 files ................................... 5.10
Inbound214Arrival ............................................................................................................................. 5.10
Specifying the status codes used for processing location reports ............................................................ 5.11
Inbound214CheckCalls ....................................................................................................................... 5.11
Specifying the departure update codes that actualize departure events for Inbound 214 files ........... 5.12
Inbound214Departure......................................................................................................................... 5.12
Inbound214MiscDates ................................................................................................................................... 5.13
Inbound214MiscDates ........................................................................................................................ 5.13
Processing Outbound 214 files ............................................................................................................................. 5.13
Copyright © 2017 TMW Systems, Inc.
A Business Confidential Document.
5.1
Revised: 7/2017
Working with Inbound 214 status update files
What is a 214?
The 214 Transportation Carrier Shipment Status Message is an EDI transaction sent to the
shipper to indicate current shipment status. Each record in a 214 file includes this information:

Carrier code

SCAC code

Reference number

Status code

Status date/time

Reason code

Location

Time zone
Understanding Inbound 214 status update files
The carrier sends a 990 Load Tender Acknowledgement upon accepting a load and a
214 Acknowledgement status upon starting a load. The 214 file is processed into the LTSL EDI
214 folder, and is available to be accepted or declined as a stop update in TMWSuite.
The Process Inbound 214’s window (shown here with sample data) allows you to review the
events listed on a 214, and the current status and reason code associated with each event.
A. The header allows you to specify the criteria that will restrict which 214s can be reviewed.
B. The 214 Data grid displays the stops and appointment information contained in the 214 file.
C. The Stop Detail grid displays stops and events data as they would appear in the
Trip Folder's Stop Detail grid.
Brokerage EDI
TMWSuite
5.2
Revised: 7/2017
Working with Inbound 214 status update files
Processing Inbound 214 status updates
To process 214 data, complete the following steps:
1. In Dispatch's Trip Folder or Planning Worksheet, select Dispatch > Inbound 214 Updates.
The Process Inbound 214’s window appears.
2. In the header section, make entries in these fields:
Billto Id
Select the company ID of the Bill-To company for which you want to
process 214 data.
From / To
Enter the start and end dates of the stops that you want to process.
Status
Select the status for the 214 stops that you want to process.
Note: The status of each stop is stored in the TMWSuite database.
Events that have been previously processed are accessible through this
window for review.
Note: To retrieve a group of 214s based on different criteria, click New Search.
3. Click Retrieve to view the available 214s.
Brokerage EDI
TMWSuite
5.3
Revised: 7/2017
Working with Inbound 214 status update files
4. Review the data in the 214 Data grid. All data is from the Inbound 214 file.
Status
Select the status for the 214 event. The options are:

Open
The data has not been accepted or rejected. This is the initial status
for 214 events.
Note: You may change data in the EDI Reasoncode and Status Dt
fields when the 214 stop is in the Open status.

Accepted
Actualize the event and update the date/time in the database. The
214 event is removed from the grid.

Accepted W/O Cmp
Update the stop reason code and date/time. The event is not
actualized. You must manually actualize the stop in the Trip
Folder. The 214 event is marked as accepted and removed from the
grid.

Rejected
Decline any updates made to the database.
Ord Num
Unique identifier assigned to the order.
Ord Status
Current dispatch status of the stop. Status levels include:
Brokerage EDI
TMWSuite

Planned
The carrier has been assigned.

Dispatched
The assignment has been communicated to the carrier.

Started
The trip is in progress.

Completed
The carrier has reached the stop.
5.4
Revised: 7/2017
Working with Inbound 214 status update files
Booked By
Identifies the user who created the order.
Carr Scac
The carrier’s unique four-digit SCAC code.
EDI Code
The event mapped to the 214 status code in the X12 mapping data.
Note: The event codes are identified in the Inbound214Status label in
the System Administration label file.
EDI Reasoncode
The late reason code mapped to the 214 reason code in the X12
mapping data.
Note: Late reason codes are identified in the Inbound214Reason label
in the System Administration label file.
Status Dt
The date/time the event occurred.
Evt
Event type that identifies the primary activity that occurred at the
stop.
Cmp ID
ID of the company at the stop.
Cmp Name
Name of the company at the stop location.
City
Name of the city for the stop location.
State
State abbreviation for the stop location.
Stat
Status of the arrival stop event: Estimated (E) or Actual (A).
Arrival Dt
Date and time the carrier is scheduled to arrive at the stop.
Stat
Status of the departure stop event: Estimated (E) or Actual (A).
Depart Dt
Date and time the carrier is scheduled to leave the stop.
Status City
Name of the city stop location for which the 214 status was recorded.
Note: The Status City, Status State, Stop Latitude, and Stop
Longitude also appear in the Check Calls window in Dispatch. When
viewed in the Check Calls window, the asset's position appears as
city/state and latitude/longitude. For more information, refer to the
"Recording/reviewing check calls" chapter in the General Dispatch
guide.
Status State
State abbreviation for the stop location for which the 214 status was
recorded.
Stop Latitude
The latitude recorded for the Status City/Status State.
Brokerage EDI
TMWSuite
5.5
Revised: 7/2017
Working with Inbound 214 status update files
Stop Longitude
The longitude recorded for the Status City/Status State.
Ref Type
Type of reference number recorded for the stop.
Ref Number
Reference number recorded for the stop.
Rejection Error
Reason
If Status is Rejected, enter the reason the 214 was rejected.
EDI Order No
The TMWSuite order number.
5. Review the data in the Stop Detail grid of the Process Inbound 214's window.
When you select a row in the 214 Data grid, the corresponding row is highlighted in the
Stop Detail grid.
Section of the Stop Detail grid
Notes:
1. This section of the window is read-only.
2. The columns contain the data that appears in the Trip Folder's Stop Detail grid. Refer to
the Column descriptions for the Freight Detail and Stop Detail grids section in the
“Understanding the Layout of the Trip Folder” chapter in the Trip Folder guide.
6. After you select the status for each 214 stop, click Process to update the 214 data in the
window and TMWSuite database.
The 214 files marked with the Accepted status are actualized and the date/times are updated.
Note: If the arrival status is not actualized before the departure status, the following error
appears:
Brokerage EDI
TMWSuite
5.6
Revised: 7/2017
Working with Inbound 214 status update files
Setting up the system to generate Inbound 214 files
automatically
You can set up the system to automatically actualize each stop and to update the date/time and
reason codes.
In the label file in System Administration, you must create codes that identify the following:

Why an arrival or departure for a stop was late

Type of stops on an Inbound 214
Editing labels for the Load Tender Outbound process
The TMWSuite label file allows you to customize the system for your company. The labels listed
below are used with the 214 Load Tender Outbound process.
Note: All options for the Inbound214Reason and Inbound214Status labels are user-defined.
Recording options for the Inbound214Reason label
In Inbound 214 files, the Inbound214Reason label provides the EDI reason codes used to
identify why the arrival or departure for a stop was late.
The Abbr text for each label option can be used in String1 of these General Info Table settings:

Inbound214Appointment

Inbound214Arrival

Inbound214Departure
The Description text for each option appears in the EDI Code drop-down list in the Process
Inbound 214's window in Dispatch.
Recording options for the Inbound214Status label
The Inbound214Status label provides the EDI status codes used to identify the type of stops in
Inbound 214 files.
The Description text for each label option appears in the EDI Reasoncode drop-down list in the
Process Inbound 214's window in Dispatch.
Brokerage EDI
TMWSuite
5.7
Revised: 7/2017
Working with Inbound 214 status update files
Actualizing each stop automatically
You can use the Inbound214Validation General Info Table setting to actualize each stop
and update the date/time and reason code automatically. The reason code indicates whether
the stop was on time, early, or late.
Inbound214Validation
Applies to
TMWSuite: 2011.10_08.0427, TMW Operations
Description
This setting determines whether the system will actualize each stop and update
the date/time and reason code in a 214 automatically.
String1

No (default)
Stops are not actualized and updated automatically.

Yes
Actualize each stop and update the date/time and status for each.
Note: The system performs the following validation checks. If any one of the
checks is true for the Inbound 214, its status will be Rejected.
Brokerage EDI
TMWSuite

Pickup date/time or delivery date/time is blank.

Order status is not Dispatched, Started, or Completed.

Status for the current leg is not Dispatched, Started, or Completed.

Pickup or delivery date/time is after the date/time the 214 was received.

Pickup or delivery date/time is for a future date.

A 990 Counter or 990 Accept has not been received.

Carrier is different than the carrier assigned to the order.

Stops for previous legs have not been actualized.

Arrival at the current stop has not been actualized.

Arrival 214 was received before the previous stop's Departure 214.

Departure 214 for the stop was received before the Arrival 214.

Departure status date/time is earlier than the Arrival status date/time.

A 214 has already been received for the pickup.

A 214 has already been received for the delivery.

Delivery date/time is on or before the pickup date/time.

Delivery 214 was received before the Pickup 214.

The 214 AD (delivery appointment) was received after a delivery 214.

The 214 AD (delivery appointment) is on or before the 214 pickup
date/time.

Date/time is invalid.
5.8
Revised: 7/2017
Working with Inbound 214 status update files
Inbound214Validation
String2

Blank, that is, no entry (default)
No custom validation is applied.

User-defined entry
Enter the name of the customized validation stored procedure that applies
your company's business rules. You must have String1 set to Yes to use a
customized stored procedure.
Note: For information about obtaining a customized stored procedure,
contact your TMW EDI Support representative.
Identifying the EDI appointment codes for Inbound 214 files
Use the Inbound214Appointment General Info Table setting to identify the EDI appointment
codes used to update the earliest and latest dates/times for appointments on Inbound 214s. It
also identifies the Reason Late code associated with each appointment code.
When the appointment code on a 214 matches the appointment code listed in String1 of the
setting, the date/time on the appointment will be updated automatically when the 214 is
accepted.
Inbound214Appointment
Applies to
TMWSuite: 2008 and later, TMW Operations
Description
In the Process Inbound 214s window, you can review the events listed on a 214
before processing it. Processing a 214 updates a trip's status with the data it
contains. Use this setting to identify the event codes that will result in an
appointment's earliest and latest dates/times being updated when a 214 is
processed.
String1

Setting is blank by default
The appointment dates/times are not updated when the 214 is processed.

User-specified list of appointment status codes
Enter the codes that will update an appointment's earliest and latest
dates/times. Your entry must exactly match the Abbr column value of the
Inbound214Status label options you want to use. You must enter a comma
before and after each code. For example, suppose the label contains these
options:

Pickup Appt, with an Abbr value of AA

Delivery Appt, with an Abbr value of AB
To update the appointment dates/times, you would enter ,AA,AB,
Brokerage EDI
TMWSuite
5.9
Revised: 7/2017
Working with Inbound 214 status update files
Specifying the arrival update codes that
actualize events for Inbound 214 files
Use the Inbound214Arrival General Info Table setting to identify the arrival update codes
that are used to actualize arrival events on Inbound 214 files.
When the event code on the 214 matches the event code listed in String1 of the setting, the
arrival will be actualized when the 214 is accepted.
Inbound214Arrival
Applies to
TMWSuite: 2008 and later, TMW Operations
Description
In the Process Inbound 214s window, you can review the events listed on a 214
before processing it. Processing a 214 updates a trip's status with the data it
contains. Use this setting to identify the event codes that will result in the arrival
at a stop being actualized when a 214 is processed.
String1

Setting is blank by default
The arrival stop is not actualized when the 214 is processed.

User-specified list of arrival status codes
Enter the codes that will actualize the arrival at a stop. Your entry must
exactly match the Abbr column value of the Inbound214Status label options
you want to use. You must enter a comma before and after each code. For
example, suppose the label contains these options:

Arrival at Pickup, with an Abbr value of X3

Arrival at Deliver, with an Abbr value of X1
To actualize the stop on the order, you would enter ,X3,X1,
Brokerage EDI
TMWSuite
5.10
Revised: 7/2017
Working with Inbound 214 status update files
Specifying the status codes used for processing location reports
Use the Inbound214CheckCalls General Info Table setting to specify the EDI status codes
used for Inbound 214 processing of location reports.
Inbound214CheckCalls
Applies to
TMWSuite: 2008 and later, TMW Operations
Description
In the Process Inbound 214s window, you can review the events listed on a 214
before processing it. Processing a 214 updates a trip's status with the data it
contains. Use this setting to identify the status codes that will result in a trip's
location reports being updated when a 214 is processed.
String1

Setting is blank by default
The location reports are not updated when the 214 is processed.

User-specified list of EDI status codes
Enter the codes that will update a trip's location reports. Your entry must
exactly match the Abbr column value of the Inbound214Status label options
you want to use. You must enter a comma before and after each code. For
example, suppose the label contains these options:

Enroute Location, with an Abbr value of X6

Arrived At Pickup, with an Abbr value of X3
To update the location reports, you would enter ,X6,X3,
Brokerage EDI
TMWSuite
5.11
Revised: 7/2017
Working with Inbound 214 status update files
Specifying the departure update codes that
actualize departure events for Inbound 214 files
Use the Inbound214Departure General Info Table setting to specify the departure update
codes that are used to actualize departure events on Inbound 214 files.
When the event code on the 214 matches the event code listed in the setting, the departure will
be actualized when the 214 is accepted.
Inbound214Departure
Applies to
TMWSuite: 2008 and later, TMW Operations
Description
In the Process Inbound 214s window, you can review the events listed on a 214
before processing it. Processing a 214 updates a trip's status with the data it
contains. Use this setting to identify the event codes that will result in the
departure at a stop being actualized when a 214 is processed.
String1

Setting is blank by default
The departure stop is not actualized when the 214 is processed.

User-specified list of departure status codes
Enter the codes that will actualize the departure from a stop. Your entry must
exactly match the Abbr column value of the Inbound214Status label options
you want to use. You must enter a comma before and after each code. For
example, suppose the label contains these options:

Delivered, with an Abbr value of D1

Departed Pickup, with an Abbr value of AF
To actualize the stop on the order, you would enter ,D1,AF,
Brokerage EDI
TMWSuite
5.12
Revised: 7/2017
Working with Inbound 214 status update files
Inbound214MiscDates
Use the Inbound214MiscDates General Info Table setting to identify the EDI status codes
used for storing records in a miscellaneous dates table. This setting is not used to update the
actual stop status or date/time.
Inbound214MiscDates
Applies to
TMWSuite: 2008 and later, TMW Operations
Description
This setting identifies the EDI status codes used for storing records in a
miscellaneous dates table. This information does not update the actual stop status
or date/time.
String1

Setting is blank by default
The dates/times are not stored in the miscellaneous dates table.

User-specified list of EDI status codes
Enter the codes that will be used for storing records in a miscellaneous dates
table. Your entry must exactly match the Abbr column value of the
Inbound214Status label options you want to use. You must enter a comma
before and after each code. For example, suppose the label contains these
options:

Pickup Appt, with an Abbr value of AA

Delivery Appt, with an Abbr value of AB
You would enter ,AA,AB,
Processing Outbound 214 files
You can set up the inbound 214 process to send an automatic outbound 214 (auto-214) with an
order status update to the designated trading partner. The following must be met:

The stop has been actualized.
This can be an automatic or manual process. If the stop and reason codes are set up to do so,
the system will actualize the stop automatically and use the reason codes that were assigned
from the inbound 214 to be included on the outbound 214.

The trading partner is set up to run auto-214s.

The license for the EDI Scheduler is applied to your TMWSuite database and the application
is set up to process auto-214s.

In File Maintenance, the EDI Codes Maintenance window’s Auto214 tab is set up for
outbound 214 events. .
For further information on how to set up outbound auto-214s, refer to the Setting up the
system to generate auto-214s section of the “Setting up TMWSuite for EDI” chapter in the
TMWSuite EDI Interface guide.
Brokerage EDI
TMWSuite
5.13
Revised: 7/2017