To start and identify an interchange of zero or more functional groups and interchange-related control segments
CPKC (formerly Kansas City Southern) X12 322 Terminal Operations and Intermodal Ramp Activity
Plan X12 322 Terminal Operations and Intermodal Ramp Activity for CPKC (formerly Kansas City Southern) / Kansas City Southern. Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 15
- Loops
- 3
- X12 322
- Partner references ↗
Implementation guide
CPKC (formerly Kansas City Southern) / Kansas City Southern: 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.
This document is listed for CPKC (formerly Kansas City Southern) / Kansas City Southern. Confirm the version, required fields and responses that apply to your account.
| 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 |
|
The document reference includes 15 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
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.
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 CPKC (formerly Kansas City Southern) 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.
Transaction context
Where 322 Terminal Operations and Intermodal Ramp Activity fits on Kansas City Southern
- CPKC (formerly Kansas City Southern) channels
- 1 of 1
1 of CPKC (formerly Kansas City Southern)'s 1 channel list 322
- Trading partners
- 6
partner references list 322
- Channels
- 6
channel entries list 322
Frequently listed alongside 322
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 |
Key identifiers in 322
- Equipment Number
- Seal Number
- Equipment Description Code
- Equipment Initial
- Equipment Status Code
- Port or Terminal Function Code
- Date/Time Qualifier
- Entity Identifier Code
Segment reference — 15 segments 3 loops · X12 322 Terminal Operations and Intermodal Ramp Activity
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To specify the status of the shipment in terms of dates, time, reference numbers, and location
N7 Loop Repeat: 1,000
To identify the equipment
To record seal numbers used and the organization that applied the seals
To identify equipment and the commodity being carried
To cross-reference additional equipment to a primary piece of equipment
To provide vessel details and voyage number
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
R4 Loop Repeat: 20
Contractual or operational port or point relevant to the movement of the cargo
To specify special handling instructions in coded or free-form format
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To specify the geographic place of the named party
To transmit identifying information as specified by the Reference Identification Qualifier
Related references
Other transactions in Kansas City Southern
Other EDI documents listed on this channel.
CPKC (formerly Kansas City Southern) / Kansas City Southern EDI 322 questions
Common questions about 322 Terminal Operations and Intermodal Ramp Activity on the Kansas City Southern channel.
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.
Is 322 required for CPKC (formerly Kansas City Southern) / Kansas City Southern?
322 is listed for CPKC (formerly Kansas City Southern) / Kansas City Southern. Confirm the required version and direction for your business unit and account with the partner.
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 is a related document also listed on Kansas City Southern. 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 CPKC (formerly Kansas City Southern) 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.
