Hamburg Sud
/
Terminal Operations and Intermodal Ramp Activity
  • 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 322 Terminal Operations and Intermodal Ramp Activity

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Terminal Operations and Intermodal Ramp Activity Transaction Set (322) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary for a terminal operation, port authority or intermodal ramp to communicate terminal and intermodal ramp activities (e.g., "ingates" and "outgates") to authorized parties to a shipment.

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
    Q5
    016
    Status Details
    Max use 1
    Required
    N7 Loop
    N7
    020
    Equipment Details
    Max use 1
    Required
    DTM
    040
    Estimated Arrival Date
    Max use 2
    Optional
    DTM
    040
    Estimated Delivery
    Max use 2
    Optional
    DTM
    040
    Original ETA
    Max use 2
    Optional
    M7
    050
    Seal Numbers
    Max use 5
    Optional
    W2
    070
    Equipment Identification
    Max use 1
    Optional
    N1 Loop
    N9
    170
    Reference Identification
    Max use 10
    Optional
    SE
    220
    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

    SO
    Ocean Shipment Information (304, 306, 309, 311, 317, 319, 321, 322, 323, 324, 325, 350, 352, 353, 354, 355, 356, 357, 358, 361)
    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).
    322
    Terminal Operations and Intermodal Ramp Activity
    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

    Q5
    016

    Status Details

    RequiredMax use 1

    To specify the status of the shipment in terms of dates, time, reference numbers, and location

    Usage notes

    Example Syntax

    Q5I20100802091200LT**SALT LAKE CITY~

    Example
    If State or Province Code (Q5-07) is present, then City Name (Q5-06) is required
    Q5-01
    157
    Shipment Status Code
    Required

    Code indicating the status of a shipment

    A
    Arrived
    AL
    Loaded on Rail
    AR
    Rail Arrival at Destination Intermodal Ramp
    I
    In-Gate
    J
    Delivered to Connecting Line
    NF
    Free Time to Expire
    NT
    Notification
    OA
    Out-Gate
    P
    Departed Terminal Location
    R
    Received from Prior Carrier
    RL
    Rail Departure from Origin Intermodal Ramp
    UR
    Unloaded from a Rail Car
    Q5-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • Q502 is the date of the status reported in Q501.
    Usage notes

    Example: 20160526 (26th May 2016)

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

    • Q503 is the time of the status reported in Q501.
    Usage notes

    Example: 224500 (10:45:00 pm)

    Q5-04
    623
    Time Code
    Required

    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
    Q5-06
    19
    City Name
    Required
    Min 2Max 30

    Free-form text for city name

    Q5-07
    156
    State or Province Code
    Optional
    Min 2Max 2

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

    Q5-08
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    N7 Loop
    RequiredMax >1
    N7
    020

    Equipment Details

    RequiredMax use 1

    To identify the equipment

    Usage notes

    Example Syntax

    N7HASU43161743459G*CNBNSF*L0***451GBNSF~

    Example
    If either Weight (N7-03) or Weight Qualifier (N7-04) is present, then the other is required
    N7-01
    206
    Equipment Initial
    Required
    Min 1Max 4

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

    • N701 is mandatory for rail transactions.
    N7-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)

    Usage notes

    This element should contain the container number without the check digit!
    Please report check digit in N718!

    N7-03
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    N7-04
    187
    Weight Qualifier
    Optional

    Code defining the type of weight

    CE
    Certified Weight of Cargo
    E
    Estimated Net Weight
    G
    Gross Weight
    N
    Actual Net Weight
    N7-11
    40
    Equipment Description Code
    Optional

    Code identifying type of equipment used for shipment

    CC
    Container resting on a Chassis
    CN
    Container
    CZ
    Refrigerated Container
    N7-12
    140
    Standard Carrier Alpha Code
    Optional
    Min 2Max 4

    Standard Carrier Alpha Code

    • N712 is the owner of the equipment.
    N7-17
    188
    Weight Unit Code
    Optional

    Code specifying the weight unit

    K
    Kilograms
    L
    Pounds
    N7-18
    761
    Equipment Number Check Digit
    Optional
    Min 1Max 1

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

    N7-19
    56
    Type of Service Code
    Optional
    Min 2Max 2

    Code specifying extent of transportation service requested

    N7-22
    24
    Equipment Type
    Optional
    Min 4Max 4

    Code identifying equipment type

    Usage notes

    ISO Equipment Type Code according to ISO 6346:1995 (preferred) or ISO 6346:1984

    N7-23
    140
    Standard Carrier Alpha Code
    Optional
    Min 2Max 4

    Standard Carrier Alpha Code

    • N723 is the operator or carrier of the rights of the equipment.
    DTM
    040

    Estimated Arrival Date

    OptionalMax use 2

    To specify pertinent dates and times

    Usage notes

    Example Syntax

    DTM37120160702091200LT~

    Hamburg Süd expects up to 3 DTMs to receive ETA information. The ETA date and time are linked to the destination location (R4*7).

    Example
    Variants (all may be used)
    DTMEstimated DeliveryDTMOriginal ETA
    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

    371
    Estimated Arrival Date

    Estimated Arrival Date at destination rail ramp

    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

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

    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
    040

    Estimated Delivery

    OptionalMax use 2

    To specify pertinent dates and times

    Usage notes

    Example Syntax

    DTM37120160702091200LT~

    Hamburg Süd expects up to 3 DTMs to receive ETA information. The ETA date and time are linked to the destination location (R4*7).

    Example
    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

    017
    Estimated Delivery

    When the equipment will be available for pickup

    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

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

    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
    040

    Original ETA

    OptionalMax use 2

    To specify pertinent dates and times

    Usage notes

    Example Syntax

    DTM37120160702091200LT~

    Hamburg Süd expects up to 3 DTMs to receive ETA information. The ETA date and time are linked to the destination location (R4*7).

    Example
    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

    830
    Schedule

    Original ETA

    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

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

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

    Seal Numbers

    OptionalMax use 5

    To record seal numbers used and the organization that applied the seals

    Usage notes

    Example Syntax

    M7SN1234567SN1234568~

    Example
    M7-01
    225
    Seal Number
    Required
    Min 2Max 15

    Unique number on seal used to close a shipment

    M7-02
    225
    Seal Number
    Optional
    Min 2Max 15

    Unique number on seal used to close a shipment

    M7-03
    225
    Seal Number
    Optional
    Min 2Max 15

    Unique number on seal used to close a shipment

    M7-04
    225
    Seal Number
    Optional
    Min 2Max 15

    Unique number on seal used to close a shipment

    M7-05
    98
    Entity Identifier Code
    Optional
    Min 2Max 3

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

    • M705 indicates the name of the organization which applied the seal(s).
    W2
    070

    Equipment Identification

    OptionalMax use 1

    To identify equipment and the commodity being carried

    Usage notes

    Example Syntax

    W2HASU431617CCL*****0~

    Example
    W2-01
    206
    Equipment Initial
    Required
    Min 1Max 4

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

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

    Usage notes

    This element should contain the container number including the check
    digit!

    W2-03
    22
    Commodity Code
    Optional
    Min 1Max 30

    Code describing a commodity or group of commodities

    • Commodity code (W203) is STCC.
    W2-04
    40
    Equipment Description Code
    Required

    Code identifying type of equipment used for shipment

    CC
    Container resting on a Chassis
    CN
    Container
    CZ
    Refrigerated Container
    W2-05
    578
    Equipment Status Code
    Required

    Code indicating status of equipment

    E
    Empty
    L
    Load
    W2-13
    761
    Equipment Number Check Digit
    Optional
    Min 1Max 1

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

    R4 Loop
    RequiredMax >1
    R4
    120

    Port or Terminal

    RequiredMax use 1

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

    Usage notes

    Example Syntax

    R45UNUSCHIBNSF CHICAGO RAMP (CICERO)US**IL~

    Example
    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)
    6
    Origin Rail Intermodal Terminal
    7
    Destination Rail Intermodal Terminal
    D
    Port of Discharge (Operational)
    L
    Port of Loading (Operational)
    R4-02
    309
    Location Qualifier
    Required

    Code identifying type of location

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

    Code which identifies a specific location

    R4-04
    114
    Port Name
    Optional
    Min 2Max 30

    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-08
    156
    State or Province Code
    Optional
    Min 2Max 2

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

    N1 Loop
    OptionalMax >1
    N1
    150

    Name

    RequiredMax use 1

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

    Usage notes

    Example Syntax

    N1CNABCCONSIGNEE~
    N1RRBNSF RailwayZZBNSF~

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    CN
    Consignee
    MC
    Motor Carrier
    RR
    Railroad
    SH
    Shipper
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

    Code designating the system/method of code structure used for Identification Code (67)

    ZZ
    Mutually Defined
    N1-04
    67
    Identification Code
    Optional
    Min 2Max 80

    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.
    N9
    170

    Reference Identification

    OptionalMax use 10

    To transmit identifying information as specified by the Reference Identification Qualifier

    Usage notes

    Example Syntax

    N9BN6PHLSA1234~
    N9BMA5GEMEN1976X~

    Example
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number
    BN
    Booking Number
    P8
    Pickup Reference Number
    WY
    Waybill Number
    N9-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    SE
    220

    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

    Free time to expire on 25th June 2016

    ST*322*0001~
    Q5*NF*20160625*120000*LT**BNSF CHICAGO (LOGISTICS PARK)*IL*US~
    N7*HASU*431617*43459*G*******CN*BNSF*****L*0****451G*BNSF~
    M7*SN1234567*SN1234568~
    W2*HASU*431617**CC*L********0~
    R4*5*UN*USCHI*BNSF CHICAGO (LOGISTICS PARK)*US***IL~
    R4*6*UN*USLGB*LONG BEACH*US***CA~
    R4*7*UN*USCHI*BNSF CHICAGO RAMP (CICERO)*US***IL~
    N1*RR*BNSF Railway*ZZ*BNSF~
    N9*BN*6PHLSA1234~
    N9*BM*A5GEMEN1976X~
    SE*12*0001~

    Loaded on Rail

    ST*322*0001~
    Q5*AL*20160524*073000*LT**LONG BEACH*CA*US~
    N7*HASU*431617*43459*G*******CN*BNSF*****L*0****451G*BNSF~
    DTM*371*20160528*160000*LT~
    DTM*830*20160528*160000*LT~
    M7*SN1234567*SN1234568~
    W2*HASU*431617**CC*L********0~
    R4*5*UN*USLGB*LONG BEACH*US***CA~
    R4*6*UN*USLGB*LONG BEACH*US***CA~
    R4*7*UN*USCHI*BNSF CHICAGO RAMP (CICERO)*US***IL~
    N1*RR*BNSF Railway*ZZ*BNSF~
    N9*BN*6PHLSA1234~
    N9*BM*A5GEMEN1976X~
    SE*12*0001~

    Out-Gate

    ST*322*0001~
    Q5*OA*20160610*104520*LT**BNSF CHICAGO (LOGISTICS PARK)*IL*US~
    N7*HASU*431617*43459*G*******CN*BNSF*****L*0****451G*BNSF~
    M7*SN1234567*SN1234568~
    W2*HASU*431617**CC*L********0~
    R4*5*UN*USCHI*BNSF CHICAGO (LOGISTICS PARK)*US***IL~
    R4*6*UN*USLGB*LONG BEACH*US***CA~
    R4*7*UN*USCHI*BNSF CHICAGO RAMP (CICERO)*US***IL~
    N1*RR*BNSF Railway*ZZ*BNSF~
    N9*BN*6PHLSA1234~
    N9*BM*A5GEMEN1976X~
    SE*12*0001~

    Rail Arrival at Intermediate Rail Location

    ST*322*0001~
    Q5*A*20160526*214520*LT**SAINT PAUL*MN*US~
    N7*HASU*431617*43459*G*******CN*BNSF*****L*0****451G*BNSF~
    DTM*371*20160528*091200*LT~
    DTM*017*20160529*080000*LT~
    DTM*830*20160528*160000*LT~
    M7*SN1234567*SN1234568~
    W2*HASU*431617**CC*L********0~
    R4*5*UN*USSTP*SAINT PAUL*US***MN~
    R4*6*UN*USLGB*LONG BEACH*US***CA~
    R4*7*UN*USCHI*BNSF CHICAGO RAMP (CICERO)*US***IL~
    N1*RR*BNSF Railway*ZZ*BNSF~
    N9*BN*6PHLSA1234~
    N9*BM*A5GEMEN1976X~
    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.