Product Could Not Be Detected Before That Product Is Suspended
Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 184.108.40.206.0
Information in this document applies to any platform.
***Checked for relevance on 29-April-2011***
Rateplan could not be detected when rating a call in the period that should be still active, i.e. a product purchased on 10 Feb 2008 and suspended on 12 Feb 2008, the product could not be detected when a call started on 11 Feb 2008, and the call was rated with other (default) rateplan.
Steps To Reproduce:
- Purchased a product for telephony on 10 Feb (ex: rateplan-X) and priority is 100.
- Suspended that product on 12 Feb
- Rate a call started on 11 Feb
It should be rated with rateplan-X, but the call is actually rated with the default rateplan (ex: rateplan-Y)
with priority 0.
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