(Doc ID 2116343.1)

Last updated on MARCH 29, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.5.0]
Information in this document applies to any platform.


On : version, Pricing

While getting the product details for a given service type using PCM_OP_PRICE_GET_PRICE_LIST, the user observed that, the opcode reads the products for the service type which is fine, but for all other information like rateplan, rate, selector etc., it reads entire data from DB and then applies logic to form the obtained products' rate details.

The user needs to know why does the opcode fetching the entire rateplan, rate data when only for the given service type is wanted?
This is impacting the performance of this opcode when the DB has huge pricing data.


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