Wrong Validity Period After Making Backdated Purchase
(Doc ID 1552500.1)
Last updated on MARCH 21, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.4.0]
Information in this document applies to any platform.
A wrong validty period is found when performing backdated purchase, under the following scenario:
01.06.2012 - Create customer and subscription account with 1st as billing date and with any monthly cycle arrear charge deal (This deal is not dependent to the current issue and any currency charging deal can be purchased just to track the billing)
01.07.2012 - do blling
01.08.2012 - do blling
01.09.2012 - do blling
01.10.2012 - do blling
01.11.2012 - Purchase a free bundles deal with start as 21.06.2012 (this start date can be any date older than 2 months, i.e any date in Aug or earlier) - Here two free bundles provided without aligning dates to monthly cycle from 21/06/12-21/07/12 and 21/07/12-21/08/12.
01.11.2012 - do billing - Here two more bundles provided from 21/08/12-01/12/12 (i.e one bundle covering more than 3 month period) and from 01/12/12-01/01/13
Below are more details
1) created an account say 1884119 on dec 15th with DOM set to 1
2) Service creation, with opcodes input like:
3) perform product purchase with effective date set to dec 14th.
a) sub-balances are created on dec 14 to jan 14 2013 jan 14 to feb 14 2013. NOTE - There is a discrepancy here
4) perform billing till april 1st
a) sub-balances are created on Apr 1st do a purchase deal back dated to jan 23rd
Jan 23rd feb 23rd
feb 23rd mar 23rd
5) move pvt to may 1st and run billing
a) we get 2 sub balalance buckets
Mar 23 to Jun 1st <There is a discrepancy here>
Jun 1st to July 1st
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document