This section includes graphical representations of the functionality included for this integration point.

This integration process shows how an order is billed to a customer. An Oracle Utilities Work and Asset Management v1.9.1.x user initiates this process when a service request is Closed and the Bill Customer Flag is set to true. This invokes the Send Billable Charge Web Service to send billable charge information for Time, Materials, and/or Direct Charges associated with the order to the integration layer.

The Oracle Utilities Work and Asset Management v1.9.1.x Requester ABCS accepts the ABM coming from Oracle Utilities Work and Asset Management v1.9.1.x in the integration layer. The ABCS transforms the message into an EBM using the Invoice EBO format and initiates the EBS. The transformation also gets the common ID of the service request from the Cross-reference table and passes it to the EBM. The EBS, which is implemented as a Mediator process routes the message to the appropriated Oracle Utilities Customer Care and Billing Queue. An Oracle Utilities Customer Care and Billing provider JMS consumer listens to the provider queue in Oracle Utilities Customer Care and Billing and invokes the Oracle Utilities Customer Care and Billing Provider ABCS for each message received in the queue.

The Oracle Utilities Customer Care and Billing Provider ABCS calls the following services to create the billable charges:

C1RetCreateBillableChargeSA - This Inbound Web Service retrieves a Billable Charge Service Agreement (SA) for a given Account or Service Point (SP). The status of the SA must be non-closed or non-canceled. If the Account or SP is not associated with a Billable Charge SA, it creates the SA using the CIS Division, SA Type, SA Start Option (if provided) defined in the AIA Configuration File. If only the SP is provided and the SP is linked to more than one account, it picks one of the accounts for the SP and use that to find or create the billable charge SA. Then, it sets the Create To Do Flag to true.

BillableChargeUploadMaintenance - This existing Inbound Web Service creates a Billable Charge Upload record in Oracle Utilities Customer Care and Billing. The Order Common ID is stored as a Line Characteristic in the Billable Charge Line.

F1AutomaticToDoEntry - This existing Inbound Web Service is only invoked if the Create To Do Flag coming from C1RetCreateBillableChargeSA service is true. If Create To Do Flag is true, the integration layer creates a To Do Entry using the To Do Type data defined in the AIA Configuration File after the Billable Charge Upload record has been added to Oracle Utilities Customer Care and Billing. This To Do reminds the user to verify if the billable charge has been created for the correct account because the SP provided is linked to more than one account. New To Do Type is also needed for this TO DO.

If an error is encountered when the message is sent from Oracle Utilities Work and Asset Management v1.9.1.x, the system synchronously responds to the requesting application with an error. The Oracle Utilities Work and Asset Management v1.9.1.x application does not include resend functionality for Create Billable Charge so there is no way to resend the message again. The Billable Charge has to be manually created in Oracle Utilities Customer Care and Billing.

In case of data or technical error in the ABCS like transformation failure or bind fault or some other internal error in the BPEL process, the standard AIA error processing generates an error e-mail notification and work list entry.

In case of remote exception (the target web service cannot be reached even after all the retry attempts configured in the fault policy file are exhausted), the standard AIA error processing generates an error e-mail notification and work list entry. The system rolls back the transaction so that the message stays in the Oracle Utilities Customer Care and Billing Queue and the JMS consumer stops processing the queue. When the target web service is available again, it processes the record from the queue again.

In case of business exceptions from the target application, the standard AIA error processing generates an error e-mail notification and work list entry. After fixing the error, this can be retrieved from BPEL.