Hamburg Sud
/
Transportation Carrier Shipment Status Message
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Hamburg Sud. Contact Hamburg Sud for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Hamburg Sud 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 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
    Optional
    0200 Loop
    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

    Usage notes

    Please note that the Transport / Job Order (e.g. 7PHLSA1234) has to be
    reported in the B1001 element and not in the B1002 element.

    Example Syntax:

    B107PHLSA12340123465*SCAC~

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

    • B1001 is the carrier assigned reference number.
    • B1001 is the carrier's PRO (invoice number) that identifies the shipment.
    Usage notes

    Hamburg Süd Transport / Job Order Number

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

    Job order of the truck vendor

    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

    OptionalMax use 300

    To specify instructions in this business relationship or a reference number

    Usage notes

    Example Syntax:

    L116PHLSA1234BN~
    L11SUDU7N3400812147BM~

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

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

    L11-02
    128
    Reference Identification Qualifier
    Optional

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number
    BN
    Booking Number
    MCI
    Motor Carrier Identification Number

    Only to be used in case trucking company has no SCAC code assigned. Hamburg Süd will inform the trucker, which ID to use.

    SN
    Seal Number
    0200 Loop
    RequiredMax >1
    LX
    130

    Assigned Number

    RequiredMax use 1

    To reference a line number in a transaction set

    Usage notes

    Example Syntax:

    LX*1~

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

    Number assigned for differentiation within a transaction set

    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.

    Usage notes

    The appointment time event codes "AA" and "AB" should be reported in AT703 element in contrast to the other event codes that have to be reported in the AT701 element.

    Example Syntax:
    Appointment: AT7AA201705040800LT~
    Regular event: AT7
    CDNS*201701281700*LT~

    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 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.
    AA
    Pick-up Appointment Date and/or Time (Appointment Time for Export)
    AB
    Delivery Appointment Date and/or Time (Appointment Time for Import)
    AF
    Carrier Departed Pick-up Location with Shipment
    CA
    Shipment Cancelled
    CD
    Carrier Departed Delivery Location
    CP
    Completed Loading at Pick-up Location
    D1
    Completed Unloading at Delivery Location
    X1
    Arrived at Delivery Location
    X3
    Arrived at Pick-up Location
    AT7-02
    1651
    Shipment Status or Appointment Reason Code
    Optional

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

    NS
    Normal Status
    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

    Appointment Time for Export

    AB
    Delivery Appointment Date and/or Time

    Appointment Time for Import

    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

    Usage notes

    Example: 20160526 (26th May 2016)

    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)

    Usage notes

    Example: 224529 (10:45:29 pm)

    AT7-07
    623
    Time Code
    Optional

    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.
    LT
    Local Time
    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

    Usage notes

    Example Syntax:

    MS1DETROITMI*US~

    Example
    If State or Province Code (MS1-02) is present, then City Name (MS1-01) is required
    MS1-01
    19
    City Name
    Required
    Min 2Max 30

    Free-form text for city name

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

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

    MS1-03
    26
    Country Code
    Required
    Min 2Max 3

    Code identifying the country

    Usage notes

    Country code according to ISO 3166-1.
    The ISO 3166-1 alpha-2 codes are two-letter country codes defined in ISO 3166-1, part of the ISO 3166 standard published by the International Organization for Standardization (ISO), to represent countries, dependent territories, and special areas of geographical interest.

    MS2
    146

    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

    Example Syntax:

    MS2SUDU852938**7~

    Example
    MS2-01
    140
    Standard Carrier Alpha Code
    Required
    Min 2Max 4

    Standard Carrier Alpha Code

    MS2-02
    207
    Equipment Number
    Required
    Min 1Max 10

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

    MS2-04
    761
    Equipment Number Check Digit
    Required
    Min 1Max 1

    Number which designates the check digit applied to a piece of equipment

    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

    Appointment time (Import)

    ST*214*0001~
    B10*6PHL00JZEN*01234567*ABCD~
    L11*SUDU15MANEN211AX*BM~
    LX*1~
    AT7***AB**20170202*1200*LT~
    MS1*SENECA*SC*US~
    MS2*SUDU*545487**5~
    SE*8*0001~

    Arrived at customer’s premises (Export)

    ST*214*0002~
    B10*6JAXIA0770*01234567*ABCD~
    L11*6JAXIA0770*BN~
    LX*1~
    AT7*X3*NS***20170125*0720*LT~
    MS1*CHICAGO*IL*US~
    MS2*HASU*431020**6~
    SE*8*0002~

    Arrived at customer’s premises (Import)

    ST*214*0002~
    B10*6PHL00JZEN*01234567*ABCD~
    L11*SUDU15MANEN211AX*BM~
    LX*1~
    AT7*X1*NS***20170202*1425*LT~
    MS1*SENECA*SC*US~
    MS2*SUDU*545487**5~
    SE*8*0002~

    Export Appointment time (container known)

    ST*214*0001~
    B10*6JAXIA0770*0123456*ABCD~
    L11*6JAXIA0770*BN~
    LX*1~
    AT7***AA**20170512*0935*LT~
    MS1*CHICAGO*IL*US~
    MS2*HASU*431020**6~
    SE*8*0001~

    Export Appointment time (container unknown)

    ST*214*0001~
    B10*6JAXIA0770*0123456*ABCD~
    L11*6JAXIA0770*BN~
    LX*1~
    AT7***AA**20170512*0935*LT~
    MS1*CHICAGO*IL*US~
    SE*7*0001~

    Left customer’s premises (Export)

    ST*214*0004~
    B10*6JAXIA0770*01234567*ABCD~
    L11*6JAXIA0770*BN~
    LX*1~
    AT7*AF*NS***20170125*1510*LT~
    MS1*CHICAGO*IL*US~
    MS2*HASU*431020**6~
    SE*8*0004~

    Left customer’s premises (Import)

    ST*214*0004~
    B10*6PHL00JZEN*01234567*ABCD~
    L11*SUDU15MANEN211AX*BM~
    LX*1~
    AT7*CD*NS***20170204*0715*LT~
    MS1*SENECA*SC*US~
    MS2*SUDU*545487**5~
    SE*8*0004~

    Loading of container completed (Export)

    ST*214*0003~
    B10*6JAXIA0770*01234567*ABCD~
    L11*6JAXIA0770*BN~
    LX*1~
    AT7*CP*NS***20170125*1500*LT~
    MS1*CHICAGO*IL*US~
    MS2*HASU*431020**6~
    SE*8*0003~

    Transport / Shipment cancelled

    ST*214*0004~
    B10*6PHL00JZEN*01234567*ABCD~
    L11*SUDU15MANEN211AX*BM~
    LX*1~
    AT7*CA*NS***20170204*0715*LT~
    MS1*SENECA*SC*US~
    MS2*SUDU*545487**5~
    SE*8*0004~

    Unloading completed (Import)

    ST*214*0003~
    B10*6PHL00JZEN*01234567*ABCD~
    L11*SUDU15MANEN211AX*BM~
    LX*1~
    AT7*D1*NS***20170203*1200*LT~
    MS1*SENECA*SC*US~
    MS2*SUDU*545487**5~
    SE*8*0003~

    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.