X12
Inbound

CPKC (formerly Kansas City Southern) X12 322 Terminal Operations and Intermodal Ramp Activity

Kansas City Southern
The EDI 322 (Terminal Operations and Intermodal Ramp Activity) document is used by CPKC (formerly Kansas City Southern) for electronic data interchange. It enables automated processing and compliance with CPKC (formerly Kansas City Southern)'s trading partner requirements.
15segments
3loops
7mandatory
Book a demo
← All CPKC (formerly Kansas City Southern) transactions

Schema Reference

15 segments · X12 322 Terminal Operations and Intermodal Ramp Activity

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 Interchange Control Version Number Code
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested Code
M ID 1-1
ISA15 Interchange Usage Indicator Code
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
Q5 Status Details
Mandatory Max: 1
Q501 Shipment Status Code
O ID 1-2
Q502 Date
O DT 8-8
Q503 Time
C TM 4-8
Q504 Time Code
C ID 2-2
N7 Loop Repeat: 1,000
N7 Equipment Details
Mandatory Max: 1
N701 Equipment Initial
O AN 1-4
N702 Equipment Number
M AN 1-15
N703 Weight
C R 1-10
N704 Weight Qualifier
C ID 1-2
N711 Equipment Description Code
O ID 2-2
N712 Standard Carrier Alpha Code
O ID 2-4
N715 Equipment Length
O N0 4-5
N717 Weight Unit Code
O ID 1-1
N718 Equipment Number Check Digit
O N0 1-1
N720 Height
O R 1-8
N721 Width
O R 1-8
N722 Equipment Type Code
O ID 4-4
N723 Standard Carrier Alpha Code
O ID 2-4
M7 Seal Numbers
Optional Max: 5
M701 Seal Number
M AN 2-15
M702 Seal Number
O AN 2-15
M703 Seal Number
O AN 2-15
M704 Seal Number
O AN 2-15
W2 Equipment Identification
Optional Max: 1
W201 Equipment Initial
M AN 1-4
W202 Equipment Number
M AN 1-15
W204 Equipment Description Code
M ID 2-2
W205 Equipment Status Code
M ID 1-2
W207 Intermodal Service Code
O ID 1-2
W211 Equipment Initial
C AN 1-4
W212 Equipment Number
C AN 1-15
NA Cross-Reference Equipment
Optional Max: 30
NA03 Equipment Initial
M AN 1-4
NA04 Equipment Number
M AN 1-15
NA05 Cross Reference Type Code
O ID 1-1
NA06 Position
O AN 1-3
NA11 Yes/No Condition or Response Code
O ID 1-1
NA12 Equipment Number Check Digit
O N0 1-1
V1 Vessel Identification
Optional Max: 1
V101 Vessel Code
C ID 1-8
V102 Vessel Name
C AN 2-50
V104 Flight/Voyage Number
O AN 2-30
V108 Vessel Code Qualifier
O ID 1-1
R4 Loop Repeat: 20
R4 Port or Terminal
Mandatory Max: 1
R401 Port or Terminal Function Code
M ID 1-1
R402 Location Qualifier
C ID 1-2
R403 Location Identifier
C AN 1-30
R404 Port Name
O AN 2-24
H3 Special Handling Instructions
Optional Max: 6
H301 Special Handling Code
C ID 2-3
N1 Loop Repeat: 10
N1 Party Identification
Optional Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N4 Geographic Location
Optional Max: 1
N401 City Name
O AN 2-30
N402 State or Province Code
C ID 2-2
N403 Postal Code
C ID 3-15
N404 Country Code
C ID 2-3
N9 Extended Reference Information
Optional Max: 30
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-80
N904 Date
O DT 8-8
N905 Time
C TM 4-8
N906 Time Code
O ID 2-2
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating CPKC (formerly Kansas City Southern) EDI 322

