X12 transaction code
X12 322 Terminal Operations And Intermodal Ramp Activity
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 322
- Trading partners
- 6
Specification summary
X12 322 Terminal Operations And Intermodal Ramp Activity at the element level
The X12 322 specification defines 26 segments carrying 113 data elements, 43 of which are mandatory.
- 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
Trading partners that support X12 322
6 partners, 6 channels. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 322 Terminal Operations And Intermodal Ramp Activity
322 is used most heavily in logistics & transport.
The 322 reports terminal and intermodal ramp activity, chiefly ingate and outgate events, to the parties authorized on a shipment. Each event identifies the equipment initial and number, seal numbers, event status with date and time, and the terminal or port location, so carriers and shippers can track custody of a container or trailer as it moves through marine terminals and rail ramps. 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. A container or trailer passes an ingate or outgate at a marine terminal or intermodal rail ramp and the gate system records the movement.
By industry
- logistics & transport 6 channels
FAQ
X12 322 questions
What is X12 322 Terminal Operations And Intermodal Ramp Activity?
X12 322 (Terminal Operations And Intermodal Ramp Activity) is an EDI transaction set defined by ANSI ASC X12 for exchanging terminal operations and intermodal ramp activity between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 6 Stacksync trading partners support this code across 6 channels.
Which trading partners use X12 322?
6 Stacksync partners accept X12 322: Burlington Northern Santa Fe Railway (BNSF), Canadian National Railway, Canadian Pacific Railway, COFC, CPKC (formerly Kansas City Southern), CSX Transportation. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 322 with my ERP?
Stacksync handles the full X12 322 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
