Kinexo
/
Transportation Carrier Shipment Status Message
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Kinexo. Contact Kinexo for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Kinexo logo

X12 214 Transportation Carrier Shipment Status Message

X12 Release 5010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/kinexo/transportation-carrier-shipment-status-message/01HATBV51Y7MESZR02G5MTSQMB
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
detail
1000 Loop
SE
2100
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required

Code identifying the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required

Code identifying the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
HHMM format

Time of the interchange

ISA-11
I65
Repetition Separator
Required
String (AN)
Min 1Max 1

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
ISA-12
I11
Interchange Control Version Number
Required

Code specifying the version number of the interchange control segments

00501
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code indicating sender's request for an interchange acknowledgment

0
No Interchange Acknowledgment Requested
1
Interchange Acknowledgment Requested (TA1)
ISA-15
I14
Interchange Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code indicating whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required

Code identifying a group of application related transaction sets

QM
Transportation Carrier Shipment Status Message (214)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission; codes agreed to by trading partners

GS-04
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

GS-05
337
Time
Required
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required

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

ST
0100
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required

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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

B10
0200
Heading > B10

Beginning Segment for Transportation Carrier Shipment Status Message

RequiredMax use 1

To transmit identifying numbers and other basic data relating to the transaction set

Example
B10-01
127
Reference Identification
Optional
String (AN)
Min 1Max 50

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.
Usage notes

Carrier's Reference Number - Pro Number

B10-02
145
Shipment Identification Number
Required
String (AN)
Min 1Max 30

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)

Usage notes

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)

B10-03
140
Standard Carrier Alpha Code
Required
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

  • B1003 is required when used in Transaction Set 214.
Usage notes

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.

Heading end

Detail

1000 Loop
RequiredMax 999999
LX
0100
Detail > 1000 Loop > LX

Transaction Set Line Number

RequiredMax use 1

To reference a line number in a transaction set

Example
LX-01
554
Assigned Number
Required
Numeric (N0)
Min 1Max 6

Number assigned for differentiation within a transaction set

Usage notes

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.

L11
0200
Detail > 1000 Loop > L11

Business Instructions and Reference Number

RequiredMax use 999

To specify instructions in this business relationship or a reference number

Usage notes

Please return in the EDI 214 the PO, BN reference numbers that are sent to the carrier in the corresponding EDI 204 load tender.

Example
L11-01
127
Reference Identification
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

L11-02
128
Reference Identification Qualifier
Required

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.

K1
0500
Detail > 1000 Loop > K1

Remarks

OptionalMax use 10

To transmit information in a free-form format for comment or special instruction

Example
K1-01
61
Free-form Information
Required
String (AN)
Min 1Max 30

Free-form information

K1-02
61
Free-form Information
Optional
String (AN)
Min 1Max 30

Free-form information

1100 Loop
RequiredMax 10
AT7
0800
Detail > 1000 Loop > 1100 Loop > AT7

Shipment Status Details

RequiredMax use 1

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.

Usage notes

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

Example
If Shipment Status or Appointment Reason Code (AT7-02) is present, then Shipment Status Indicator (AT7-01) is required
Only one of Shipment Status Indicator (AT7-01) or Shipment Appointment Status Code (AT7-03) may be present
If Shipment Status or Appointment Reason Code (AT7-04) is present, then Shipment Appointment Status Code (AT7-03) is required
If Time (AT7-06) is present, then Date (AT7-05) is required
If Time Code (AT7-07) is present, then Time (AT7-06) is required
AT7-01
1650
Shipment Status Indicator
Required

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
AT7-02
1651
Shipment Status or Appointment Reason Code
Optional

Code indicating the reason a shipment status or appointment reason was transmitted

Usage notes

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.

AT7-03
1652
Shipment Appointment Status Code
Optional

Code indicating the status of an appointment to pickup or deliver a shipment

Usage notes

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
AT7-04
1651
Shipment Status or Appointment Reason Code
Optional

Code indicating the reason a shipment status or appointment reason was transmitted

Usage notes

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.

AT7-05
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

Usage notes

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.

AT7-06
337
Time
Optional
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

Usage notes

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.

AT7-07
623
Time Code
Optional

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
MS1
0900
Detail > 1000 Loop > 1100 Loop > MS1

Equipment, Shipment, or Real Property Location

RequiredMax use 1

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

Usage notes

The MS1 segment is required by Kinexo on all EDI 214's. The MS1 should correspond with the location and status being reported.

Example
MS1-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

MS1-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

Code (Standard State/Province) as defined by appropriate government agency

MS1-03
26
Country Code
Required
Identifier (ID)
Min 2Max 3

Code identifying the country

Usage notes

Please use 'USA' and not 'US' for the United States.

K1
1100
Detail > 1000 Loop > 1100 Loop > K1

Remarks

OptionalMax use 1

To transmit information in a free-form format for comment or special instruction

Example
K1-01
61
Free-form Information
Required
String (AN)
Min 1Max 30

Free-form information

K1-02
61
Free-form Information
Optional
String (AN)
Min 1Max 30

Free-form information

1100 Loop end
1200 Loop
RequiredMax 5
Usage notes

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.

N1
1300
Detail > 1000 Loop > 1200 Loop > N1

Party Identification

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required

Code identifying an organizational entity, a physical location, property or an individual

SF
Ship From
ST
Ship To
N1-02
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional

Code designating the system/method of code structure used for Identification Code (67)

91
Assigned by Seller or Seller's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

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.
N2
1400
Detail > 1000 Loop > 1200 Loop > N2

Additional Name Information

OptionalMax use 1

To specify additional names

Example
N2-01
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

N2-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N3
1500
Detail > 1000 Loop > 1200 Loop > N3

Party Location

RequiredMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

N4
1600
Detail > 1000 Loop > 1200 Loop > N4

Geographic Location

RequiredMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

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.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Required
Identifier (ID)
Min 2Max 3

Code identifying the country

L11
1800
Detail > 1000 Loop > 1200 Loop > L11

Business Instructions and Reference Number

RequiredMax use 10

To specify instructions in this business relationship or a reference number

Example
L11-01
127
Reference Identification
Required
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

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.

L11-02
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

QN
Stop Sequence Number
1200 Loop end
1000 Loop end
SE
2100
Detail > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Detail end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

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.