Hamburg Sud
/
Status Details (Ocean)
  • 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 315 Status Details (Ocean)

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Status Details (Ocean) Transaction Set (315) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary to report status or event details for selected shipments or containers. It is intended to accommodate the details for one status or event associated with many shipments or containers, as well as more than one status or event for one shipment or container.

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
    B4
    020
    Beginning Segment for Inquiry or Reply
    Max use 1
    Required
    N9
    030
    Reference Identification
    Max use 30
    Required
    Q2
    040
    Status Details (Ocean)
    Max use 1
    Optional
    R4 Loop
    SE
    090
    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

    QO
    Ocean Shipment Status Information (313, 315)
    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).
    315
    Status Details (Ocean)
    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

    B4
    020

    Beginning Segment for Inquiry or Reply

    RequiredMax use 1

    To transmit identifying numbers, dates, and other basic data relating to the transaction set

    Usage notes

    Example Syntax

    B4*VD20160526*2245HASU431617L45G1DEHAMUN0~
    B4
    VD201605262245HASU431617L45G1JACKSONVILLE, FL,
    USCI0~

    Example
    If either Equipment Initial (B4-07) or Equipment Number (B4-08) is present, then the other is required
    If either Location Identifier (B4-11) or Location Qualifier (B4-12) is present, then the other is required
    B4-03
    157
    Shipment Status Code
    Required

    Code indicating the status of a shipment

    A
    Arrived
    AA
    Pick-up Appointment Date and Time
    AD
    Delivery Appointment Date and Time
    AE
    Loaded on Vessel
    AF
    Departed Pickup Location
    AL
    Loaded on Rail
    AM
    Loaded on Truck
    AO
    Loaded on Barge
    AP
    Loaded on Feeder Vessel
    AR
    Rail Arrival at Destination Intermodal Ramp
    AV
    Container Available
    C
    Estimated To Depart Terminal Location
    CH
    Customs Hold
    CR
    Carrier Release
    CT
    Customs Released
    D
    Completed Unloading at Delivery Location
    E
    Estimated to Arrive (En Route)
    EE
    Empty Equipment Dispatched
    HR
    Carrier Un-Release
    I
    In-Gate
    IB
    U.S. Customs, In-bond Movement Authorized
    J
    Delivered to Connecting Line
    NF
    Free Time to Expire
    NT
    Notification
    OA
    Out-Gate
    P
    Rail Departed from In-Transit Location
    RD
    Return Container
    RL
    Rail Departure from Origin Intermodal Ramp
    UR
    Unloaded from a Rail Car
    UV
    Unloaded From Vessel
    VA
    Vessel Arrival

    Vessel scheduled to arrive or has arrived

    VD
    Vessel Departure

    Vessel scheduled to depart or has departed

    X
    Removed from Customer Dock or Siding
    X1
    Arrived at Delivery Location

    The carrier has arrived at the shipment delivery location

    X3
    Arrived at Pick-up Location
    B4-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • B404 is the date of last reported status of cargo.
    Usage notes

    Example: 20160526 (26th May 2016)

    B4-05
    161
    Status Time
    Required
    HHMM format

    Time (HHMM) of last reported status of cargo

    Usage notes

    Example: 2245 (10:45 pm)

    B4-07
    206
    Equipment Initial
    Optional
    Min 1Max 4

    Prefix or alphabetic part of an equipment unit's identifying number

    B4-08
    207
    Equipment Number
    Optional
    Min 1Max 10

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

    B4-09
    578
    Equipment Status Code
    Required

    Code indicating status of equipment

    E
    Empty
    L
    Load
    B4-10
    24
    Equipment Type
    Optional
    Min 4Max 4

    Code identifying equipment type

    Usage notes

    ISO Equipment Type Code according to ISO 6346:1995
    Example: 45G1

    B4-11
    310
    Location Identifier
    Optional
    Min 1Max 30

    Code which identifies a specific location

    Usage notes

    UN location code or city name.
    Example UN location code: USDAL (Dallas, TX, US)
    Example city name: JACKSONVILLE, FL, US

    B4-12
    309
    Location Qualifier
    Optional

    Code identifying type of location

    CI
    City
    UN
    United Nations Location Code (UNLOCODE)
    B4-13
    761
    Equipment Number Check Digit
    Required
    Min 1Max 1

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

    N9
    030

    Reference Identification

    RequiredMax use 30

    To transmit identifying information as specified by the Reference Identification Qualifier

    Usage notes

    Example Syntax

    N9BN6PHLSA1234~
    N9IB82564523*20160523224521*LT~

    Example
    At least one of Reference Identification (N9-02) or Free-form Description (N9-03) is required
    If Time Code (N9-06) is present, then Time (N9-05) is required
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    4F
    Carrier-assigned Shipper Number

    Customer number assigned by Hamburg Süd

    BM
    Bill of Lading Number
    BN
    Booking Number
    CO
    Customer Order Number
    CR
    Customer Reference Number
    EQ
    Equipment Number
    FN
    Forwarder's/Agent's Reference Number
    IB
    In Bond Number

    In Bond Number will be accompanied by date and time data elements

    MCI
    Motor Carrier Identification Number

    Motor Carrier Name (Truck)

    RR
    Payer's Financial Institution Transit Routing Number for Check, Draft or Wire Payments. Originating Depository Financial Institution Routing Number for ACH Transfers
    SCA
    Standard Carrier Alpha Code (SCAC)
    SI
    Shipper's Identifying Number for Shipment (SID)
    SN
    Seal Number
    WU
    Vessel
    N9-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    N9-03
    369
    Free-form Description
    Optional
    Min 1Max 45

    Free-form descriptive text

    N9-04
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    Usage notes

    Example: 20160526 (26th May 2016)

    N9-05
    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: 224526 (10:45:26 pm)

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

    • N906 reflects the time zone which the time reflects.
    LT
    Local Time
    Q2
    040

    Status Details (Ocean)

    OptionalMax use 1

    To transmit identifying information relative to identification of vessel, transportation dates, lading quantity, weight, and cube

    Usage notes

    Example Syntax

    Q29449160DE***371SLCAP SAN MARCO~

    Example
    Q2-01
    597
    Vessel Code
    Optional
    Min 1Max 8

    Code identifying vessel

    Q2-02
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    • Q202 is the code identifying the country in which the ship (vessel) is registered.
    Q2-09
    55
    Flight/Voyage Number
    Optional
    Min 2Max 10

    Identifying designator for the particular flight or voyage on which the cargo travels

    Q2-12
    897
    Vessel Code Qualifier
    Optional

    Code specifying vessel code source

    L
    Lloyd's Register of Shipping
    Q2-13
    182
    Vessel Name
    Optional
    Min 2Max 28

    Name of ship as documented in "Lloyd's Register of Ships"

    R4 Loop
    RequiredMax >1
    R4
    060

    Port or Terminal

    RequiredMax use 1

    Contractual or operational port or point relevant to the movement of the cargo

    Usage notes

    Example Syntax

    R4LUNDEHAMHamburgDE~
    R4
    ICIN/A*CSX NORTHWEST OHIO RAMP~

    Example
    If either Location Qualifier (R4-02) or Location Identifier (R4-03) is present, then the other is required
    R4-01
    115
    Port or Terminal Function Code
    Required

    Code defining function performed at the port or terminal with respect to a shipment

    5
    Activity Location (Operational)
    D
    Port of Discharge (Operational)
    E
    Place of Delivery (Contractual)
    I
    Interim Point (Operational)
    L
    Port of Loading (Operational)
    R
    Place of Receipt (Contractual)
    T
    Transshipment Port (Contractual)
    R4-02
    309
    Location Qualifier
    Optional

    Code identifying type of location

    CI
    City
    UN
    United Nations Location Code (UNLOCODE)
    R4-03
    310
    Location Identifier
    Optional
    Min 1Max 30

    Code which identifies a specific location

    Usage notes

    If location qualifier "CI" this element will be populated with "N/A".

    R4-04
    114
    Port Name
    Required
    Min 2Max 24

    Free-form name for the place at which an offshore carrier originates or terminates (by transshipment or otherwise) its actual ocean carriage of property

    R4-05
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    R4-06
    174
    Terminal Name
    Optional
    Min 2Max 30

    Free-form field for terminal name

    R4-07
    113
    Pier Number
    Optional
    Min 1Max 4

    Identifying number for the pier

    R4-08
    156
    State or Province Code
    Optional
    Min 2Max 2

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

    DTM
    070

    Actual

    OptionalMax use 15

    To specify pertinent dates and times

    Usage notes

    Example Syntax

    DTM13920160526*224529

    Example
    Variants (all may be used)
    DTMEstimated
    If Time Code (DTM-04) is present, then Time (DTM-03) is required
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time

    140
    Actual
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    Usage notes

    Example: 20160526 (26th May 2016)

    DTM-03
    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)

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

    LT
    Local Time
    DTM
    070

    Estimated

    OptionalMax use 15

    To specify pertinent dates and times

    Usage notes

    Example Syntax

    DTM13920160526*224529

    Example
    Variants (all may be used)
    DTMActual
    If Time Code (DTM-04) is present, then Time (DTM-03) is required
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time

    139
    Estimated
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    Usage notes

    Example: 20160526 (26th May 2016)

    DTM-03
    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)

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

    LT
    Local Time
    SE
    090

    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

    Customs Release

    ST*315*0001~
    B4***CR*20160520*0950**HASU*483190*L**USLGB*UN*3~
    N9*BN*6PHL89OTZT~
    N9*BM*N6HKGKP2966X~
    N9*EQ*HASU4831903~
    N9*SCA*SUDU~
    Q2*9399193********073E***L*CMA CGM LIBRA~
    R4*D*UN*USLGB*LONG BEACH CA US~
    DTM*140*20160120*143700~
    SE*10*0001~

    Gate In

    ST*315*0001~
    B4***I*20160413*1415**HASU*431617*L*45G1*GBBEL*UN*0~
    N9*BN*6BELCV1099~
    N9*BM*N6HKGKP2966X~
    N9*EQ* HASU4316170~
    N9*SCA*SUDU~
    Q2*9214202*LR*******0000***L*E.R. LONDON~
    R4*R*UN*GBBEL*BELFAST GB*GB~
    R4*L*UN*BEANR*ANTWERP BE*BE~
    DTM*139*20160424~
    R4*I*UN*GBBEL*BELFAST SEALINKTERM.*GB~
    DTM*139*20160413*1415*LT~
    R4*D*UN*MAPTM*TANGER MED MA*MA~
    DTM*139*20160501~
    R4*E*UN*TNTUN*TUNIS / RADES TN*TN~
    SE*16*0001~

    In transit rail movement (arrived at in transit location)

    ST*315*0001~
    B4***A*20160520*0950**HASU*483190*L**Colorado Springs, CO*CI*3~
    N9*BN*6PHL89OTZT~
    N9*BM*N6HKGKP2966X~
    N9*EQ*HASU4831903~
    N9*SCA*SUDU~
    N9*RR*BNSF*BNSF Railway~
    R4*I*UN*N/A*Colorado Springs, CO~
    DTM*140*20160520*095000~
    R4*D*UN*USCHI*Chicago, IL~
    DTM*139*20160529*120000~
    SE*11*0001~

    Loaded on Vessel

    ST*315*0001~
    B4***AE*20160420*1415**HASU*431617*L*45G1*GBBEL*UN*0~
    N9*BN*6BELCV1099~
    N9*BM*N6HKGKP2966X~
    N9*EQ* HASU4316170~
    N9*SCA*SUDU~
    R4*R*UN*GBBEL*BELFAST GB*GB~
    R4*L*UN*GBBEL*BELFAST GB*GB~
    DTM*139*20160420~
    R4*I*UN*GBBEL*BELFAST SEALINKTERM.*GB~
    DTM*139*20160420*1415*LT~
    R4*D*UN*MAPTM*TANGER MED MA*MA~
    DTM*139*20160501~
    R4*E*UN*TNTUN*TUNIS / RADES TN*TN~
    SE*15*0001~

    Vessel Departure

    ST*315*0001~
    B4***VD*20160421*1200**HASU*431617*L*45G1*GBBEL*UN*0~
    N9*BN*6BELCV1099~
    N9*BM*N6HKGKP2966X~
    N9*EQ*HASU4316170~
    N9*SCA*SUDU~
    R4*R*UN*GBBEL*BELFAST GB*GB~
    R4*L*UN*GBBEL*BELFAST GB*GB~
    DTM*140*20160421*1200*LT~
    R4*I*UN*GBBEL*BELFAST SEALINKTERM.*GB~
    DTM*140*20160421*1200*LT~
    R4*D*UN*MAPTM*TANGER MED MA*MA~
    DTM*139*20160501~
    R4*E*UN*TNTUN*TUNIS / RADES TN*TN~
    SE*15*0001~

    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.