Overview
On Boomi, a rejected 997 rarely means the document is wrong. It usually means the envelope is: control numbers, qualifiers or functional group identifiers that do not match what the trading partner's system expects. Each partner is configured once at go-live and rarely looked at again.
Challenge
After a second EDI process was added for a large OEM customer, the partner began rejecting outbound 856 ship notices with 997 acknowledgements, and shipments sat in an exception queue at the partner. The Boomi process reported success because the AS2 delivery worked. The supplier's team could not tell which interchange was rejected or why.
Environment
Boomi processes for X12 EDI over AS2 with about a dozen trading partners, running on a Boomi-hosted runtime cloud, with an ERP generating shipment data.
Approach
AceMQ pulled the rejected interchanges and the partner's 997 error codes, then compared the trading partner profile against the partner's specification. Two processes were drawing interchange control numbers from different number ranges for the same sender and receiver pair, and one functional group identifier did not match what the OEM expected. Fixes were made in the profile and the processes, then the stuck shipments were resent in order.
Solution
- Collected the rejected interchanges and the partner's 997 error codes for each
- Compared the trading partner profile with the OEM's published X12 specification
- Found two processes using separate control number ranges for the same sender and receiver
- Moved both processes to a single number range for that trading partner
- Corrected the functional group identifier in the partner profile
- Resent the held 856 documents in sequence and confirmed accepted acknowledgements
- Added an alert on rejected 997s so a bad interchange is seen the same day
Outcome
The OEM now accepts the ship notices, the held shipments were released, and rejected acknowledgements raise an alert instead of waiting for the partner to complain. Each trading partner's envelope settings are documented for the next onboarding.