How To Handle Very Large Amounts of /item (Doc ID 1391143.1)

Last updated on DECEMBER 17, 2024

Applies to:

Goal

One user requires many different kind of items. Suppose there is a telco company and end users make international calls to any countries. Each of those calls may be on either peak or non peak, so at the moment of invoicing, there would be a huge performance penalty just for accessing the event_t, journal_t, or event_bal_impacts. So the values should be calculated before get into the item each time a new call is made. In this way, when generating invoices, there is no need to look beyond items.

The user 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).

Items would be:
/item/calls/international/us/peak
/item/calls/international/us/non-peak
and so on...

Please provide a good design approach for this.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.