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

X12 214 Transportation Carrier Shipment Status Message

X12 Release 5010

This X12 Transaction Set 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
  • ^ Repetition
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    https://www.stedi.com/app/guides/view/coyote-logistics/transportation-carrier-shipment-status-message/01HATB8Q4DG8G1NRCFQJVWSHGF
    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
    detail
    1000 Loop
    SE
    2100
    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

    Code identifying 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

    Code identifying 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

    Code indicating 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

    Code indicating 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
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I65
    Repetition Separator
    Required
    String (AN)
    Min 1Max 1

    Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

    ^
    Repetition Separator
    ISA-12
    I11
    Interchange Control Version Number
    Required

    Code specifying the version number of the interchange control segments

    00501
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
    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 indicating sender's request for an interchange acknowledgment

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

    Code indicating 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

    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

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    GS-05
    337
    Time
    Required
    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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480

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

    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

    005010
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

    Heading

    ST
    0100
    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

    Code uniquely identifying a Transaction Set

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

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

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

    From the B204 on the 204 tender

    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.
    Heading end

    Detail

    1000 Loop
    RequiredMax >1
    LX
    0100
    Detail > 1000 Loop > LX

    Transaction Set Line Number

    RequiredMax use 1

    To reference a line number in a transaction set

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

    Number assigned for differentiation within a transaction set

    L11
    0200
    Detail > 1000 Loop > L11

    Business Instructions and Reference Number

    RequiredMax use 10

    To specify instructions in this business relationship or a reference number

    Example
    L11-01
    127
    Reference Identification
    Required
    String (AN)
    Min 1Max 50

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

    Usage notes

    S501 from the 204 tender with a QN qualifier in the L1102 required. Not required for X6 status updates.

    L11-02
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    QN
    Stop Sequence Number
    1100 Loop
    RequiredMax 5
    AT7
    0800
    Detail > 1000 Loop > 1100 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.

    Example
    If Shipment Status or Appointment Reason Code (AT7-02) is present, then Shipment Status Indicator (AT7-01) is required
    If Shipment Status or Appointment Reason Code (AT7-04) is present, then Shipment Appointment Status Code (AT7-03) is required
    Only one of Shipment Status Indicator (AT7-01) or Shipment Appointment Status Code (AT7-03) may be present
    AT7-01
    1650
    Shipment Status Indicator
    Optional

    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.
    AF
    Carrier Departed Pickup Location with Shipment
    D1
    Completed Unloading at Delivery Location
    X1
    Arrived at Delivery Location
    X3
    Arrived at Pickup Location
    X6
    En Route to Delivery Location
    AT7-02
    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

    Default to NS otherwise use Standard ASC X12 Codes.

    AT7-03
    1652
    Shipment Appointment Status Code
    Optional

    Code indicating the status of an appointment to pickup or deliver a shipment

    AA
    Pickup Appointment Date and/or Time
    AB
    Delivery Appointment Date and/or Time
    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

    Default to Blank otherwise use Standard ASC X12 Codes.

    AT7-05
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    AT7-06
    337
    Time
    Required
    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)

    AT7-07
    623
    Time Code
    Required
    Identifier (ID)
    Min 2Max 2

    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.
    MS1
    0900
    Detail > 1000 Loop > 1100 Loop > MS1

    Equipment, Shipment, or Real Property Location

    RequiredMax use 1

    To specify the location of a piece of equipment, a shipment, or real property in terms of city and state or longitude and latitude or postal code

    Example
    Only one of City Name (MS1-01) or Longitude Code (MS1-04) may be present
    If City Name (MS1-01) is present, then at least one of State or Province Code (MS1-02) or Country Code (MS1-03) is required
    If Country Code (MS1-03) is present, then City Name (MS1-01) is required
    If either Longitude Code (MS1-04) or Latitude Code (MS1-05) is present, then the other is required
    If Direction Identifier Code (MS1-06) is present, then Longitude Code (MS1-04) is required
    If Direction Identifier Code (MS1-07) is present, then Latitude Code (MS1-05) is required
    MS1-01
    19
    City Name
    Required
    String (AN)
    Min 2Max 30

    Free-form text for city name

    MS1-02
    156
    State or Province Code
    Required
    Identifier (ID)
    Min 2Max 2

    Code (Standard State/Province) as defined by appropriate government agency

    MS1-03
    26
    Country Code
    Optional
    Identifier (ID)
    Min 2Max 3

    Code identifying the country

    MS1-04
    1654
    Longitude Code
    Optional
    Identifier (ID)
    Min 7Max 7

    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.
    MS1-05
    1655
    Latitude Code
    Optional
    Identifier (ID)
    Min 7Max 7

    Code indicating the latitude in degrees (3 positions), minutes (2 positions), seconds (2 positions)

    • MS105 is the latitude expressed in Degrees, Minutes, and Seconds.
    MS1-06
    1280
    Direction Identifier Code
    Optional
    Identifier (ID)
    Min 1Max 1

    Code identifying geographic direction

    • MS106 may only be 'E' or 'W'.
    Usage notes

    Standard ASC X12 Codes.

    MS1-07
    1280
    Direction Identifier Code
    Optional
    Identifier (ID)
    Min 1Max 1

    Code identifying geographic direction

    • MS107 may only be 'N' or 'S'.
    Usage notes

    Standard ASC X12 Codes.

    MS2
    1000
    Detail > 1000 Loop > 1100 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

    Usage notes

    Not Mandatory on Shipment Appointments

    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 15

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

    1100 Loop end
    1000 Loop end
    SE
    2100
    Detail > 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

    Detail 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

    Sample for Coyote 214

    ISA*00* *00* *ZZ*TEST *02*CLLQ *190406*1214*U*00501*000038399*0*P*>~
    GS*QM*TEST*CLLQ*20190406*1214*38399*X*005010~
    ST*214*0001~
    B10*02774648*400473*TEST~
    LX*1~
    L11*2*QN~
    AT7*X1*NS***20190406*091000*LT~
    MS1*ANYWHERE*CA~
    MS2*CLLQ*55668~
    SE*8*0001~
    GE*1*38399~
    IEA*1*000038399~

    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.