How To Handle Very Large Amounts Of /item (refer to Note 1148518.1)
(Doc ID 1391143.1)
Last updated on JUNE 29, 2022
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
From <Note 1148518.1> (Impossible To Load Rated Usage because Of ITEM_POID_LIST Size Limit), there is only a workaround provided when ITEM_POID_LIST needs to be more than 2000 characters in length.
We need a different solution as our customer requires many different kind of items. Suppose we have a telco company and customers make international calls to any country. Each of those calls may be either peak or non peak. Customer wants to be able to have one cumulative item per country/peak_or_non_peak. Suppose there are 200 countries, and two different items per country (maximum).
Customer make many international calls, so at the moment of invoicing, there would be a huge performance penalty just for accessing the event_t, journal_t, or, even more, event_bal_impacts. So the values should be pre-calculated into the item each time a new call is made. In this way, when generating invoices, we do not need to look beyond items.
Items would be:
and so on...
Can you provide a good design approach for this?
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