New Features Required In Pin_monitor_balance (Doc ID 1547114.1)

Last updated on OCTOBER 03, 2017

Applies to:

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

Symptoms

On : BRM 7.4.0.0.0 version, Balance Monitoring Manager

      REL publishes any monitored balance impact data to the monitor queue for 0 rated events also.

Due to this more number of events will be lying in the monitor_queue_t unprocessed. The pin_monitor_balance utility will be very slow since it does an 'order by' created_t on all the unprocessed events.

To better handle this, we are looking for the following OOTB features :

1. Ability to run pin_monitor_balance for a date range.
2. The failed records should have some other status so that these records can be managed separately, currently we see only 1 or 0 status.




Cause

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