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
- None included
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
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
See Customer Addendum for Reference Number Requirements.
Example: B10501209250B4188632~WXYZ
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.
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)
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
This should match the shipment id sent in EDI 204.
Example: L11V123456789BN
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
Code designating the system/method of code structure used for Identification Code (67)
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.
Address Information
To specify the location of the named party
Example: N3~1500 NW GRANDE ST
Geographic Location
To specify the geographic place of the named party
Example: N4DALLASTX75250US
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)
Date/Time
To specify pertinent dates and times
- Status and appointment dates and times shall not be transmitted in the G62 segment.
This segment could be mandatory based on the RXO Client specific requirements.
Example: G628620001116
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
Name
To identify a party by type of organization, name, and code
Example: N1CNMETRO DISTRIBUTORS
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)
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.
Address Information
To specify the location of the named party
Example: N3~1500 NW GRANDE ST
Geographic Location
To specify the geographic place of the named party
Example: N4DALLASTX75250US
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)
Date/Time
To specify pertinent dates and times
- Status and appointment dates and times shall not be transmitted in the G62 segment.
This segment could be mandatory based on the RXO Client specific requirements.
Example: G628620001116
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
Name
To identify a party by type of organization, name, and code
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)
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.
Address Information
To specify the location of the named party
Example: N3~1500 NW GRANDE ST
Geographic Location
To specify the geographic place of the named party
Example: N4DALLASTX75250US
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)
Date/Time
To specify pertinent dates and times
- Status and appointment dates and times shall not be transmitted in the G62 segment.
This segment could be mandatory based on the RXO Client specific requirements.
Example: G628620001116
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
Interline Information
To identify the interline carrier and relevant data
If a shipment is an interlined shipment then we should receive this segment.
Example: MS3WXYZ1AMARILLOLT~TX
Standard Carrier Alpha Code
- MS301 is the Standard Carrier Alpha Code (SCAC) of the interline carrier.
Code describing the relationship of a carrier to a specific shipment movement
Free-form text for city name
- MS303 is the city where the interline was performed.
Code specifying the method or type of transportation for the shipment
Code (Standard State/Province) as defined by appropriate government agency
Each LX Loop must contain only one set of detail segments within it.
The first LX01 value must be 1, and subsequent LX01's must increment by 1.
Example: LX~1
Assigned Number
To reference a line number in a transaction set
Each LX Loop must contain only one set of detail segments within it.
The first LX01 value must be 1, and subsequent LX01's must increment by 1.
Example: LX~1
Number assigned for differentiation within a transaction set
There can only be 1 AT7 in an LX Loop.
Only one of the AT701 or AT703 may be present. Whichever is present must have a related reason code present.
If AT701 is present, AT702 is required.
If AT703 is present, AT704 is required.
Example: AT7D1NS~~~200011202218CT
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.
Example: AT7D1NS~~~200011202218CT
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.
Code indicating the reason a shipment status or appointment reason was transmitted
Code indicating the status of an appointment to pick-up or deliver a shipment
Code indicating the reason a shipment status or appointment reason was transmitted
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.
- AD
- Alaska Daylight Time
- AS
- Alaska Standard Time
- AT
- Alaska Time
- CD
- Central Daylight Time
- CS
- Central Standard Time
- CT
- Central Time
- ED
- Eastern Daylight Time
- ES
- Eastern Standard Time
- ET
- Eastern Time
- GM
- Greenwich Mean Time
- HD
- Hawaii-Aleutian Daylight Time
- HS
- Hawaii-Aleutian Standard Time
- HT
- Hawaii-Aleutian Time
- LT
- Local Time
- MD
- Mountain Daylight Time
- MS
- Mountain Standard Time
- MT
- Mountain Time
- ND
- Newfoundland Daylight Time
- NS
- Newfoundland Standard Time
- NT
- Newfoundland Time
- PD
- Pacific Daylight Time
- PS
- Pacific Standard Time
- PT
- Pacific Time
- TD
- Atlantic Daylight Time
- TS
- Atlantic Standard Time
- TT
- Atlantic Time
- UT
- Universal Time Coordinate
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
If a shipment is an interlined shipment then we should receive this segment.
There can only be 1 MS1 in an LX Loop.
Example: MS1DALLASTX~US
Equipment or Container Owner and Type
To specify the owner, the identification number assigned by that owner, and the type of equipment
This segment could be mandatory based on the RXO Client specific requirements.
There can only be 1 MS2 in an LX Loop.
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.
Number which designates the check digit applied to a piece of equipment
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
Code qualifying the Reference Identification
Lading Exception Code
To specify the status of the shipment in terms of lading exception information
Q7 is MANDATORY only if a "Lading Exception" exists.
There can only be 1 Q7 in an LX Loop.
Example: Q7PPCS~1
Code indicating the condition of the shipment
Code for packaging form of the lading quantity
Number of units (pieces) of the lading commodity
Shipment Weight, Packaging and Quantity Data
To specify shipment details in terms of weight, and quantity of handling units
There can be only 1 AT8 segment in an LX Loop.
Example: AT8GL140020
Code specifying the weight unit
- E
- Metric Ton
- G
- Grams
- K
- Kilograms
- L
- Pounds
- M
- Measurement Ton
- S
- Short Ton
- T
- Long Ton
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.
Carton (Package) Detail
To transmit identifying codes, weights, and other related information related to an individual carton (package)
- Loops 0210, 0215 and 0220 shall be used in conjunction with loop 0200 to convey status for small package carrier shipments.
Individual or Organizational Name
To supply the full name of an individual or organizational entity
Code identifying an organizational entity, a physical location, property or an individual
Code qualifying the type of entity
- NM102 qualifies NM103.
Individual last name or organizational name
Code designating the system/method of code structure used for Identification Code (67)
Code describing entity relationship
- NM110 and NM111 further define the type of entity in NM101.
Code identifying an organizational entity, a physical location, property or an individual
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.