How Docsplitter uses the 997 or 999

The source of errors is the 997 or the 999 rather than the detailed results file.

Note: Docsplitter does not check the validity of the 997 or 999. It is assumed to be valid.

Docsplitter treats certain Error Codes in the AK5 and AK9 as warnings rather than errors so that it can split the valid application documents from the invalid ones. Otherwise, Docsplitter would have to handle the transaction sets and groups as unsplittable units.

Seg.	With this ACK code	AND this Error code	Docsplitter action
AK5	M, R, W, X	5 or empty (with no other codes)	Treats it as a warning; splits within transaction set; records WARN tag in output report
	A, E		Not an error; nothing in output report
AK9	M, R, W, X	empty	Considers it a warning; splits the functional group
	A, E, P		Not an error; nothing in output report

By treating the AK5 and AK9 error codes as warnings, Docsplitter can look at the AK3s to determine which chunks of data go to the valid file and which go to the invalid file.

Examples

Seg.	Docsplitter treatment
AK5*R~	Treated as warning, since the Acknowledgment code is R and the error code is empty. Docsplitter looks at the AK3s for this transaction set to determine what data goes to the valid file and what data goes to the invalid file.
AK5R5~	Treated as warning, since the Acknowledgment code is R and the error code is 5.
AK5E5~	Treated as warning, since the Acknowledgment code is E and the error code is 5.
AK5R6~	Treated as an error, since the error code is 6. The entire transaction set goes to the invalid file. Error codes other than 5 or empty indicate errors to the transaction set itself (for example, to the ST or SE segments or to security). It would be impossible for Docsplitter to write any valid EDI from this transaction set.
AK9R220~	Treated as warning, since the Acknowledgment code is R and there are no error codes. An error code in the AK9 would indicate an error in the GS or GE segments, meaning that no valid EDI data could be written.