Stacksync validates, transforms, and delivers your 322 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync processes CPKC (formerly Kansas City Southern) EDI 322 (Terminal Operations and Intermodal Ramp Activity) documents automatically — syncing data to your system in real time with no manual intervention required.
Related Documents

Other CPKC (formerly Kansas City Southern) EDI transactions

Explore all supported EDI transaction types for CPKC (formerly Kansas City Southern). Stacksync handles every document from a single platform.

404In
Rail Carrier Shipment Information
Kansas City Southern
998In
Set Cancellation
Kansas City Southern
824In
Application Advice
Kansas City Southern
View all CPKC (formerly Kansas City Southern) EDI documents →

CPKC (formerly Kansas City Southern) EDI 322 FAQ

Common questions about 322 Terminal Operations and Intermodal Ramp Activity transactions with CPKC (formerly Kansas City Southern).

What is a CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity?

The CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity is an X12 transaction set used to exchange Terminal Operations and Intermodal Ramp Activity data electronically between trading partners. As a inbound document, it standardizes the communication of Terminal Operations and Intermodal Ramp Activity information between CPKC (formerly Kansas City Southern) and their suppliers, carriers, or partners. Stacksync processes CPKC (formerly Kansas City Southern) 322 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with CPKC (formerly Kansas City Southern)'s requirements in real time.

What is a CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity?

The CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity is an X12 transaction set used to exchange Terminal Operations and Intermodal Ramp Activity data electronically between trading partners. As a inbound document, it standardizes the communication of Terminal Operations and Intermodal Ramp Activity information between CPKC (formerly Kansas City Southern) and their suppliers, carriers, or partners. Stacksync processes CPKC (formerly Kansas City Southern) 322 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with CPKC (formerly Kansas City Southern)'s requirements in real time.

How does Stacksync automate CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity transactions?

Stacksync handles CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 322 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every CPKC (formerly Kansas City Southern) 322 document meets their specific formatting requirements before transmission or after receipt.

How does Stacksync automate CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity transactions?

Stacksync handles CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 322 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every CPKC (formerly Kansas City Southern) 322 document meets their specific formatting requirements before transmission or after receipt.

What are common CPKC (formerly Kansas City Southern) EDI 322 errors and how do I fix them?

Common errors in CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates CPKC (formerly Kansas City Southern) 322 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

What are common CPKC (formerly Kansas City Southern) EDI 322 errors and how do I fix them?

Common errors in CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates CPKC (formerly Kansas City Southern) 322 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

How long does it take to set up CPKC (formerly Kansas City Southern) EDI 322 with Stacksync?

Most CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between CPKC (formerly Kansas City Southern)'s 322 format and your system, running test transactions, and completing CPKC (formerly Kansas City Southern)'s certification process if required. Stacksync includes pre-built mappings for CPKC (formerly Kansas City Southern)'s most common 322 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

How long does it take to set up CPKC (formerly Kansas City Southern) EDI 322 with Stacksync?

Most CPKC (formerly Kansas City Southern) EDI 322 Terminal Operations and Intermodal Ramp Activity integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between CPKC (formerly Kansas City Southern)'s 322 format and your system, running test transactions, and completing CPKC (formerly Kansas City Southern)'s certification process if required. Stacksync includes pre-built mappings for CPKC (formerly Kansas City Southern)'s most common 322 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize CPKC (formerly Kansas City Southern) EDI 322 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how CPKC (formerly Kansas City Southern) EDI 322 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If CPKC (formerly Kansas City Southern) updates their 322 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Can I customize CPKC (formerly Kansas City Southern) EDI 322 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how CPKC (formerly Kansas City Southern) EDI 322 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If CPKC (formerly Kansas City Southern) updates their 322 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate CPKC (formerly Kansas City Southern) EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding
Book a demo
"We've been using Stacksync across 4 different projects and can't imagine working without it."

Alex Marinov

VP Technology, Acertus Delivers
Vehicle logistics powered by technology