Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.3.1 to 7.5.0]
Information in this document applies to any platform.
At customer end, BRM rating performance getting worse and worse (pin_bill_day process is too time-consuming).They think accumulation of data on core billing table such as "ITEM_T" would be major cause. So customer would like to purge non-event class such as ITEM_T, BILL_T, JOURNAL_T.
Customer would like to know the specific side effects of purging the closed item data (status = 4) from ITEM_T by force with some customer script.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms