Order Create, Update or Cancel from Oracle Utilities Customer Care and Billing | |
Triggering Event | Creation, Update, or Cancellation of a field activity in CC&B with a Dispatch Group that is associated to an external system (this is controlled by an algorithm on Dispatch Group). |
Retry for Business errors | If any of the target applications returns a business error while processing the inbound message, a negative acknowledgment is returned to CC&B. CC&B can be configured to create a To Do Entry on negative acknowledgments. • If the error is caused because of missing configuration information, the user can fix the issue then resend the original message by changing the status of the message back to Pending. This is done on the Oracle Utilities Customer Care and Billing Notification Download table (using the Oracle Utilities Customer Care and Billing user interface). This sends another create, update or cancel message. • If the error requires that something is changed on the field activity, the user can make updates to the data on the field activity in Oracle Utilities Customer Care and Billing to fix the business error. The update causes another outbound message (this time update) to be sent from Oracle Utilities Customer Care and Billing to the target application(s). |
Triggering Event | Creation of a service request in WAM and the status of the service request changed to active. |
Retry for Business errors | The WAM user must cancel the service request and create a new one once the root cause of the issue has been fixed. |
Triggering Event | WAM user updates either schedule date or problem description on the service request that was previously sent to the other application(s). This action sends send an update message. |
Retry for Business errors | WAM user can try resending the Update by making additional changes to the Problem Description on the service request after the root cause of the issue has been fixed. |
Triggering Event | The status is changed on a service request that was previously sent to the other application(s). This sends a status update from WAM. |
Retry for Business errors | Once the root cause of the issue has been fixed, additional Status updates sent from WAM for the same order are sent successfully. |
Triggering Event | The status on a WAM service request is changed to canceled. |
Retry for Business errors | The corresponding orders can be canceled manually in CC&B and/or MWM. |
Triggering Event | The status on a WAM service request is changed to Finished. |
Retry for Business errors | There is no corresponding update required in CC&B or MWM. |
Triggering Event | A WAM service request status changed to Closed and Billable Indicator is true. |
Retry for Business errors | The message can be resent from BPEL or it can manually be created in CC&B. |
Triggering Event | Creation, Update, or Cancellation/Completion of a Activity in WAM/ODM with an activity type that is associated to an external system. |
Retry for Business errors | If the target application returns a business error while processing the inbound message, a negative acknowledgment is returned to WAM. If the error is caused because of missing configuration information, the user can fix the issue then resend the original message by clicking on the Resend button on the Activity page. This sends another create, update or cancel outbound message. If the error requires that something is changed on the Activity, the user can make updates to the data on the Activity in Oracle Utilities Work and Asset Management to fix the business error. The user then clicks on the Resend button that causes another outbound message (this time update) to be sent from Oracle Utilities Work and Asset Management to the target application(s). |
Triggering Event | Creation of Pick-Up Field Order in MWM for a Field Order that was earlier received from the integration. |
Retry for Business errors | If the Order failed in CC&B, the CC&B user can re-process the inbound order from the CC&B upload staging table after resolving the issue that caused it to fail. If the order failed in WAM, it can be re-imported in WAM from the WAM interface table. This requires running an SQL in the WAM database. |
Triggering Event | Field Order status change in MWM send an update to CC&B. |
Retry for Business errors | The CC&B user can re-process the inbound order from the CC&B upload staging table after resolving the issue that caused it to fail. |
Triggering Event | Field Order cancellation in MWM and the integration sends an update. |
Retry for Business errors | If the transaction failed in CC&B, the CC&B user can re-process the inbound order from the CC&B upload staging table, after resolving the issue that caused it to fail. If the transaction failed in WAM, it can be re-imported in WAM from the WAM interface table. This requires running SQL in the WAM database. |
Triggering Event | Field Order is completed in MWM and the integration sends an update. The same update is triggered when a Pickup Order is completed. |
Retry for Business errors | If the transaction failed in CC&B, the CC&B user can re-process the inbound order completion from the CC&B upload staging table after resolving the issue that caused it to fail. If the transaction failed in WAM, it can be re-imported in WAM from the WAM interface table. This requires running SQL in the WAM database. |