X12
Inbound

Canadian National Railway X12 998 Set Cancellation

Canadian National Railway
The EDI 998 (Set Cancellation) document is used by Canadian National Railway for electronic data interchange. It enables automated processing and compliance with Canadian National Railway's trading partner requirements.
5segments
0loops
5mandatory

Schema Reference

5 segments · X12 998 Set Cancellation

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
ZD Transaction Set Deletion - ID, Reason, and Source
Mandatory Max: 1
ZD01 Transaction Set Identifier Code
M ID 3-3
ZD03 Equipment Initial
M AN 1-4
ZD04 Equipment Number
M AN 1-15
ZD05 Transaction Reference Number
O AN 1-50
ZD06 Transaction Reference Date
O DT 8-8
ZD07 Correction Indicator Code
M 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 Canadian National Railway EDI 998

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

Validate
Transform
Route
Monitor
Stacksync processes Canadian National Railway EDI 998 (Set Cancellation) documents automatically — syncing data to your system in real time with no manual intervention required.

Canadian National Railway EDI 998 FAQ

Common questions about 998 Set Cancellation transactions with Canadian National Railway.

What is a Canadian National Railway EDI 998 Set Cancellation?

The Canadian National Railway EDI 998 Set Cancellation is an X12 transaction set used to exchange Set Cancellation data electronically between trading partners. As a inbound document, it standardizes the communication of Set Cancellation information between Canadian National Railway and their suppliers, carriers, or partners. Stacksync processes Canadian National Railway 998 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 Canadian National Railway's requirements in real time.

What is a Canadian National Railway EDI 998 Set Cancellation?

The Canadian National Railway EDI 998 Set Cancellation is an X12 transaction set used to exchange Set Cancellation data electronically between trading partners. As a inbound document, it standardizes the communication of Set Cancellation information between Canadian National Railway and their suppliers, carriers, or partners. Stacksync processes Canadian National Railway 998 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 Canadian National Railway's requirements in real time.

How does Stacksync automate Canadian National Railway EDI 998 Set Cancellation transactions?

Stacksync handles Canadian National Railway EDI 998 Set Cancellation 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 998 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 Canadian National Railway 998 document meets their specific formatting requirements before transmission or after receipt.

How does Stacksync automate Canadian National Railway EDI 998 Set Cancellation transactions?

Stacksync handles Canadian National Railway EDI 998 Set Cancellation 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 998 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 Canadian National Railway 998 document meets their specific formatting requirements before transmission or after receipt.

What are common Canadian National Railway EDI 998 errors and how do I fix them?

Common errors in Canadian National Railway EDI 998 Set Cancellation 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 Canadian National Railway 998 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 Canadian National Railway EDI 998 errors and how do I fix them?

Common errors in Canadian National Railway EDI 998 Set Cancellation 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 Canadian National Railway 998 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 Canadian National Railway EDI 998 with Stacksync?

Most Canadian National Railway EDI 998 Set Cancellation 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 Canadian National Railway's 998 format and your system, running test transactions, and completing Canadian National Railway's certification process if required. Stacksync includes pre-built mappings for Canadian National Railway's most common 998 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 Canadian National Railway EDI 998 with Stacksync?

Most Canadian National Railway EDI 998 Set Cancellation 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 Canadian National Railway's 998 format and your system, running test transactions, and completing Canadian National Railway's certification process if required. Stacksync includes pre-built mappings for Canadian National Railway's most common 998 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize Canadian National Railway EDI 998 field mappings in Stacksync?

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

Can I customize Canadian National Railway EDI 998 field mappings in Stacksync?

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

Ready to automate Canadian National Railway 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