X12 214 Transportation Carrier Shipment Status Message
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify 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 to identify 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)
Qualifier to designate 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
Qualifier to designate 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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate 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
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 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
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
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) 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
Beginning Segment for Transportation Carrier Shipment Status Message
To transmit identifying numbers and other basic data relating to the transaction set
Please note that the Transport / Job Order (e.g. 7PHLSA1234) has to be
reported in the B1001 element and not in the B1002 element.
Example Syntax:
B107PHLSA12340123465*SCAC~
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.
Hamburg Süd Transport / Job Order 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)
Job order of the truck vendor
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
Example Syntax:
L116PHLSA1234BN~
L11SUDU7N3400812147BM~
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
- BN
- Booking Number
- MCI
- Motor Carrier Identification Number
Only to be used in case trucking company has no SCAC code assigned. Hamburg Süd will inform the trucker, which ID to use.
- SN
- Seal Number
Assigned Number
To reference a line number in a transaction set
Example Syntax:
LX*1~
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.
The appointment time event codes "AA" and "AB" should be reported in AT703 element in contrast to the other event codes that have to be reported in the AT701 element.
Example Syntax:
Appointment: AT7AA201705040800LT~
Regular event: AT7CDNS*201701281700*LT~
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.
- AA
- Pick-up Appointment Date and/or Time (Appointment Time for Export)
- AB
- Delivery Appointment Date and/or Time (Appointment Time for Import)
- AF
- Carrier Departed Pick-up Location with Shipment
- CA
- Shipment Cancelled
- CD
- Carrier Departed Delivery Location
- CP
- Completed Loading at Pick-up Location
- D1
- Completed Unloading at Delivery Location
- X1
- Arrived at Delivery Location
- X3
- Arrived at Pick-up Location
Code indicating the reason a shipment status or appointment reason was transmitted
- NS
- Normal Status
Code indicating the status of an appointment to pick-up or deliver a shipment
- AA
- Pick-up Appointment Date and/or Time
Appointment Time for Export
- AB
- Delivery Appointment Date and/or Time
Appointment Time for Import
Code indicating the reason a shipment status or appointment reason was transmitted
Date expressed as CCYYMMDD
Example: 20160526 (26th May 2016)
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)
Example: 224529 (10:45:29 pm)
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.
- 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
Example Syntax:
MS1DETROITMI*US~
Code (Standard State/Province) as defined by appropriate government agency
Code identifying the country
Country code according to ISO 3166-1.
The ISO 3166-1 alpha-2 codes are two-letter country codes defined in ISO 3166-1, part of the ISO 3166 standard published by the International Organization for Standardization (ISO), to represent countries, dependent territories, and special areas of geographical interest.
Equipment or Container Owner and Type
To specify the owner, the identification number assigned by that owner, and the type of equipment
Example Syntax:
MS2SUDU852938**7~
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
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
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Appointment time (Import)
B10*6PHL00JZEN*01234567*ABCD~
L11*SUDU15MANEN211AX*BM~
LX*1~
AT7***AB**20170202*1200*LT~
MS1*SENECA*SC*US~
MS2*SUDU*545487**5~
SE*8*0001~
Arrived at customer’s premises (Export)
B10*6JAXIA0770*01234567*ABCD~
L11*6JAXIA0770*BN~
LX*1~
AT7*X3*NS***20170125*0720*LT~
MS1*CHICAGO*IL*US~
MS2*HASU*431020**6~
SE*8*0002~
Arrived at customer’s premises (Import)
B10*6PHL00JZEN*01234567*ABCD~
L11*SUDU15MANEN211AX*BM~
LX*1~
AT7*X1*NS***20170202*1425*LT~
MS1*SENECA*SC*US~
MS2*SUDU*545487**5~
SE*8*0002~
Export Appointment time (container known)
B10*6JAXIA0770*0123456*ABCD~
L11*6JAXIA0770*BN~
LX*1~
AT7***AA**20170512*0935*LT~
MS1*CHICAGO*IL*US~
MS2*HASU*431020**6~
SE*8*0001~
Export Appointment time (container unknown)
B10*6JAXIA0770*0123456*ABCD~
L11*6JAXIA0770*BN~
LX*1~
AT7***AA**20170512*0935*LT~
MS1*CHICAGO*IL*US~
SE*7*0001~
Left customer’s premises (Export)
B10*6JAXIA0770*01234567*ABCD~
L11*6JAXIA0770*BN~
LX*1~
AT7*AF*NS***20170125*1510*LT~
MS1*CHICAGO*IL*US~
MS2*HASU*431020**6~
SE*8*0004~
Left customer’s premises (Import)
B10*6PHL00JZEN*01234567*ABCD~
L11*SUDU15MANEN211AX*BM~
LX*1~
AT7*CD*NS***20170204*0715*LT~
MS1*SENECA*SC*US~
MS2*SUDU*545487**5~
SE*8*0004~
Loading of container completed (Export)
B10*6JAXIA0770*01234567*ABCD~
L11*6JAXIA0770*BN~
LX*1~
AT7*CP*NS***20170125*1500*LT~
MS1*CHICAGO*IL*US~
MS2*HASU*431020**6~
SE*8*0003~
Transport / Shipment cancelled
B10*6PHL00JZEN*01234567*ABCD~
L11*SUDU15MANEN211AX*BM~
LX*1~
AT7*CA*NS***20170204*0715*LT~
MS1*SENECA*SC*US~
MS2*SUDU*545487**5~
SE*8*0004~
Unloading completed (Import)
B10*6PHL00JZEN*01234567*ABCD~
L11*SUDU15MANEN211AX*BM~
LX*1~
AT7*D1*NS***20170203*1200*LT~
MS1*SENECA*SC*US~
MS2*SUDU*545487**5~
SE*8*0003~
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.