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

Schema Reference

15 segments · X12 322 Terminal Operations and Intermodal Ramp Activity

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

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

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

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

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

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

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

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

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

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

H301 Special Handling Code

C ID 2-3

N1 Loop Repeat: 10

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

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

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

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

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.

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).

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

Most suppliers are fully connected and processing live CPKC (formerly Kansas City Southern) EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with CPKC (formerly Kansas City Southern)?

No. Stacksync handles the entire EDI transport layer. We connect directly to CPKC (formerly Kansas City Southern)'s trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with CPKC (formerly Kansas City Southern) compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for CPKC (formerly Kansas City Southern)?

Stacksync supports all EDI document types required by CPKC (formerly Kansas City Southern) — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect CPKC (formerly Kansas City Southern) EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between CPKC (formerly Kansas City Southern)'s EDI network and your system in real time.

What happens when CPKC (formerly Kansas City Southern) updates their EDI specifications?

Stacksync monitors CPKC (formerly Kansas City Southern)'s EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.