972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Transportation

EDI 322 Terminal Operations and Intermodal Ramp Activity

The X12 document terminals, port authorities and intermodal ramps use to report activity such as ingates and outgates to the parties to a shipment.

Sent by
Terminal operator, port authority or intermodal ramp
Received by
Carrier, shipper, forwarder or other authorized party
Standard
ANSI ASC X12

What is an EDI 322?

The EDI 322 Terminal Operations and Intermodal Ramp Activity is the ANSI X12 transaction set a terminal operation, port authority or intermodal ramp uses to communicate terminal activity to authorized parties to a shipment. Typical activities are ingates and outgates of containers and equipment, along with loads, discharges and other terminal events.

For carriers and logistics providers, 322 events show when a container physically enters or leaves a terminal, which drives equipment tracking, free-time calculations and the planning of the next move.

How the EDI 322 worksDiagram of the EDI 322 Terminal Operations and Intermodal Ramp Activity. Terminal operator, port authority or intermodal ramp sends it to carrier, shipper, forwarder or other authorized party. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: Q5 (Status Details) and the required N7 loop with N7 (Equipment Details) and the required R4 loop with R4 (Port or Terminal). 2 optional loops are listed by their first segment.How the EDI 322 worksTerminal Operations and Intermodal Ramp Activity: who sends it, where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 322SENDERTerminal operator, portauthority or intermodalrampRECEIVERCarrier, shipper,forwarder or otherauthorized party997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SOGS … GETransaction set 322ST … SEHEADINGQ5Status DetailsRequired loop N7 · repeats up to 1,000N7Equipment DetailsRequired loop R4 · repeats up to 20R4Port or Terminal+ 2 optional loops, starting with:N1L0Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 322. Your trading partner's implementation guide adds its own requirements.
How the EDI 322 worksDiagram of the EDI 322 Terminal Operations and Intermodal Ramp Activity. Terminal operator, port authority or intermodal ramp sends it to carrier, shipper, forwarder or other authorized party. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: Q5 (Status Details) and the required N7 loop with N7 (Equipment Details) and the required R4 loop with R4 (Port or Terminal). 2 optional loops are listed by their first segment.How the EDI 322 worksTerminal Operations and Intermodal RampActivity: who sends it, where it fits and whatthe standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 322SENDERTerminaloperator, portauthority orintermodal rampRECEIVERCarrier, shipper,forwarder orother authorizedparty997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code SO (GS … GE)Transaction set 322 (ST … SE)HEADINGQ5Status DetailsRequired loop N7 · repeats up to1,000N7Equipment DetailsRequired loop R4 · repeats upto 20R4Port or Terminal+ 2 optional loops, starting with:N1L0Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 322. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 322, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 322 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Reporting container ingate and outgate at ports and ramps
  • Tracking equipment through intermodal terminals
  • Calculating free time and storage charges

Where it fits in the document flow

This document 322 Terminal Operations and Intermodal Ramp Activity
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 322 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • Q5
  • N7
  • R4
  • N1
  • L0
  • LH1
  • SE

Practical example

The 322 in practice

A drayage company picks up an import container at a port terminal. When the truck exits, the terminal sends a 322 outgate event with the container number, time and equipment details. The steamship line and the importer's logistics provider record the outgate, stopping the free-time clock and updating the container's location.

Implementation

Implementation considerations for the 322

  • Identify containers and equipment by their standard numbers, as every party matches on them.
  • Combine terminal events with carrier status messages for a complete picture.
  • Use event times, not receipt times, for free-time and storage calculations.

How ECOM helps

Automate the 322 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Industry

3PL and Warehousing

Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 322?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us