Partition Pruning In Invoicing (Doc ID 1360911.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.2.1.0.0 to 7.2.1.0.0 [Release 7.2.1]
Information in this document applies to any platform.
Checked for relevance on 2-Dec-2014

Goal

The performance of invoicing application is getting degraded as the number of events being processed by invoicing application is increasing on monthly basis.

The following query (retrieves events for the items) has been identified in invoicing to be severely impacting the performance:

select distinct event_t.poid_DB, event_t.poid_ID0, event_t.poid_TYPE, event_t.poid_REV, event_t.end_t, event_t.sys_descr, event_t.rerate_obj_DB, event_t.rerate_obj_ID0, event_t.rerate_obj_TYPE, event_t.rerate_obj_REV, event_t.invoice_data, event_t.timezone_adj_end_t, event_t.rated_timezone_id, event_t.item_obj_DB, event_t.item_obj_ID0, event_t.item_obj_TYPE, event_t.item_obj_REV from event_t ,item_t where item_t.ar_bill_obj_ID0 = :1 and item_t.poid_ID0 = event_t.item_obj_ID0 and event_t.poid_type in( select type_str from config_invoice_event_types_t where obj_id0 = 102 )


Partition-based search should be used in invoicing. Is there a patch for 7.2.1 to have partition pruning active for this query during invoicing?

Solution

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