X12 transaction code
X12 322 Terminal Operations And Intermodal Ramp Activity
X12 322 Terminal Operations And Intermodal Ramp Activity: explore its business purpose, mapping identifiers, validation tests and 6 partner references across 6 listed channels.
- Standard
- X12
- Code
- 322
- Partner references
- 6
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
X12 322 questions
What is X12 322 Terminal Operations And Intermodal Ramp Activity used for?
322 is used when a terminal or intermodal ramp records equipment activity. It carries information for the terminal equipment event. Match it to your business system using container or rail equipment, event time and terminal.
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.
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.
How does 322 relate to other EDI messages?
X12 404 Rail Carrier Shipment Information; X12 417 Rail Carrier Waybill Interchange are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 322 and 404?
322 is used when a terminal or intermodal ramp records equipment activity. 404 is used when rail movement instructions are ready for carrier use. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
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.
