Last updated on JULY 05, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Checked for relevance on 5-Jul-2017.
An incorrect behaviour has been observed in the following scenario:
1. 2013/09/02 Account create
2. 2013/10/30 Buy a product, during which proratable flag was incorrect, i.e. not set
3. 2013/11/12 Account suspended
4. 2013/12/22 Account reactivated
5. 2014/01/24 Corrected product configuration loaded (set proratable flag)
Fix on audit entries related to incorrect configuration was applied (AU_RATE_BAL_IMPACTS_T.flags set to 2)
Other configuration details:
-fm_bill change_start_time_on_activation flag was already set to 0.
-cycle_arrear_proration flag in pin.conf is not used.
-proratable flag in configuration of used product is set (after fix applied in January - earlier it was not set)
-purchase/cancel proration information in product configuration is set to 'Calculate the charge based on amount used.'
6. 2014/01/26 Account suspended (or terminated)
Amount calculated for refund after last suspension is incorrect. The amount should be calculated as some percentage of full charge period, where full charge period is 2013/12/01 - 2014/01/31; instead, the amount seems to be calculated like full charge period was 2013/12/22 - 2014/01/31, i.e. starting from last reactivation.
Could you please explain why amount was computed incorrectly?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms