X12

Inbound

COFC X12 322 Terminal Operations and Intermodal Ramp Activity

COFC

The EDI 322 (Terminal Operations and Intermodal Ramp Activity) document is used by COFC for electronic data interchange. It enables automated processing and compliance with COFC's trading partner requirements.

14segments

3loops

7mandatory

Book a demo

← All COFC transactions

Schema Reference

14 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 Interchange Control Standards Identifier

M ID 1-1

ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Usage Indicator

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

Q505 Status Reason Code

O ID 3-3

Q506 City Name

C AN 2-30

Q507 State or Province Code

O ID 2-2

Q508 Country Code

O ID 2-3

N7 Loop Repeat: 1,000

N701 Equipment Initial

O AN 1-4

N702 Equipment Number

M AN 1-10

N703 Weight

C R 1-10

N704 Weight Qualifier

C ID 1-2

N708 Volume

C R 1-8

N709 Volume Unit Qualifier

C ID 1-1

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

O ID 4-4

N723 Standard Carrier Alpha Code

O ID 2-4

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

DTM03 Time

C TM 4-8

DTM04 Time Code

O ID 2-2

M701 Seal Number

M AN 2-15

M702 Seal Number

O AN 2-15

M703 Seal Number

O AN 2-15

W201 Equipment Initial

M AN 1-4

W202 Equipment Number

M AN 1-10

W203 Commodity Code

O AN 1-30

W204 Equipment Description Code

M ID 2-2

W205 Equipment Status Code

M ID 1-2

W211 Equipment Initial

C AN 1-4

W212 Equipment Number

C AN 1-10

NA03 Equipment Initial

M AN 1-4

NA04 Equipment Number

M AN 1-10

NA05 Cross Reference Type Code

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

R405 Country Code

O ID 2-3

R406 Terminal Name

O AN 2-30

R407 Pier Number

O AN 1-4

R408 State or Province Code

O ID 2-2

H301 Special Handling Code

C ID 2-3

H302 Special Handling Description

C AN 2-30

N1 Loop Repeat: 10

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

N903 Free-form Description

C AN 1-45

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

How It Works

Automating COFC 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 COFC EDI 322 (Terminal Operations and Intermodal Ramp Activity) documents automatically — syncing data to your system in real time with no manual intervention required.

COFC EDI 322 FAQ

Common questions about 322 Terminal Operations and Intermodal Ramp Activity transactions with COFC.

What is a COFC EDI 322 Terminal Operations and Intermodal Ramp Activity?

The COFC 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 COFC and their suppliers, carriers, or partners. Stacksync processes COFC 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 COFC's requirements in real time.

How does Stacksync automate COFC EDI 322 Terminal Operations and Intermodal Ramp Activity transactions?

Stacksync handles COFC 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 COFC 322 document meets their specific formatting requirements before transmission or after receipt.

What are common COFC EDI 322 errors and how do I fix them?

Common errors in COFC 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 COFC 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 COFC EDI 322 with Stacksync?

Most COFC 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 COFC's 322 format and your system, running test transactions, and completing COFC's certification process if required. Stacksync includes pre-built mappings for COFC'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 COFC EDI 322 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how COFC 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 COFC updates their 322 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate COFC EDI?