X12 214 Transportation Carrier Shipment Status Message
This X12 Transaction Set contains the format and establishes the data contents of the Transportation Carrier Shipment Status Message Transaction Set (214) for use within the context of an Electronic Data Interchange (EDI) environment.
This transaction set can be used by a transportation carrier to provide shippers, consignees, and their agents with the status of shipments in terms of dates, times, locations, route, identifying numbers, and conveyance.
- ~ Segment
- * Element
- > Component
- ^ Repetition
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code identifying the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00501
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
Code indicating whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- QM
- Transportation Carrier Shipment Status Message (214)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 005010
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 214
- Transportation Carrier Shipment Status Message
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Transportation Carrier Shipment Status Message
To transmit identifying numbers and other basic data relating to the transaction set
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- B1001 is the carrier assigned reference number.
- B1001 is the carrier's PRO (invoice number) that identifies the shipment.
Carrier's Reference Number - Pro Number
Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)
KINEXO TMS system Load Numbers:
This field must contain the Load Number found in the B2-04 of the Kinexo 204.
The load number from our system will begin with an “L”. (i.e.: L100850)
Standard Carrier Alpha Code
- B1003 is required when used in Transaction Set 214.
The B10-03 must contain the carrier's SCAC code as sent to the carrier in the EDI 204 B2-02.
If the carrier has a different SCAC for intermodal use, that should be the SCAC used here on intermodal loads.
Detail
Transaction Set Line Number
To reference a line number in a transaction set
Number assigned for differentiation within a transaction set
This field should be mapped from the S5-01 of the 204 and represents the stop sequence number. If you did not receive a 204 automated tender, then just start numbering the LX segments with 1, and increase sequentially by 1, for each LX in the document.
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
Please return in the EDI 214 the PO, BN reference numbers that are sent to the carrier in the corresponding EDI 204 load tender.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- BN
- Booking Number
Please return in the EDI 214 the BN reference number that is sent on the EDI
204 load tender. - PO
- Purchase Order Number
Please return in the EDI 214 the PO reference number that is sent on the EDI
204 load tender.
Remarks
To transmit information in a free-form format for comment or special instruction
Shipment Status Details
To specify the status of a shipment, the reason for that status, the date and time of the status and the date and time of any appointments scheduled.
Pickup codes (AA, X3, AF) and delivery codes (AB, X1, D1). Kinexo requests all the codes shown be sent .
All codes that Kinexo accepts are shown. Please only send the codes that are specified. If you need to
send codes other than are specified please coordinate these code changes with Kinexo
Code indicating the status of a shipment
- If AT701 is present, AT705 is the date the status occurred. If AT703 is present, AT705 is a date related to an appointment.
- If AT701 is present, AT706 is the time of the status. If AT703 is present, AT706 is the time of the appointment.
- AF
- Carrier Departed Pickup Location with Shipment
- D1
- Completed Unloading at Delivery Location
- X1
- Arrived at Delivery Location
- X3
- Arrived at Pickup Location
Code indicating the reason a shipment status or appointment reason was transmitted
Only the AT7-02 codes shown are accepted. Note: Only the AT7-02 codes shown are accepted.
Please always include an appropriate AT7-02 code.
If shipment is NOT late, then always use 'NS'.
Do NOT use 'NS' on late shipment updates.
Must use one of the late reason codes shown on ALL late shipment updates.
- A1
- Missed Delivery
- AG
- Consignee Related
- AJ
- Other Carrier Related
- AM
- Shipper Related
- NS
- Normal Status
Always include AT7-02 as "NS" - Normal Status if no other code applies.
Code indicating the status of an appointment to pickup or deliver a shipment
When 214's containing Pickup (AA) and Delivery Appointment (AB) codes are sent they should be sent in the AT7-03. When they are sent the AT7-01 and AT7-02
will be empty.
- AA
- Pickup Appointment Date and/or Time
- AB
- Delivery Appointment Date and/or Time
Code indicating the reason a shipment status or appointment reason was transmitted
Only the AT7-04 codes shown are accepted. Only the AT7-04 codes shown are accepted.
Please always include an appropriate AT7-04 code.
If shipment is NOT late, then always use 'NA'.
Do NOT use 'NA' on late shipment updates.
Must use one of the late reason codes shown on ALL late shipment updates.
- AG
- Consignee Related
- AI
- Mechanical Breakdown
- AJ
- Other Carrier Related
- AM
- Shipper Related
- NA
- Normal Appointment
When AT7-03 = "AA" or "AB" always include "NA" in AT7-04 if no other code
applies.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
When AT7-03 contains "AA" then AT7-05 should contain the Pickup
Appointment Date.
When AT7-03 contains "AB" then AT7-05 should contain the Delivery Appointment
Date.
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
When AT7-03 contains "AA" then AT7-06 should contain the Pickup
Appointment Time.
When AT7-03 contains "AB" then AT7-06 should contain the Delivery Appointment
Time.
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
- If AT707 is not present then AT706 represents local time of the status.
- ET
- Eastern Time
- LT
- Local Time
Equipment, Shipment, or Real Property Location
To specify the location of a piece of equipment, a shipment, or real property in terms of city and state or longitude and latitude or postal code
The MS1 segment is required by Kinexo on all EDI 214's. The MS1 should correspond with the location and status being reported.
Code (Standard State/Province) as defined by appropriate government agency
Code identifying the country
Please use 'USA' and not 'US' for the United States.
Remarks
To transmit information in a free-form format for comment or special instruction
Use of the N1 segment:
The correct N1 - SF (Ship From) and N1 - ST (Ship To) address information needs to be returned that
corresponds with that stop.
You should return the N1-SF segments for the pickup statuses (AA, X3, and AF). You should return the
N1-ST segments for the delivery statuses (AB, X1, D1).
Therefore you will have one N1, N2, N3, N4 segment group, either SF or ST, per 214 status (per ST/SE).
Please return the correct Ship From and Ship To address information that is sent to the carrier in the EDI 204 load tender.
Party Identification
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Additional Name Information
To specify additional names
Party Location
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
This field should represent the stop sequence number that corresponds with the actual stop that is being reported. The EDI 204 contains the stop number in the S5-01.
Code qualifying the Reference Identification
- QN
- Stop Sequence Number
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.