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

X12 214 Transportation Carrier Shipment Status Message

X12 Release 4010

This Draft Standard for Trial Use 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
EDI samples
  • Arrival at pickup location
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/kraft-heinz/transportation-carrier-shipment-status-message/01GYW5NG6GTZBKCWF5E8P7QY5Q
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
ST
010
Transaction Set Header
Max use 1
Required
B10
020
Beginning Segment for Transportation Carrier Shipment Status Message
Max use 1
Required
K1
040
Remarks
Max use 10
Optional
0200 Loop
LX
130
Assigned Number
Max use 1
Required
0205 Loop
L11
150
Business Instructions and Reference Number
Max use 10
Required
SE
610
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
Identifier (ID)

Code to identify 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
Identifier (ID)

Code to identify 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

Qualifier to designate 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

Qualifier to designate 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
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
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 sent by the sender to request an interchange acknowledgment (TA1)

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

Code to indicate 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
Identifier (ID)

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

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
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 used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
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
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) 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
020
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

Usage notes

The information sent in this segment will be used to apply the status to the correct shipment. The carrier will send us the PRO number for the shipment, the BOL that was sent, and the SCAC code.

The system will look for the BOL to ensure the shipment exists. If it does, it will continue to look for the stop off information. If not, the transmission will error out.

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

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 PRO number

B10-02
145
Shipment Identification Number
Optional
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

BOL sent to the carrier in the B204 (element 145)

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

SCAC code

K1
040
Heading > K1

Remarks

OptionalMax use 10

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

Usage notes

This segment will be used if the carrier is providing any information back. It will be mapped to the comments associated with the status.

Example
K1-01
61
Free-Form Message
Required
String (AN)
Min 1Max 30

Free-form information

Usage notes

Free-form information

K1-02
61
Free-Form Message
Optional
String (AN)
Min 1Max 30

Free-form information

Usage notes

Free-form information

0200 Loop
OptionalMax >1
LX
130
Heading > 0200 Loop > LX

Assigned Number

RequiredMax use 1

To reference a line number in a transaction set

Usage notes

This segment is used as a counter for EDI purposes only.

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

Number assigned for differentiation within a transaction set

Usage notes

Number assigned to the unique occurrences of status related to the stop off

0205 Loop
RequiredMax >1
AT7
140
Heading > 0200 Loop > 0205 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

This segment is the main status segment where most of the critical information is contained. When the carrier sends in an X3 or AF value in the AT701, the status should be mapped to the first pickup location (stop 01 in our current system). When the carrier sends in an X1 or a CD, the status should be mapped to the final delivery stop off (stop 02 in our current system).

The AT702 (for the X3, AF, X1, and CD) is required. If the shipment is arriving on time, the value will be “NS”. If the carrier is arriving or departing late, use a late code which best describes the reason. See
Reason codes below.

The AT703 (for the AA and AB) relates to the appointment status. When the carrier sends in an AA, the appointment will be applied to the first pickup location only (stop 01 in our current system). When the carrier sends in an AB, the appointment will be applied to the final delivery stop off (stop 02 in our current system only).

The AT704 is required (for the AA and AB). If the shipment is arriving on time, the value will be “NA.” If the carrier is planning to arrive or depart late, use a late code which best describes the reason. See Reason Codes.

If AT707 is not present, then AT706 represents the local time of the status.

Example
If either Shipment Status Code (AT7-01) or Shipment Status or Appointment Reason Code (AT7-02) is present, then the other is required
Only one of Shipment Status Code (AT7-01) or Shipment Appointment Status Code (AT7-03) may be present
If either Shipment Appointment Status Code (AT7-03) or Shipment Status or Appointment Reason Code (AT7-04) is present, then the other 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 Code
Optional
Identifier (ID)

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

Used for arrival/departure status

AF
Carrier Departed Pick-up Location with Shipment
CD
Carrier Departed Delivery Location
X1
Arrived at Delivery Location
X2
Estimated Date and/or Time of Arrival at Consignee's Location

not used by Kraft Heinz

X3
Arrived at Pick-up Location
AT7-02
1651
Shipment Status or Appointment Reason Code
Optional
Identifier (ID)

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

Usage notes

The value of the reason code will be NS if the actual time does not
differ from the appointment.

