Optimization Of BILLING_UPDATES Procedure To Improve Billing Performance
(Doc ID 1214663.1)
Last updated on OCTOBER 21, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.4.0]
Information in this document applies to any platform.
During the billing process, the stored procedure BILLING_UPDATES invokes the following sql statement :
In some customer situations, EVENT_POID_LIST is always NULL for all items. This statement always return NULL and takes more time time execute, which leads to billing performance issues. This query is part of CHECK_FOR_TRANSFER_EVENT inside BILLING_UPDATES. The "check_for_transfer_event" procedure is called in order to set AR_BILL_OBJ into the transfer events which are associated with all items for the given ar_bill. Transfer events are created during line transfer operation (when services are moved to different accounts). Setting the AR_BILL_OBJ field into transfer events is provided for performance gain reason. Now in this customer situation the table event_item_transfer_t is empty. Meaning that transfer events are never created.
This is one example where this query can be avoided and performance during billing can be improved.
Similarly, in some customer situations custom item management is in place and so the item number need not be updated during billing.
keeping these requirements in mind, it is expected to :
1. Avoid item number update in the system during billing.
2. Avoid update on transfer events as there is no transfer performed in the system
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document