ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 322 — Terminal Operations and Intermodal Ramp Activity

The 322 documents the activity of an ocean terminal or intermodal ramp: equipment ingate / outgate events, container movements, unit status.

Purpose

The 322 is the operational visibility instrument for container terminals and intermodal rail ramps: it carries each physical movement of a unit (TEU, FEU, chassis) — gate-in of a truck, gate-out, hostling on the yard, lift on a train or a vessel. Issued by the terminal to the carriers (ocean carrier, rail carrier, motor carrier) tracking their equipment.

It complements the 324 (Advance Ship Notice on the ocean side) and the 404 (Rail Carrier Shipment Information on the rail side): the 322 narrates the daily life of the terminal, not the transport contract. Acknowledged by 997, it feeds operational dashboards and occupancy / demurrage billing.

Envelope structure

The 322 travels within the three X12 envelope levels (ISA/IEA, GS/GE with functional group IO, and ST/SE). Didactic example in release 004010:

x12 example-322.x12 
ISA*00*          *00*          *ZZ*PORTTERMINAL  *ZZ*OCEANCARRIER  *260514*0830*U*00401*000000322*0*P*>~
GS*IO*PORTTERMINAL*OCEANCARRIER*20260514*0830*1*X*004010~
ST*322*0001~
ZC1*FUEL*L*USD~
Q5*OA*20260514*0825*LT~
N7*MSCU*4501230*22G1~
M7*MSCU SEAL 887766*ACME LINE SEAL~
N9*BM*BL-2026-PORT-998~
N9*RU*VOYAGE-EAST-005~
Q5*OD*20260514*0832*LT~
N7*MSCU*7782314*22G1~
M7*MSCU SEAL 990011~
N9*BM*BL-2026-PORT-999~
SE*12*0001~
GE*1*1~
IEA*1*000000322~

Common segments

  • Header — ST, ZC1 (Beginning Segment for Data Correction), Q5 (Status Details).
  • Movement — repeated Q5 (date / time / status code: OA = Outgate Available, OD = Outgate Date), N7 (Equipment Details: container number, ISO size-type).
  • Seals / references — M7 (Seal Numbers), N9 (Reference: BL, voyage, train, chassis).
  • Reporting party — N1 when the terminal sub-contracts to a third-party operator.
  • Summary — SE.

Common pitfalls

  • Proprietary Q5 codes: each terminal and each ocean alliance (2M, THE Alliance, Ocean Alliance) keeps its own event code list; without a contractual alignment, the Q5 values are unusable.
  • Time zones: Q5 carries terminal-local time; without explicit UTC conversion at the hub, the 322 / 324 activity curves drift and demurrage calculations diverge.
  • Volume: a large terminal produces several thousand 322 per day; do not design the AS2 channel without batching or archival, otherwise the partner saturates.

Documentation

The code 322 and the name Terminal Operations and Intermodal Ramp Activity are public and listed on x12.org/products/transaction-sets. The complete structure of loops, qualifiers and code lists is distributed by DISA via the proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.