X12 transaction code
EDI 322 Terminal Operations and Intermodal Ramp Activity (X12 322)
EDI 322 is the X12 Terminal Operations and Intermodal Ramp Activity transaction set, used when a terminal or intermodal ramp records equipment activity. A terminal operator, port authority, or intermodal ramp sends the 322 to authorized parties to the shipment, such as ocean carriers, railroads, motor carriers, and shippers.
- Standard
- X12
- Code
- 322
- Partner references
- 6
At a glance
EDI 322 at a glance
What the 322 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 322 Terminal Operations and Intermodal Ramp Activity |
|---|---|
| Business record | Terminal equipment event |
| Who sends it to whom | A terminal operator, port authority, or intermodal ramp sends the 322 to authorized parties to the shipment, such as ocean carriers, railroads, motor carriers, and shippers. |
| When it is sent | A container or trailer passes an ingate or outgate at a marine terminal or intermodal rail ramp and the gate system records the movement. |
| Match on | Container or rail equipment, event time and terminal |
| Partner references | 6 trading partners in this directory |
| Related documents | X12 404 Rail Carrier Shipment Information, X12 417 Rail Carrier Waybill Interchange |
Key segments in an EDI 322
The business segments that appear in at least half of the 6 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| Q5 | Status Details | To specify the status of the shipment in terms of dates, time, reference numbers, and location. | 6 of 6 |
| N7 | Equipment Details | To identify the equipment. | 6 of 6 |
| M7 | Seal Numbers | To record seal numbers used and the organization that applied the seals. | 6 of 6 |
| W2 | Equipment Identification | To identify equipment and the commodity being carried. | 6 of 6 |
| NA | Cross-Reference Equipment | To cross-reference additional equipment to a primary piece of equipment. | 6 of 6 |
| R4 | Port or Terminal | Contractual or operational port or point relevant to the movement of the cargo. | 6 of 6 |
| N1 | Name | To identify a party by type of organization, name, and code. | 6 of 6 |
| N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 6 of 6 |
| DTM | Date/Time Reference | To specify pertinent dates and times. | 5 of 6 |
| H3 | Special Handling Instructions | To specify special handling instructions in coded or free-form format. | 4 of 6 |
Stacksync connects EDI documents such as the X12 322 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 322 mapping and validation
X12 322 Terminal Operations and Intermodal Ramp Activity is used when a terminal or intermodal ramp records equipment activity. Preserve container or rail equipment, event time and terminal so the terminal equipment event in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | terminal equipment event container or rail equipment, event time and terminal |
|
| Update the receiving system | Processing the terminal equipment event ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the terminal equipment event Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 404 Rail Carrier Shipment Information
rail shipment: rail movement instructions are ready for carrier use.
- X12 417 Rail Carrier Waybill Interchange
rail waybill interchange: rail shipment information passes between carriers.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a terminal or intermodal ramp records equipment activity. Name the operational owner of the terminal equipment event and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map container or rail equipment, event time and terminal. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic terminal equipment event data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful terminal equipment event processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 322 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic terminal equipment event data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out terminal equipment event without processing it twice.
Document structure
X12 322 Terminal Operations and Intermodal Ramp Activity at the element level
The X12 322 reference contains 26 segment entries and 113 data elements; 43 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 26
- Data elements
- 113
- Mandatory elements
- 43
| Segment | Elements | Mandatory |
|---|---|---|
| N7 | 14 | 1 |
| M7 | 4 | 1 |
| W09 | 3 | 1 |
| W2 | 11 | 4 |
| NA | 5 | 2 |
| R4 | 6 | 1 |
| DTM | 4 | 1 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| K1 | 2 | 1 |
| N9 | 6 | 1 |
| H1 | 1 | 1 |
- Equipment Number
- Seal Number
- Equipment Description Code
- Equipment Initial
- Equipment Status Code
- Port or Terminal Function Code
- Date/Time Qualifier
- Entity Identifier Code
Find your trading partner for X12 322
6 partners, 6 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 322 Terminal Operations and Intermodal Ramp Activity appears in this catalog
The largest groups of classified 322 catalog entries are in logistics & transport.
By industry
- logistics & transport 6 channels
FAQ
EDI 322 questions
What is an EDI 322?
EDI 322 is the X12 Terminal Operations and Intermodal Ramp Activity transaction set. Trading partners use it when a terminal or intermodal ramp records equipment activity. It carries the data for the terminal equipment event, and your system matches it on container or rail equipment, event time and terminal.
Who sends an EDI 322 and who receives it?
A terminal operator, port authority, or intermodal ramp sends the 322 to authorized parties to the shipment, such as ocean carriers, railroads, motor carriers, and shippers. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 322 sent?
A container or trailer passes an ingate or outgate at a marine terminal or intermodal rail ramp and the gate system records the movement. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 322?
Across 6 partner document references listed here, the business segments that appear most often include Q5 (Status Details), N7 (Equipment Details), M7 (Seal Numbers), W2 (Equipment Identification), NA (Cross-Reference Equipment), R4 (Port or Terminal). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 322 and EDI 404?
The 322 carries the terminal equipment event and is used when a terminal or intermodal ramp records equipment activity. The 404 carries the rail shipment and is used when rail movement instructions are ready for carrier use.
What should I map for X12 322?
Start with container or rail equipment, event time and terminal and the target terminal equipment event. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 322 error handling?
Process an out-gate event arriving before the in-gate event without discarding either. Test reuse of an equipment number on a later visit and keep the visits distinct. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 322?
The directory on this page links 6 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
