Processing Details
Currently NDS records processing supports Create/Update/Reschedule/Cancel operations only. Additional processing includes the following:
GetNDSRecordsOUCCBUtilitiesEBF is a singleton, which polls the OUCCB_NDS_PROCESS_ACTIVATION table according to the predefined polling frequency. Once this BPEL process is activated, it queries the Oracle Utilities Customer Care and Billing database and extracts NDS records that are ready to be delivered to the integration layer. The query picks up the records in batches, and the batch size is defined in the configuration properties.
For each field activity record found, status is updated to ‘Processing’ in the NDS table and the ProcessNDSRecordOUCCBUtilitiesEBF processing is invoked, specifying the field activity details as parameters.
ProcessNDSRecordOUCCBUtilitiesEBF makes field activity details enrichment by calling the Oracle Utilities Customer Care and Billing web service, ExtractFAInfo .
Next the field activity record is transformed to match the field activity representation in the integration layer. If the transformation is successful, it invokes the ProcessWorkOrderOUCCBUtilitiesReqABCSImpl process. This process completed the field activity processing. It is possible to specify a delay between each field activity record being processed in the configuration properties if necessary.
When the operation is completed successfully, the field activity status is set to ‘Completed’ in the NDS table. If it is not completed successfully the status is set to ‘Error’.
If there is an error, a standard error message is created (message number 9805, category number 11011). This is displayed in Oracle Utilities Customer Care and Billing via the NDS record user interface.
Both BPEL processes detect errors and report them via the AIAASyncErrorHandlingBPELProcess.
The following diagram provides a graphical representation of the general NDS records processing:
General NDS Records Processing