S.No | Integration Process | Type of error | Action | Notification Type | Retry |
|---|---|---|---|---|---|
A1 | Order Process from CC&B | CC&B cannot reach Req ABCS | Process error response to CC&B | The Notification Download Staging table is marked with an error and CC&B creates a To Do Entry. | Resend the message by changing the status in the CC&B Notification Download table. |
A2 | Internal failure in Req ABCS | Process error response to CC&B | The Notification Download Staging table is marked with an error and CC&B creates a To Do Entry. | Resend the message by changing the status in the CC&B Notification Download table. | |
A3 | Requester ABCS cannot reach Mediator Process for routing | Process error response to CC&B | The Notification Download Staging table is marked with an error and CC&B creates a To Do Entry. | Resend the message by changing the status in the CC&B Notification Download table. | |
A4 | Mediator cannot communicate to the JMS Queue | Process error response to CC&B | The Notification Download Staging table is marked with an error and CC&B creates a To Do Entry. | Resend the message by changing the status in the CC&B Notification Download table. | |
A5 | JMS consumer is down | Messages queue up | Start JMS consumer | ||
A6 | Provider ABCS cannot be reached | Message goes from the queue to the corresponding error queue. + AIA error handling. | E-mail notification and worklist entry | After ensuring that the prov ABCS is up again, the admin must restore the messages from the error to the main queue and then re-start the consumption from the queue. | |
A7 | Internal failure in Provider ABCS | Negative acknowledgment back to CC&B | CC&B To do, E-mail notification and worklist entry | Fix the issue, Resend the original message by changing the status in the CC&B Notification Download table. | |
A8 | Provider ABCS cannot reach target web service endpoint | Message goes from the queue to the corresponding error queue. + AIA error handling. | E-mail notification and worklist entry | After ensuring that the web service end-point is up again, the admin must restore the messages from error to the main queue and then re-start the consumption from the queue. | |
A9 | Error response from target (valid business response) | Negative acknowledgment back to CC&B | CC&B creates a To Do Entry. | Fix the data, Resend the original message by changing the status in the CC&B Notification Download table. | |
A10 | The CC&B Ack ABCS cannot be reached. | Message goes to error queue & AIA error handling. | E-mail notification and worklist entry | ||
A11 | CC&B Ack web service (FA Response) cannot be reached or returns a server error | Message goes from the queue to the corresponding error queue. + AIA error handling. | E-mail notification and worklist entry | ||
A12 | CC&B Ack web service(FA Response ) returns a Client Error | AIA Error Handling | E-mail notification and worklist entry | ||
B1 | Order Process from WAM v1.9.1.x | WAM cannot reach Req ABCS | Process error response to WAM | An on screen error is displayed. | Resend the message by selecting the appropriate action on the WAM service request. (This works for create, update, cancel messages. Not for completions). When the resend link is selected a create message is sent to ABCS. |
B2 | Internal failure in Req ABCS | Process error response to WAM | An on screen error is displayed. | ||
B3 | Requester ABCS cannot reach the Mediator process for Routing | Process error response to WAM | An on screen error is displayed. | ||
B4 | Mediator cannot communicate to the JMS Queue | Process error response to WAM | An on screen error is displayed. | ||
B5 | JMS consumer is down | Messages queue up | Start JMS consumer | ||
B6 | Provider ABCS cannot be reached | Message goes from the queue to the corresponding error queue. + AIA error handling. | E-mail notification and worklist entry | After ensuring that the prov ABCS is up again, the admin must restore the messages from error to the main queue and then re-start the consumption from the queue. | |
B7 | Internal failure in Provider ABCS | Negative acknowledgment to the WAM ABCS. | E-mail notification and worklist entry | Resend the message by selecting the appropriate action on the WAM service request. (This action works for create, update, cancel messages, but not for completions). When the resend link is clicked a create message is sent to ABCS. | |
B8 | Provider ABCS cannot reach target web service endpoint | Message goes from the queue to the corresponding error queue. + AIA error handling. | E-mail notification and worklist entry | After ensuring that the web service end-point is up again, the admin must restore the messages from error to the main queue and then re-start the consumption from the queue. | |
B9 | Error response from target | Negative acknowledgment to the WAM ABCS. | E-mail notification and worklist entry | Resend the message by selecting the appropriate action on the WAM service request. (This action works for create, update, cancel messages, but not for completions). When the resend link is clicked a create message is sent to ABCS. | |
B10 | Ack ABCS for WAM cannot be reached. | AIA error handling. | E-mail notification and worklist entry | ||
B11 | Internal failure in Ack ABCS for WAM | AIA error handling | E-mail notification and worklist entry | ||
C1 | Order Process from WAM v2.1.x | WAM/ODM v2.1.x cannot reach Req ABCS | Process error response to WAM v2.1.x | The activity is marked with an error. | |
C2 | Internal failure in Req ABCS | Process error response to WAM v2.1.x | The activity is marked with an error. | ||
C3 | Requester ABCS cannot reach the Mediator Process for routing | Process error response to WAM v2.1.x | The activity is marked with an error. | ||
C4 | Mediator cannot communicate to the JMS Queue | Process error response to WAM v2.1.x | The activity is marked with an error. | ||
C5 | JMS consumer is down | Messages queue up | Restart the JMS consumer | ||
C6 | Provider ABCS cannot be reached | Message goes from the queue to the corresponding error queue. + AIA error handling. | E-mail notification and worklist entry | After ensuring that the prov ABCS is up again, the admin must restore the messages from error to the main queue and then re-start the consumption from the queue. | |
C7 | Internal failure in Provider ABCS | Negative acknowledgment back to WAM v2.1.x | E-mail notification and worklist entry | WAM Log shows error message, E-mail notification and worklist entry | |
C8 | Provider ABCS cannot reach target web service endpoint | Message goes from the queue to the corresponding error queue. + AIA error handling. | E-mail notification and worklist entry | After ensuring that the web service end-point is up again, the admin must restore the messages from error to the main queue and then re-start the consumption from the queue. | |
C9 | Error response from target business | Negative acknowledgment to WAM v2.1.x. | WAM Activity shows the error. | Fix the data and click the Resend button in WAM. | |
C10 | The WAM v2.1.x Ack ABCS cannot be reached. | Message goes from the queue to the error queue + AIA error handling. | E-mail notification and worklist entry. | ||
C11 | WAM v2.1.x Ack web service (FA Response) cannot be reached or server error. | Message goes from the queue to the corresponding error queue. + AIA error handling. | |||
C12 | WAM v2.1.x Ack web service returns a client error | AIA Error Handling | E-mail notification and worklist entry. | ||
D1 | Order Process from MWM | MWM cannot reach Req ABCS | Process error response to MWM | For any order processing error, verification is synchronous, and the user must retry. All other actions create a sync request record to generate the outbound message. These sync request records are retried automatically by the F1-SYNRQ batch process until they are successful. This applies for any error (business or technical). | |
D2 | Internal failure in Req ABCS | Process error response to MWM | |||
D3 | Requester ABCS cannot reach the Mediator Process for Routing | Process error response to MWM | |||
D4 | Mediator cannot communicate to the JMS Queue | Process error response to MWM | |||
D5 | JMS consumer is down | Messages queue up | Start JMS consumer | ||
D6 | Provider ABCS cannot be reached | Message goes from the queue to the corresponding error queue. + AIA error handling. | E-mail notification and worklist entry | After ensuring that the prov ABCS is up again, the admin must restore the messages from error to the main queue and then re-start the consumption from the queue. | |
D7 | Internal failure in Provider ABCS | Negative acknowledgment to the MWM ABCS. | E-mail notification and worklist entry | ||
D8 | Provider ABCS cannot reach target web service endpoint | Message goes from the queue to the corresponding error queue. + AIA error handling. | E-mail notification and worklist entry | After ensuring that the web service end-point is up again, the admin must restore the messages from error to the main queue and then re-start the consumption from the queue. | |
D9 | Error response from target | Negative acknowledgment to the MWM ABCS. | E-mail notification and worklist entry | ||
D10 | Ack ABCS for MWM cannot be reached. | AIA error handling. | E-mail notification and worklist entry | ||
D11 | Internal failure in the MWM Ack ABCS | AIA error handling | E-mail notification and worklist entry |