Originally posted by: SystemAdmin

We are running Commerce Manager to process dental claims with the compliance check and an 837 Hipaa map imbedded in the flow. We recently received a file from a trading partner which had an error in one of the segments and the 997 nor the 824 reports were generated. The only output generated by Commerce Manager compliance check was the compliance_check_log. This log had the following information about the erroneous segment '#####00000TOO 8'. There were hundreds of this TOO (tooth) segments in the file. We could not find the error and had to reject the file.
The trading partner had left the last field blank after a : and has since corrected and resubmitted the file. Here is the erroneous segment; TOO*JP*14*:D:O:

The log was not very helpful in finding the problem. My question is what is the best way to produce the 824 and/or 997 when there are errors in a file since they were not produced when this error occurred? And is there some documentation as to how to read the compliance_check_log?
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Without further details I am only guessing. You should contact customer care to research the answer to why this didn't generate a 997.

If the transaction contained over 99,999 segments and the error ocurred on a segment over 99,999 , Commerce Manager had an overflow condition that would give # in the log. The overflow has been corrected. However with X12 limitations, we now give back a segment position in the AK302 of up to 6 digits. This means any error found on or after segment 1,000,000 will show up in the AK302 as 999999 (six 9's). If we were to give the correct segment position we would generate an invalid 997. Segment positions in error less than 1,000,000 return the correct segment position. You are currently limited to 9,999,999,999 segments in a transaction, by X12 standards (SE01).

But this is just a guess of the issue. Please contact customer care for research.

The documentation on understanding the logs is included with DataStage TX. We do not document specifics to Commerce Manager about the audit log as it changes every release and patch. Understanding how to read a DataStage TX audit log and then understanding Commerce Manager is the way to understand. There are very few times when the log must be examined by hand and it tends to be debugging.

Thanks
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender