To start and identify an interchange of zero or more functional groups and interchange-related control segments
Norfolk Southern X12 998 Set Cancellation
Plan X12 998 Set Cancellation for Norfolk Southern. Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 5
- Loops
- 0
- X12 998
- Partner references ↗
Implementation guide
Norfolk Southern: 998 mapping and validation
X12 998 Set Cancellation is used when a previously transmitted transaction needs cancellation. Preserve original transaction reference and cancellation reason so the transaction cancellation request in your business system stays connected to the original document.
This document is listed for Norfolk Southern. Confirm the version, required fields and responses that apply to your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | transaction cancellation request original transaction reference and cancellation reason |
|
| Update the receiving system | Processing the transaction cancellation request ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the transaction cancellation request Original document reference and matching response |
|
The document reference includes 5 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a previously transmitted transaction needs cancellation. Name the operational owner of the transaction cancellation request and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map original transaction reference and cancellation reason. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Norfolk Southern guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic transaction cancellation request data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful transaction cancellation request processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 998 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic transaction cancellation request data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out transaction cancellation request without processing it twice.
Transaction context
Where 998 Set Cancellation fits on Norfolk Southern
- Norfolk Southern channels
- 1 of 1
1 of Norfolk Southern's 1 channel list 998
- Trading partners
- 4
partner references list 998
- Channels
- 4
channel entries list 998
Frequently listed alongside 998
Document structure
X12 998 Set Cancellation at the element level
The X12 998 reference contains 5 segment entries and 34 data elements; 30 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 5
- Data elements
- 34
- Mandatory elements
- 30
| Segment | Elements | Mandatory |
|---|---|---|
| ZD | 8 | 4 |
Key identifiers in 998
- Transaction Set Identifier Code
- Equipment Initial
- Equipment Number
- Correction Indicator Code
Segment reference — 5 segments 0 loops · X12 998 Set Cancellation
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
This segment is used to specify the transaction set to be canceled
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Related references
Other transactions in Norfolk Southern
Other EDI documents listed on this channel.
Norfolk Southern EDI 998 questions
Common questions about 998 Set Cancellation on the Norfolk Southern channel.
What is X12 998 Set Cancellation used for?
998 is used when a previously transmitted transaction needs cancellation. It carries information for the transaction cancellation request. Match it to your business system using original transaction reference and cancellation reason.
Is 998 required for Norfolk Southern?
998 is listed for Norfolk Southern. Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 998?
Start with original transaction reference and cancellation reason and the target transaction cancellation request. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 998 error handling?
Test cancellation of an unknown transaction and retain an explicit unresolved state. Require business review when the original transaction has already caused a shipment or ledger entry. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 998 relate to other EDI messages?
Keep 998 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the transaction cancellation request workflow; confirm any required companion messages with your partner.
Connect Norfolk Southern EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