AD
Customer Requested Future Delivery
AH
Driver Related
AI
Mechanical Breakdown
AJ
Rail delayed
AL
Previous Stop
AO
Weather or Natural Disaster Related
AS
Hold Due to Customs Inspection
AX
Insufficient or no Pick Up Time
B1
Consignee Closed/Holiday
BQ
Shipment Overweight
BS
Refused by Customer
NA
Normal Appointment
NS
Normal Status
P3
Shipper Loaded Late
T3
Tractor/Trailer Not Available
T7
Insufficient Delivery Time
AT7-03
1652
Shipment Appointment Status Code
Optional
Identifier (ID)

Code indicating the status of an appointment to pick-up or deliver a shipment

Usage notes

Used for pickup/delivery appointment

AA
Pickup appointment
AB
Delivery/Stop off appointment
AT7-04
1651
Shipment Status or Appointment Reason Code
Optional
Identifier (ID)
Min 2Max 2

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

Usage notes

The value of the reason code will be NA if the actual time does not differ from the appointment. See the table below for valid codes.

Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Actual Date of the Event

Optional
Time (TM)
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

Actual Time (Local) of the event expressed in 24-hour clock time as follows: HHMM where H = hours (00-23), M = minutes (00-59)

AT7-07
623
Time Code
Optional
Identifier (ID)

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

all times should be transmitted as LOCAL times

LT
Local Time
MS2
146
Heading > 0200 Loop > 0205 Loop > MS2

Equipment or Container Owner and Type

OptionalMax use 1

To specify the owner, the identification number assigned by that owner, and the type of equipment

Example
MS2-01
140
Standard Carrier Alpha Code
Required
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

MS2-02
207
Equipment Number
Required
String (AN)
Min 1Max 10

Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

Usage notes

Equipment (Trailer) Number

MS2-03
40
Equipment Description Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying type of equipment used for shipment

  • MS203 identifies the type for the equipment specified in MS202.
MS2-04
761
Equipment Number Check Digit
Optional
Numeric (N0)
Min 1Max 1

Number which designates the check digit applied to a piece of equipment

0205 Loop end
L11
150
Heading > 0200 Loop > L11

Business Instructions and Reference Number

RequiredMax use 10

To specify instructions in this business relationship or a reference number

Usage notes

This data is used to match the status with the appropriate stop within the software. The carrier must send this segment with the reference number sent to them in the 204 L11 loop 300, element 01. This reference number can be sent with each and every AT7, but does not have to.

Example
If either Reference Identification (L11-01) or Reference Identification Qualifier (L11-02) is present, then the other is required
At least one of Reference Identification (L11-01) or Description (L11-03) is required
L11-01
127
Reference Identification
Optional
String (AN)
Min 1Max 30

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

Usage notes

SID – sent to carrier in 204, L11 segment, loop 300, element 01

L11-02
128
Reference Identification Qualifier
Optional
Identifier (ID)

Code qualifying the Reference Identification

SI
Shipper's Identifying Number for Shipment (SID)
L11-03
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

Usage notes

Description - Appointment confirmation number from customer

0200 Loop end
SE
610
Heading > 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

Heading 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

EDI Samples

Arrival at pickup location

B10*1962072*2016722790*SCAC~
LX*1~
AT7*X3*NS***20150629*0702*LT~
MS2*SCAC*Equipment#~
L11*20167227900101*SI~

Arrive at delivery location

B10*1962072*2016722790*SCAC~
LX*1~
AT7*X1*NS***20150630*0800*LT~
MS2*SCAC*Equipment#~
L11*20167227900102*SI~

Delivery appointment

B10*1962072*2016722790*SCAC~
LX*1~
AT7***AB*NA*20150630*1430*LT~
L11*20167227900102*SI~

Departure from pickup location

B10*1962072*2016722790*SCAC~
LX*1~
AT7*AF*NS***20150629*1131*LT~
MS2*SCAC*Equipment#~
L11*20167227900101*SI~

Departure from pickup location (Stop 0102)

B10*1962072*2016722790*SCAC~
LX*1~
AT7*CD*NS***20150630*0932*LT~
MS2*SCAC*Equipment#~
L11*20167227900102*SI~

Pickup appointment

B10*1962072*2016722790*SCAC~
LX*1~
AT7***AA*NA*20150629*1100*LT~
L11*20167227900101*SI~

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.