Incorrect VALID_TO Of Non-currency Resource Sub-balance (Doc ID 2170763.1)

Last updated on SEPTEMBER 08, 2023

Applies to:

Goal

On : 7.5.0.12.0 version, Balances

There is a problem wherein valid_to date is set incorrectly for a specific sub-balance.

Scenario:

*  Account purchases offer valid for several days (e.g. 7 days) where both start_t and end_t of the offer purchased are not the account's BDOM (billing day of month).
*  The problem seems to be the end date of the offer.
*  In spite of the offer's end date being set prior to account's BDOM, the "valid_to" of the granted sub-balance resource is set to account's BDOM.

Steps to reproduce:

1. Set Pvt=28.11.2015 (dd.mm.yyyy)
    create BA (billing account) with BDOM 8,
    purchase Basic Offer1 start_t = 08.12.2015
2. Set pvt=08.01.2016
    Run opening billing to generate charges
3. Set pvt=09.01.2016
    Run closing billing to finalize bill (opening billings date + delay period which is 1 day)
4. Set pvt=10.01.2016
    purchase Optional Offer2 granting free resource 2030012 with validity for one week, start_t = 13.01.2016, end_t = 20.01.2016
5. Set pvt=13.01.2016
    Run pin_cycle_fees -cycle_fees to apply cycle_forward fees
6. Set pvt=15.01.2016
    Rate CDRs with timestamp within validity of Offer2-> CDRs are consumed from free resource 2030012
7. Set pvt=22.01.2016
    Rate CDRs with timestamp after validity of Offer2 -> CDRs are NOT consumed from free resource 2030012

Actual result :

When purchasing Offer2 in step 4, for one week, sub-balance with resource 2030012 is granted for period valid_from = 13.1.2016 valid_to =8.2.2016 (end of the period).

Expected result :

Since the offer granting this resource is valid only until 20.1.2016, expecting the valid_to of the resource sub-balance to be set to 20.1.2016 as well.

Note that CDRs rated between 13.1.2016 and 20.1.2016 are consumed from resource 2030012, and CDRs rated after 20.1.2016 are NOT consumed from resource 2030012. Furthermore, end dates (usage_end_t, purchase_end_t, cycle_end_t) set on /purchased_product object are also correctly set to 20.1.2016.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.