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

X12 214 Transportation Carrier Shipment Status Message

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build free EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    ST
    010
    Transaction Set Header
    Max use 1
    Required
    B10
    020
    Beginning Segment for Transportation Carrier Shipment Status Message
    Max use 1
    Required
    L11
    030
    Business Instructions and Reference Number
    Max use 300
    Required
    Ship From
    SE
    610
    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 to identify the type of information in the Authorization Information

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    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 to identify the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    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
    Min 2Max 2

    Qualifier to designate 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
    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
    Min 2Max 2

    Qualifier to designate 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
    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
    I10
    Interchange Control Standards Identifier
    Required

    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
    ISA-12
    I11
    Interchange Control Version Number
    Required

    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
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Min 1Max 1

    Code sent by the sender to request an interchange acknowledgment (TA1)

    0
    No Acknowledgment Requested
    1
    Interchange Acknowledgment Requested
    ISA-15
    I14
    Usage Indicator
    Required
    Min 1Max 1

    Code to indicate 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
    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
    Min 2Max 15

    Code identifying party sending transmission; codes agreed to by trading partners

    GS-03
    124
    Application Receiver's Code
    Required
    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

    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
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

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

    004010
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

    Heading

    ST
    010

    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) 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
    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
    020

    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
    Min 1Max 30

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

    Return the value sent in B2_04 from the 204 Load Tender.

    Do not send 214's for loads not tendered via an EDI 204 Load Tender.

    B10-03
    140
    Standard Carrier Alpha Code
    Required
    Min 2Max 4

    Standard Carrier Alpha Code

    • B1003 is required when used in Transaction Set 214.
    L11
    030

    Business Instructions and Reference Number

    RequiredMax use 300

    To specify instructions in this business relationship or a reference number

    Example
    If either Reference Identification (L11-01) or Reference Identification Qualifier (L11-02) is present, then the other is required
    L11-01
    127
    Reference Identification
    Required

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

    Usage notes

    Return the value sent in Header L11_01 from the 204 Load Tender.

    L
    Multi-Stop Load
    S
    Single-Stop Shipment
    X
    Default
    L11-02
    128
    Reference Identification Qualifier
    Optional

    Code qualifying the Reference Identification

    ZZ
    Mutually Defined
    0100 Ship From
    RequiredMax >1
    Variants (all may be used)
    0100Ship To
    N1
    050

    Name

    RequiredMax use 1

    To identify a party by type of organization, name, and code

    Example
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    SF
    Ship From
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N2
    060

    Additional Name Information

    OptionalMax use 1

    To specify additional names or those longer than 35 characters in length

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N2-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N3
    070

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    080

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Optional
    Min 2Max 2

    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.
    N4-03
    116
    Postal Code
    Optional
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    0100 Ship To
    RequiredMax >1
    Variants (all may be used)
    0100Ship From
    N1
    050

    Name

    RequiredMax use 1

    To identify a party by type of organization, name, and code

    Example
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    ST
    Ship To
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N2
    060

    Additional Name Information

    OptionalMax use 1

    To specify additional names or those longer than 35 characters in length

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N2-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N3
    070

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    080

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Optional
    Min 2Max 2

    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.
    N4-03
    116
    Postal Code
    Optional
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    0200 Loop
    RequiredMax >1
    LX
    130

    Assigned Number

    RequiredMax use 1

    To reference a line number in a transaction set

    Example
    LX-01
    554
    Assigned Number
    Required
    Min 1Max 6

    Number assigned for differentiation within a transaction set

    Usage notes

    If multiple AT7 segments are sent in the 214 file, a separate LX loop is required for each.

    Example:
    LX2
    AT7
    X3NS201909172200CT
    MS1QUINCYWA
    L112QN
    LX3
    AT7
    AFNS
    201909180930CT
    MS1QUINCYWA
    L113QN
    LX4
    AT7
    X6NS201909180930CT
    MS1T18WA
    L114QN
    LX5
    AT7
    X1NS
    201909181330CT
    MS1T18WA
    L115QN
    LX6
    AT7
    CDNS*201909181340CT
    MS1
    T18WA
    L11
    6*QN

    0205 Loop
    RequiredMax >1
    AT7
    140

    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 either Shipment Status Code (AT7-01) or Shipment Status or Appointment Reason Code (AT7-02) is present, then the other is required
    Only one of Shipment Status Code (AT7-01) or Shipment Appointment Status Code (AT7-03) may be present
    If either Shipment Appointment Status Code (AT7-03) or Shipment Status or Appointment Reason Code (AT7-04) is present, then the other is required
    If Time (AT7-06) is present, then Date (AT7-05) is required
    If Time Code (AT7-07) is present, then Time (AT7-06) is required
    AT7-01
    1650
    Shipment Status Code
    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 Pick-up Location with Shipment
    CD
    Carrier Departed Delivery Location
    X1
    Arrived at Delivery Location
    X3
    Arrived at Pick-up Location
    X6
    En Route to Delivery Location

    Updates should be sent twice daily: 6:00 AM and 2:00 PM MST.

    AT7-02
    1651
    Shipment Status or Appointment Reason Code
    Optional
    Min 2Max 2

    Code indicating the reason a shipment status or appointment reason was transmitted

    AT7-03
    1652
    Shipment Appointment Status Code
    Optional

    Code indicating the status of an appointment to pick-up or deliver a shipment

    AA
    Pick-up Appointment Date and/or Time
    AB
    Delivery Appointment Date and/or Time
    AT7-04
    1651
    Shipment Status or Appointment Reason Code
    Optional
    Min 2Max 2

    Code indicating the reason a shipment status or appointment reason was transmitted

    AT7-05
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    AT7-06
    337
    Time
    Optional
    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
    Optional
    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
    143

    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

    Example
    MS1-01
    19
    City Name
    Required
    Min 2Max 30

    Free-form text for city name

    MS1-02
    156
    State or Province Code
    Required
    Min 2Max 2

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

    L11
    150

    Business Instructions and Reference Number

    RequiredMax use 10

    To specify instructions in this business relationship or a reference number

    Example
    If either Reference Identification (L11-01) or Reference Identification Qualifier (L11-02) is present, then the other is required
    L11-01
    127
    Reference Identification
    Required
    Min 1Max 30

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

    Usage notes

    Stop Sequence 001,002,003 etc.

    L11-02
    128
    Reference Identification Qualifier
    Optional

    Code qualifying the Reference Identification

    QN
    Stop Sequence Number
    SE
    610

    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
    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
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    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
    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
    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
    Min 1Max 5

    A count of the number of functional groups included in an interchange

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample 1

    ST*214*38779
    B10*4455457*5759000*SCAC
    L11*S*ZZ
    N1*SF*SHIP FROM NAME
    N3*3630 GATEWAY DRIVE
    N4*GRAND FORKS*ND*58203
    N1*ST*SHIP TO NAME
    N3*17000 SIMPLOT BLVD PO BOX 1059
    N4*CALDWELL*ID*83607
    LX*1
    AT7***AA*NA*20160111*1900*CT
    MS1*GRAND FORKS*ND
    L11*01*QN
    SE*14*38779

    Sample 2

    ST*214*39051
    B10*4455457*5759000*SCAC
    L11*S*ZZ
    N1*SF*SHIP FROM NAME
    N3*3630 GATEWAY DRIVE
    N4*GRAND FORKS*ND*58203
    N1*ST*SHIP TO NAME
    N3*17000 SIMPLOT BLVD PO BOX 1059
    N4*CALDWELL*ID*83607
    LX*1
    AT7*X3*NS***20160117*0826*CT
    MS1*GRAND FORKS*ND
    L11*01*QN
    SE*14*39051

    Sample 3

    ST*214*39014
    B10*4455457*5759000*SCAC
    L11*S*ZZ
    N1*SF*SHIP FROM NAME
    N3*3630 GATEWAY DRIVE
    N4*GRAND FORKS*ND*58203
    N1*ST*SHIP TO NAME
    N3*17000 SIMPLOT BLVD PO BOX 1059
    N4*CALDWELL*ID*83607
    LX*1
    AT7*X6*NS***20160115*1030*CT
    MS1*FARGO*ND
    L11*01*QN
    SE*14*39014

    Sample 4

    ST*214*39126
    B10*4455457*5759000*SCAC
    L11*S*ZZ
    N1*SF*SHIP FROM NAME
    N3*3630 GATEWAY DRIVE
    N4*GRAND FORKS*ND*58203
    N1*ST*SHIP TO NAME
    N3*17000 SIMPLOT BLVD PO BOX 1059
    N4*CALDWELL*ID*83607
    LX*1
    AT7*CD*NS***20160120*1121*CT
    MS1*CALDWELL*ID
    L11*02*QN
    SE*14*39126

    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.