X12 transaction code
X12 998 Set Cancellation
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 998
- Trading partners
- 4
Specification summary
X12 998 Set Cancellation at the element level
The X12 998 specification defines 5 segments carrying 34 data elements, 30 of which are mandatory.
- Segments
- 5
- Data elements
- 34
- Mandatory elements
- 30
| Segment | Elements | Mandatory |
|---|---|---|
| ZD | 8 | 4 |
- Transaction Set Identifier Code
- Equipment Initial
- Equipment Number
- Correction Indicator Code
Trading partners that support X12 998
4 partners, 4 channels. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 998 Set Cancellation
998 is used most heavily in logistics & transport.
The 998 requests deletion of a previously transmitted transaction set and states the reason, such as a diverted shipment or cancelled bill. In practice it is a rail document: shippers use it to void a bill of lading (404) already submitted to the railroad while it is still suspended in the carrier's system. It is a three-segment message (ST, ZD, SE) whose ZD segment identifies the original document by equipment initial and number, bill of lading number, and sender, with a CA qualifier marking the cancellation. Sent by the rail shipper (the railroad's customer) to the rail carrier holding the previously submitted 404 bill of lading. A rail shipment is cancelled or diverted after the bill of lading has been transmitted to the railroad but before the car is waybilled and moves.
By industry
- logistics & transport 4 channels
FAQ
X12 998 questions
What is X12 998 Set Cancellation?
X12 998 (Set Cancellation) is an EDI transaction set defined by ANSI ASC X12 for exchanging set cancellation between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 4 Stacksync trading partners support this code across 4 channels.
Which trading partners use X12 998?
4 Stacksync partners accept X12 998: Canadian National Railway, CPKC (formerly Kansas City Southern), CSX Transportation, Norfolk Southern. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 998 with my ERP?
Stacksync handles the full X12 998 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
