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
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
Used to indicate the start of a transaction set and to assign a control number.
Example: B10339346807936*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.
Carrier’s unique identifier for the shipment (typically PRO 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)
Redwood customer’s unique identifier for the shipment.
Standard Carrier Alpha Code
- B1003 is required when used in Transaction Set 214.
Carrier’s designated SCAC identifier code.
Job (Project) 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
Reference Value
Code qualifying the Reference Identification
- JB
- Job (Project) Number
A free-form description to clarify the related data elements and their content
Reference Description
Stop Sequence Number
To specify instructions in this business relationship or a reference number
Stop # reference is mandatory for multi-stop loads. Otherwise, L11s are optional.
Used to specify additional reference numbers beyond those provided on the B10 segment.
L11 segment with qualifier QN must be included to indicate which stop sequence number the status message pertains to. Any other L11s may be included.
Example: L112QN~
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Reference Value
Code qualifying the Reference Identification
Reference of QN is required for all stops.
- QN
- Stop Sequence Number
A free-form description to clarify the related data elements and their content
Reference Description
Name
To identify a party by type of organization, name, and code
Examples:
N1SHSHIPPERZZABC~
N1CNRECIPIENTZZDEF~
Code identifying an organizational entity, a physical location, property or an individual
- CN
- Consignee
- SF
- Ship From
- SH
- Shipper
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
If using a location identifier codes, use 93.
- 93
- Code assigned by the organization originating the transaction set
- ZZ
- Mutually Defined
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.
If using location identifier codes, please send code as received on tender.
Address Information
To specify the location of the named party
Example: N31765 N Elston AveSuite 300~
Geographic Location
To specify the geographic place of the named party
Example: N4CHICAGOIL60622USA~
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
Example: N1LWCustomer Name93CUSTOMERCODE~
If the Entity Identifier Code of “LW” is included in the tender, the data in the N1 segment must be included on corresponding 214 messages.
Code identifying an organizational entity, a physical location, property or an individual
- LW
- Customer
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating 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.
Redwood Customer Code
Assigned Number
To reference a line number in a transaction set
For each LX loop, there should be a single AT7, a single MS1, and a single MS2.
Example: LX*1~
Number assigned for differentiation within a transaction set
Example: 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.
AT701 –X6 and AG messages are expected every four hours, if possible, based on partners system capabilities.
Example: AT7AFNS**201909181130*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.
Redwood accepts all standard shipment status codes.
- AF
- Actual Pickup
- AG
- Estimated Delivery
- D1
- Completed Unloading at Delivery Location
- X1
- Arrived at Delivery Location
- X2
- Estimated Date and/or Time of Arrival at Consignee's Location
- X3
- Arrived at Pick-up Location
- X6
- En Route to Delivery Location
Code indicating the reason a shipment status or appointment reason was transmitted
Redwood accepts all standard reason codes default is NS.
- NS
- Normal Status
Code indicating the status of an appointment to pick-up or deliver a shipment
Redwood accepts all standard shipment appointment status codes.
- 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
Redwood accepts all standard reason codes for appointments default is NA.
- 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)
Format: HHMM
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.
Redwood requests that all status updates be provided in local time to the location of the status, so if this element is included, it should be set to LT.
- 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: MS1CHICAGOIL*USA~
Equipment or Container Owner and Type
To specify the owner, the identification number assigned by that owner, and the type of equipment
May be required for certain customers.
Example: MS2SCACEQUIP*TR~
Standard Carrier Alpha Code
Carrier’s designated SCAC identifier code.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Identifier code for the equipment.
Code identifying type of equipment used for shipment
- MS203 identifies the type for the equipment specified in MS202.
- TL
- Trailer (not otherwise specified)
- TR
- Tractor
Shipment Weight, Packaging and Quantity Data
To specify shipment details in terms of weight, and quantity of handling units
Example: AT8GL150040~
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.
Example: 40
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
Example: NM1NS1LASTNAMEFIRSTNAME~
Code identifying an organizational entity, a physical location, property or an individual
- N5
- Party Who Signed the Delivery Receipt
Code qualifying the type of entity
- NM102 qualifies NM103.
- 1
- Person
Individual last name or organizational name
Freeform individual last name or organization name.
Shipment Purchase Order Detail
To specify the purchase order details for a shipment
Example: SPO*100920041~
Identifying number for Purchase Order assigned by the orderer/purchaser
Freeform text purchase order number assigned by the purchaser.
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
Sample
L11*2*QN~
L11*12345*JB~
N1*LW*Customer Name*93*CUSTOMERCODE~
N1*SH*SHIPPER*ZZ*ABC~
N3*1234 MY STREET~
N4*CHICAGO*IL*60606*USA~
N1*CN*RECIPIENT*ZZ*DEF~
N3*1234 THEIR STREET~
N4*CHICAGO*IL*60611*USA~
LX*1~
AT7*AF*NS***20190918*1130*LT~
MS1*CHICAGO*IL*USA~
MS2*SCAC*EQUIP~
AT8*G*L*558*21~
CD3~
NM1*N5*1*Supplier*Full Name~
SPO*100920041~
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.