Managing Work Order Failure Scenarios
The following sections describes failure scenarios and possible resolutions.
CC&B Originated Message - Requester Failure
The Oracle Utilities Customer Care and Billing create message can fail before getting to the target queue(s) because of the following:
• Failure in Oracle Utilities Customer Care and Billing requester.
• EBS is not reachable.
• One of the target queues is down.
The NDS Record is in error. User can set the NDS record to retry after the issue is resolved. This causes the message to go out again from Oracle Utilities Customer Care and Billing.
CC&B Originated Message - Provider Failure
If the Oracle Utilities Customer Care and Billing message reaches the target queue(s) and then it either fails in Oracle Utilities Work and Asset Management v1.9.1.x or Oracle Utilities Mobile Workforce Management provider or there is a business error, Oracle Utilities Customer Care and Billing receives the acknowledgment. The –acknowledgment is visible in the FA log UI and the NDS record is in Completed state. The same message can be sent again after resolving the issue by setting the status in NDS back to pending. If the resolution of the issue requires the FA to be updated then Oracle Utilities Customer Care and Billing user can update the FA and save the changes, which triggers an outbound update message.
In case of any provider error also standard AIA error notification framework is invoked - e-mail sent and work list entry created to notify users of the failure.
WAM/ODM v2.1.x Originated Message - Requester Failure
The Oracle Utilities Mobile Workforce Management create message can fail before getting to the target queue(s) because of the following:
• Failure in Oracle Utilities Work and Asset Management v2.1.x requester.
• EBS is not reachable.
• One of the target queues is down.
The Activity record is in error. User can resend the activity from the Activity page by clicking on the Resend button after the issue is resolved. This causes the message to go out again from Oracle Utilities Work and Asset Management.
MWM Originated Message - Provider Failure
If the Oracle Utilities Work and Asset Management v2.1.x message reaches the target queue(s) and then it either fails in Oracle Utilities Mobile Workforce Management provider or there is a business error, Oracle Utilities Work and Asset Management v2.1.x does receive an acknowledgment. In addition to sending an ack back to Oracle Utilities Work and Asset Management, standard AIA error notification framework is invoked - e-mail sent and work list entry created to notify users of the failure.
MWM Originated Message - Requester Failure
The Oracle Utilities Mobile Workforce Management create message can fail before getting to the target queue(s) because of the following
• Failure in Oracle Utilities Mobile Workforce Management requester.
• EBS is not reachable
• One of the target queue is down
The Outbound message is in error. Oracle Utilities Mobile Workforce Management created a Sync Request record for the new activity, status update, or activity completion outbound message that failed. The F1-SYNRQ batch process executes a monitor algorithm that regenerates and sends the outbound message back to the integration layer.
The monitor will retry the Sync Request record until the outbound message is successful.
MWM Originated Message - Provider Failure
If the Oracle Utilities Mobile Workforce Management message reaches the target queue(s) and then it either fails in Oracle Utilities Work and Asset Management v1.9.1.x or CCCB provider or there is a business error, Oracle Utilities Mobile Workforce Management does not receive any acknowledgment. Standard AIA error notification framework is invoked - e-mail sent and work list entry created to notify users of the failure.
WAM v1.9.1.x Originated Message - Requester Failure
When Oracle Utilities Work and Asset Management v1.9.1.x creates a service request and the message fails before getting to the target queue(s). Oracle Utilities Work and Asset Management v1.9.1.x user receives an error on the Oracle Utilities Work and Asset Management v1.9.1.x UI. After resolving the root cause of the failure the user can try re-sending the message by setting the status of the service request to Created and back to Active. This sends another create message from Oracle Utilities Work and Asset Management v1.9.1.x.
WAM v1.9.1.x Originated Message - Provider Failure
If the Oracle Utilities Work and Asset Management v1.9.1.x message reaches the target queue(s) and then it either fails in Oracle Utilities Customer Care and Billing or Oracle Utilities Mobile Workforce Management provider or there is a business error from one or both the applications. The Oracle Utilities Work and Asset Management v1.9.1.x service request can be populated with an external ID. An e-mail notification is sent to the e-mail address indicated during configuration to notify users of the failure. The Oracle Utilities Work and Asset Management v1.9.1.x user can cancel the service request in Oracle Utilities Work and Asset Management v1.9.1.x and re-create the service request after ensuring that the root cause of the error has been fixed.
Provider Application Connection Failure - Resend from Queue
If the message reaches the target queue(s) and then it fails to reach the Provider because either of the two applications is down the message stays in the error queue of the provider. The message in the error queue can be resent from that queue to the application once the application comes up by the Administrator by running AIA provided Message Resubmission Utility script as explained in the previous section.