X12 214 Shipment Status Update
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).
Ryder: For Truck Load carriers, the status update is required within 4 hours of the event.
For Less Than Truck Load carriers the status update is required by 5:00 am CST the morning following the event.
- 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
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- B1001 is the carrier's PRO (invoice number) that identifies the shipment.
Ryder: Carrier Pro/Invoice Number as sent in the N9 02 on the EDI 990. Sent in the L11 01 with a CN Qualifier In the L11 02 on the EDI 204.
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)
Ryder: Shipper's Bill Of Lading Number. May be sent in the Header Level L11 01 with a MB qualifier in the L11 02, the Header Level L11 01 with an OQ qualifier in the L11 02, or in the Detail Level L11 01 with a P8 qualifier in the L11 02 on the EDI 204.
Standard Carrier Alpha Code
- B1003 is required when used in Transaction Set 214.
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
- At least one of L1101 or L1103 is required.
- If either L1101 or L1102 is present, then the other is required.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
Ryder:
AO - Consignee Confirmation Number
BM - Should be sent in the B10 02.
LO - Ryder Load Number. Sent in the B2 04 in the EDI 204
PO - Customer PO. Sent in the L11 01 with a DJ qualifier in the L11 02 on the EDI 204
QN - Stop Number, 1 is the Pick Up, Increment Each Additional Stop By 1. 99 may be used for the final delivery location.
- AO
- Appointment Number
- BM
- Bill of Lading Number
- LO
- Load Planning Number
- PO
- Purchase Order Number
- QN
- Stop Sequence Number
Name
To identify a party by type of organization, name, and code
- At least one of N102 or N103 is required.
- If either N103 or N104 is present, then the other is required.
Code identifying an organizational entity, a physical location, property or an individual
- CN
- Consignee
Code designating the system/method of code structure used for Identification Code (67)
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
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
Note- Ryder does not currently support this functionality. This will be supported in the upcoming release of the v005010 EDI 214.
If you are going to use a single Ryder EDI Receiver Id for all Ryder EDI 214 responses then you MUST put the correct Ryder client code in this element. The correct Ryder client code is mandatory either by using Ryder's unique client EDI Receiver Id or through the use of the N1 04.
Ryder Client Id For N1 04:
ABC – ABC Bottling Group
BACARDI - Bacardi
BOEING - Boeing
ADAMS – Cadbury Adams
DAP – Philips DAP
DRPEPPER – Dr. Pepper/Seven Up
DUKE – Duke Energy
FPLG – Florida Power and Light
HAR – Harman
HONEYWELL - Honeywell
HPFTL – Hewlett Packard FTL
HPNACC –Hewlett Packard NACC
HUHTAMAKI – Huhtamaki Americas
IGPS – Intelligent Global Pooling Systems
ITC – Imperial Tobacco Canada
ITO – Imperial Tobacco Mexico
LEX - Lexmark
MFRIDGE - Microfridge
MHA – Master Halco
MOLSON – Molson
MOTTS – Motts/Snapple
PBC – Pitney Bowes
PCE – Philips Consumer
PELLA – Pella Window and Door
PRC – Pratt & Whitney Canada
PRU – Pratt & Whitney US
RECKITT – Reckitt Benckiser
SYNGENTA – Syngenta Seed
USPS – United States Postal Service
XEROXGT - Xerox
Address Information
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)
Name
To identify a party by type of organization, name, and code
- At least one of N102 or N103 is required.
- If either N103 or N104 is present, then the other is required.
Code identifying an organizational entity, a physical location, property or an individual
- SH
- Shipper
Code designating the system/method of code structure used for Identification Code (67)
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
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
Note- Ryder does not currently support this functionality. This will be supported in the upcoming release of the v005010 EDI 214.
If you are going to use a single Ryder EDI Receiver Id for all Ryder EDI 214 responses then you MUST put the correct Ryder client code in this element. The correct Ryder client code is mandatory either by using Ryder's unique client EDI Receiver Id or through the use of the N1 04.
Ryder Client Id For N1 04:
ABC – ABC Bottling Group
BACARDI - Bacardi
BOEING - Boeing
ADAMS – Cadbury Adams
DAP – Philips DAP
DRPEPPER – Dr. Pepper/Seven Up
DUKE – Duke Energy
FPLG – Florida Power and Light
HAR – Harman
HONEYWELL - Honeywell
HPFTL – Hewlett Packard FTL
HPNACC –Hewlett Packard NACC
HUHTAMAKI – Huhtamaki Americas
IGPS – Intelligent Global Pooling Systems
ITC – Imperial Tobacco Canada
ITO – Imperial Tobacco Mexico
LEX - Lexmark
MFRIDGE - Microfridge
MHA – Master Halco
MOLSON – Molson
MOTTS – Motts/Snapple
PBC – Pitney Bowes
PCE – Philips Consumer
PELLA – Pella Window and Door
PRC – Pratt & Whitney Canada
PRU – Pratt & Whitney US
RECKITT – Reckitt Benckiser
SYNGENTA – Syngenta Seed
USPS – United States Postal Service
XEROXGT - Xerox
Address Information
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)
Assigned Number
To reference a line number in a transaction set
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.
Ryder: The proper use of the AT7 segment for reporting events, event reasons and appointments is as follows:
Events- Use the AT7 01 for the actual event and the AT7 02 NS qualifier
Event Reason- Use the AT7 01 for the actual event and the AT7 02 NS qualifier Appointment- Use the AT7 03 for the actual event and the AT7 04 NA qualifier
Code indicating the status of a shipment
At a minimum the carrier must be able to support the AF (Pick Up) and D1 (Delivered) status codes. If you are unable to support either of these status codes contact Ryder EDI so that you may be implemented on Ryder's web enabled tendering and status update applications.
The D1 and AF status codes are to be used for the actual event. These two code events are to be used to record the actual event day and time and will be used to update Ryder's tracking site accordingly.
- A9
- Shipment Damaged
- AF
- Carrier Departed Pick-up Location with Shipment
- AG
- Estimated Delivery
- CD
- Carrier Departed Delivery Location
- D1
- Completed Unloading at Delivery Location
- J1
- Delivered to Connecting Line
- K1
- Arrived at Customs
- L1
- Loading
- OO
- Paperwork Received - Did not Receive Shipment or Equipment
- P1
- Departed Terminal Location
- PR
- U.S. Customs Hold at In-Bond Location
- R1
- Received from Prior Carrier
- S1
- Trailer Spotted at Consignee's Location
- SD
- Shipment Delayed
- X1
- Arrived at Delivery Location
- X2
- Estimated Date and/or Time of Arrival at Consignee's Location
- X3
- Arrived at Pick-up Location
- X4
- Arrived at Terminal Location
- X5
- Arrived at Delivery Location Loading Dock
- X6
- En Route to Delivery Location
Code indicating the reason a shipment status or appointment reason was transmitted
- A2
- Incorrect Address
- AD
- Customer Requested Future Delivery
- AG
- Consignee Related
- AH
- Driver Related
- AJ
- Other Carrier Related
- AM
- Shipper Related
- AN
- Holiday - Closed
- AO
- Weather or Natural Disaster Related
- AQ
- Recipient Unavailable - Delivery Delayed
- AS
- Hold Due to Customs Documentation Problems
- AX
- Insufficient Pick-up Time
- AY
- Missed Pick-up
- B1
- Consignee Closed
- B2
- Trap for Customer
- B5
- Held for Consignee
- B8
- Improper Unloading Facility or Equipment
- BB
- Held per Shipper
- BD
- Border Clearance
- BF
- Carrier Keying Error
- BH
- Insufficient Time to Complete Delivery
- BM
- Flatcar Shortage
- BP
- Load Shifted
- BQ
- Shipment Overweight
- BS
- Refused by Customer
- C5
- Customer Strike
- D1
- Carrier Dispatch Error
- D2
- Driver Not Available
- HB
- Held Pending Appointment
- NS
- Normal Status
- P4
- Held for Full Carrier Load
- RC
- Reconsigned
- S1
- Delivery Shortage
- T7
- Insufficient Delivery Time
Code indicating the status of an appointment to pick-up or deliver a shipment
Ryder: At a minimum the carrier must be able to support the AB (Delivery Appointment) and AA (Pick Up Appointment) status code. If you are unable to support this status code contact Ryder EDI so that you may be implemented on Ryder's web enabled tendering and status update applications.
AA - Pick Up Appointments Are Expected As Soon As They Are Made
AB - Delivery Appointments Are Expected As Soon As They Are Made
- AA
- Pick-up Appointment Date and/or Time
- AB
- Delivery Appointment Date and/or Time
Code indicating the reason a shipment status or appointment reason was transmitted
- NA
- Normal Appointment
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)
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.
Ryder: Please use the time zone for which the event occurred.
- AT
- Alaska Time
- CT
- Central Time
- ET
- Eastern Time
- LT
- Local Time
- MT
- Mountain Time
- PT
- Pacific 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
Code (Standard State/Province) as defined by appropriate government agency
Code indicating the longitude in degrees (3 positions), minutes (2 positions), and seconds (2 positions)
- MS104 is the longitude expressed in Degrees, Minutes, and Seconds.
Code indicating the latitude in degrees (3 positions), minutes (2 positions), seconds (2 positions)
- MS105 is the latitude expressed in Degrees, Minutes, and Seconds.
Code identifying geographic direction
- MS106 may only be 'E' or 'W'.
- E
- East
- W
- West
Equipment or Container Owner and Type
To specify the owner, the identification number assigned by that owner, and the type of equipment
MS203 identifies the type for the equipment specified in MS202.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Code identifying type of equipment used for shipment
- MS203 identifies the type for the equipment specified in MS202.
Shipment Weight, Packaging and Quantity Data
To specify shipment details in terms of weight, and quantity of handling units
Code defining the type of weight
- A
- Consolidated Weight
- A1
- Dimensional Weight
- B
- Billed Weight
- F
- Deficit Weight
- G
- Gross Weight
Number of units (pieces) of the lading commodity
- AT804 is the quantity of handling units that are not unitized (for example a carton). When added to the quantity in AT805, it is the total quantity of handling units in the shipment.
Electronic Format Identification
To provide basic information about the electronic format of the interchange data
Code indicating the level of confidentiality assigned by the sender to the information following
- ZZ
- Mutually Defined
Code indicating that this element will be used to tell an EDI translator program which security technique to use
Revision level of a particular format, program, technique or algorithm
Identifies the name of the software program from which the technical data originates
Revision level of a particular format, program, technique or algorithm
Industry or proprietary standard used to identify the format of the data
Revision level of a particular format, program, technique or algorithm
Identifies the digital data compression means and the type
Code indicating the drawing size and orientation of a technical drawing as specified and described in the current version of standards ANSI Y14.1 and ISO 5457 (E); see the listed ANSI and ISO standards for the maximum lengths for rolled sheets *
Name assigned or declared for a file or used by a program to identify a file; exact format of the name depends on the computer operating system being used; name also may be known as the file's "data set name"
Organization of a data block such as fixed length, variable length, spanned, etc. Synonym for "data format"
Quantity of characters or bytes in a record. Synonyms are "logical record length" and "record size"
Quantity of data elements in a block, usually specified in units such as records, words or characters; synonym for "block size"
Revision level of a particular format, program, technique or algorithm
Binary Data
To transfer binary data in a single data segment and allow identification of the end of the data segment through a count; there is no identification of the internal structure of the binary data in this segment
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
LT Example
GS*QM*SENDERGS*RECEIVERGS*20231103*025525*000000001*X*004010~
ST*214*099510001~
B10*4735103*5365205*SCAC~
L11*5365205*LO~
L11*01*QN~
L11*392651*PO~
L11*392651*PO~
N1*SH*HUHTAMAKI FSBU~
N3*5566 NEW VIENNA ROAD~
N4*NEW VIENNA*OH*45159*US~
N1*CN*HUHTAMAKI~
N3*100 HIGGENSON AVE~
N4*LINCOLN*RI*02865*US~
LX*1~
AT7***AA*NA*20080903*1600*ET~
MS1*NEW VIENNA*OH*US~
AT8*G*L*6240*402~
EFI*ZZ*NAME~
SE*18*099510001~
GE*1*000000001~
IEA*1*000000001~
LTL Example
GS*QM*SCAC*006922827USP1*20080903*1132*20832*X*004010-
ST*214*208320001-
B10*082269732X*007018135*SCAC*3-
L11*1000713*PO-
L11*5335266*LO-
N1*SH*USPS-
N3*500 SW GARY ORMSBY DR-
N4*TOPEKA*KS*66624-
N1*CN*MAINT STOCKRM-
N3*7540 E 53RD PL-
N4*DENVER*CO*802660001-
LX*1-
AT7*A9*B2***20080903*1007*MT-
AT7*AG*B2***20080902*1007*MT-
AT8*B*L*305*2-
EFI*ZZ*NAME-
SE*16*208320001-
GE*1*20832-
IEA*1*000020832-
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.