Timestamp Rounding Issue During Proration I.E Service Inactivation
Last updated on SEPTEMBER 19, 2016
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 12-Nov-2012***
***Checked for relevance on 25-JUNE-2014***
When testing service inactivation scenarios we found below observation.
Suppose the account is created on 1st Sept '10 and billing cycle is 1-Sept-10 to 1-Oct-10.
The product is having cycle_forward_arrear event.
1) timestamp_rounding entry in the CM pin.conf file is set to 1.
Then we advanced the pin_virtual_time to 15-Sept-10 15:00PM.
Now when we do service inactivation on this date we found that the prorated amount is calculated till 15-Sept-10 00:00:00.
But service inactivation time was 15-Sept-10 15:00PM, so the pro-ration should consider the 15-sept also for calculating the prorated amount.
2) timestamp_rounding entry in the CM pin.conf file is set to 0.
pin_virtual_time set to 15-Sept-10 15:00PM.
Now when we do service inactivation on this date we found that the prorated amount is calculated till 15-Sept-10 15:00PM but based on number of seconds.
Our requirement is the following - if service is inactivated on 15-Sep-10 (anytime), the system should apply a prorated charge for period 1st Sept - 15th Sept.
Currently, the system is calculating the charges only up to 14th Sept.
Is there a solution to meet this requirement in BRM?
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