Is There A Way To Avoid Daylight Savings Impacts On Cycle Arrears Proration ?

(Doc ID 1121425.1)

Last updated on JUNE 13, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 14/11/2013

Goal

Daylight Savings Time (+1 hour or -1 hour) has an impact on proration (when we use cycle arrears).
Is there a way to avoid this impact - ie to have proration based on days, not of timestamp.

For example, in March 2010:
• Any period including the night of the 27th-> 28th has 1 hour less.
• The full month (31 days) should be counted as (31 - 1/24)
• Period 22nd->31st should be counted as (9 - 1/24)
• Period 18th->22nd should be counted as (5)
• Period 01st->24th should be counted as (25)
• Period 25th->31st should be counted as (7 - 1/24)


MSISDN Full Period Proration Prorated Price
Price Nb Days Period Nb Days With Daylight (BRM) Withount Daylight
076 586 10 87 35 31 22->31 9 10.13 10.16
076 586 10 87 25 31 18->22 5 4.04 4.03
079 414 49 79 12 31 01->24 24 9.30 9.29
079 414 49 79 35 31 25->31 7 7.87 7.90

 

Solution

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