X12 322 Terminal Operations and Intermodal Ramp Activity
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
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)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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
Status Details
To specify the status of the shipment in terms of dates, time, reference numbers, and location
Example Syntax
Q5I20100802091200LT**SALT LAKE CITY~
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
Date expressed as CCYYMMDD
- Q502 is the date of the status reported in Q501.
Example: 20160526 (26th May 2016)
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.
Example: 224500 (10:45:00 pm)
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
Code (Standard State/Province) as defined by appropriate government agency
Equipment Details
To identify the equipment
Example Syntax
N7HASU43161743459G*CNBNSF*L0***451GBNSF~
Prefix or alphabetic part of an equipment unit's identifying number
- N701 is mandatory for rail transactions.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
This element should contain the container number without the check digit!
Please report check digit in N718!
Code defining the type of weight
- CE
- Certified Weight of Cargo
- E
- Estimated Net Weight
- G
- Gross Weight
- N
- Actual Net Weight
Code identifying type of equipment used for shipment
- CC
- Container resting on a Chassis
- CN
- Container
- CZ
- Refrigerated Container
Standard Carrier Alpha Code
- N712 is the owner of the equipment.
Number which designates the check digit applied to a piece of equipment
Code specifying extent of transportation service requested
Code identifying equipment type
ISO Equipment Type Code according to ISO 6346:1995 (preferred) or ISO 6346:1984
Estimated Arrival Date
To specify pertinent dates and times
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).
Code specifying type of date or time, or both date and time
- 371
- Estimated Arrival Date
Estimated Arrival Date at destination rail ramp
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)
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
Estimated Delivery
To specify pertinent dates and times
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).
Code specifying type of date or time, or both date and time
- 017
- Estimated Delivery
When the equipment will be available for pickup
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)
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
Original ETA
To specify pertinent dates and times
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).
Code specifying type of date or time, or both date and time
- 830
- Schedule
Original ETA
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)
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
Seal Numbers
To record seal numbers used and the organization that applied the seals
Example Syntax
M7SN1234567SN1234568~
Equipment Identification
To identify equipment and the commodity being carried
Example Syntax
W2HASU431617CCL*****0~
Prefix or alphabetic part of an equipment unit's identifying number
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
This element should contain the container number including the check
digit!
Code describing a commodity or group of commodities
- Commodity code (W203) is STCC.
Code identifying type of equipment used for shipment
- CC
- Container resting on a Chassis
- CN
- Container
- CZ
- Refrigerated Container
Port or Terminal
Contractual or operational port or point relevant to the movement of the cargo
Example Syntax
R45UNUSCHIBNSF CHICAGO RAMP (CICERO)US**IL~
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)
Code identifying type of location
- CI
- City
- UN
- United Nations Location Code (UNLOCODE)
Free-form name for the place at which an offshore carrier originates or terminates (by transshipment or otherwise) its actual ocean carriage of property
Name
To identify a party by type of organization, name, and code
Example Syntax
N1CNABCCONSIGNEE~
N1RRBNSF RailwayZZBNSF~
Code identifying an organizational entity, a physical location, property or an individual
- CN
- Consignee
- MC
- Motor Carrier
- RR
- Railroad
- SH
- Shipper
Code designating the system/method of code structure used for Identification Code (67)
- ZZ
- Mutually Defined
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.
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Example Syntax
N9BN6PHLSA1234~
N9BMA5GEMEN1976X~
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
- BN
- Booking Number
- P8
- Pickup Reference Number
- WY
- Waybill Number
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Free time to expire on 25th June 2016
GS*SO*SENDERGS*RECEIVERGS*20231117*005252*000000001*X*004010~
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~
GE*1*000000001~
IEA*1*000000001~
Loaded on Rail
GS*SO*SENDERGS*RECEIVERGS*20231117*005312*000000001*X*004010~
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*14*0001~
GE*1*000000001~
IEA*1*000000001~
Out-Gate
GS*SO*SENDERGS*RECEIVERGS*20231117*005328*000000001*X*004010~
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~
GE*1*000000001~
IEA*1*000000001~
Rail Arrival at Intermediate Rail Location
GS*SO*SENDERGS*RECEIVERGS*20231117*005342*000000001*X*004010~
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~
GE*1*000000001~
IEA*1*000000001~
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.