Troubleshooting
Problem
Transaction-Non-Compliant, Code: 300 (SCI55512)
Symptom
Receiving a Transaction-Non-Compliant, Code: 300 (mandatory block missing) when trying to process an inbound EDI document that is streamed.
Cause
When the translator has data left over that it wasn't able to match in the map on the first attempt (which will be the case if the ISA, GE, etc segments are missing) it tries to run through the map again to match up the remaining data. The remaining data does not contain the BEG segment because it already got matched on the previous run. This is why you get 300 mandatory segment errors in this case. If you don't want the translator to run through the map again to match up any remaining data, you can control this by setting the "exhaust input" parameter to false.
Resolving The Problem
If you have the inbound envelopes configured to, "Retain Enclosing Envelope = Yes" then you must have an SE, GE and IEA record included as well as a ISA, GS, and ST segment on the input side of your map.
Historical Number
PRI2312
Product Synonym
[<p><b>]Fact[</b><p>];Gentran Integration Suite;Sterling Integrator;All Releases [<br/>] SCI55512
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21536173