Error Severity Types
The following are the segments in the generated 997 acknowledge when a transaction is rejected:
ST~997~0001'
AK1~HC~000000001'
AK2~837~000000001'
AK3~CLM~36~2300~8'
AK4~11+3~1362~1~AP'
AK5~R'
AK9~R~1~1~0'
SE~9~0001'
The following are the segments in the generated 999 acknowledge when a transaction is rejected:
ST~999~0001' AK1~HC~1' AK2~837~Transacti~000000000001' IK3~NM1~7~2010~8' IK4~3~1035~5~NN' IK5~R~5' AK9~R~1~1~0' SE~8~0001'
The AK2 segment identifies the transaction that is rejected. The AK3/IK3 and AK4/IK4 segments give information about where one or more errors occurred in the transaction. The AK5/IK5 segment indicates that the transaction is rejected and contains a transaction status code of 'R'. The AK9 segment indicates that the group is rejected, 'R', because there was only one transaction in the group and that transaction is rejected.
If some of the transactions in the group are accepted while others are rejected, the status of the group in the AK9 segment would be 'P', which indicates that at least one transaction in the group is rejected.
When a transaction is rejected, error information is also sent to the private process on the subject AX.BCCE.INSTALLATION.X12.ERROR.VALIDATION.
This error information contains the transaction ID of the transaction that has validation errors and descriptive information about the validation errors similar to the following:
controlNumInfo={^class^="ControlNumberInfo
" ^idx^=1 interchange="000008361" group="1" transaction="000000001"}
errorInfoList={^class^="ConversionEngineInfo" ^idx^=2 ^1^={^class^="ConversionEngineInfo" ^idx^=1 errorSeverity="Normal" errorCategory="Rejecting" errorMsg="The Previous Claim does not balance. Formula used CLM02 (93534) = sum of SV102 (93533)." errorID="30092" errorContext="Loop/Group-2440 | Segment-HL" errorDataParent="HL~4~2~2
3~0'" errorSegmentCount=178 errorLoopGroupCount=1}}
Setting different error severity types to validation errors affect the information about the validation errors that is contained in 997/999 acknowledgements and the error information reported to the private process. It also affects whether the given transaction is converted from EDI to XML or from XML to EDI. When a transaction is rejected, no conversion takes place.
The following table describes the four levels of severity that can be configured for validation errors and their effect on how error information is reported.
|
Error Severity Type |
997/999 Acknowledgement |
Error Information to Private Process |
Data Conversion Occurs? |
|
Ignore |
AK5/IK5 segment reports transaction status of 'A' for accepted. AK3/IK3 and AK4/IK4 segments are not present. |
Does not cause the generation of an error report to the private process. |
Yes |
|
Informational |
AK5/IK5 segment reports transaction status of 'A' for accepted. AK3/IK3 and AK4/IK4 segments are not present. |
The cause of the error is reported in the message to the private process with the error code and a description of the error. The error description begins with |
Yes |
|
Warning |
AK5/IK5 segment reports transaction status of 'E' for accepted with errors. AK3/IK3 and AK4/IK4 segments contain information about the location of the error in the transaction as appropriate. |
The cause of the error is reported in the message to the private process with the error code and a description of the error. The error description begins with |
Yes |
|
Error |
AK5/IK5 segment reports transaction status of 'R' for rejected. AK3/IK3 and AK4/IK4 segments contain information about the location of the error in the transaction as appropriate. |
The cause of the error is reported in the message to the private process with the error code and a description of the error. |
No |
|
Fatal |
|
Similar in behavior to the 'Error' type but is used for system errors. |
No |