Inconsistent Behavior Of Sub-Balances With Grantable And Proratable Flags (Doc ID 887592.1)

Last updated on SEPTEMBER 21, 2012

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 to 7.3.0.0.1 [Release 7.3.0]
Information in this document applies to any platform.
***Checked for relevance on 21-Sep-2012***

This problem can occur on any platform.

Symptoms

-- Problem Statement:
Different behavior of 'sub-balance bucket validity' is observed when proration flags are set in
proration tab in following ways but unset in balance impact tab.
Case 1 - "Calculate the charge for the amount used" and
Case 2 - "Charge for the entire cycle"

Here are the two cases:

Case-1 (expected)

Daily cycle forward fee (custom event) with proration settings: "Calculate the charge for the
amount used" for purchase and cancel in proration tab.
In balance impact tab "Proration" flag is unset, grantable flag is set. start_date = 1 event
cycle, end_date = 1 day.
Offer is bought for /service/telco/data.
If account's or service's status is changed to inactive the validity period end date is set to the
cancellation date. This is the expected behavior.
If account's or service's status is changed to active the validity period end date is set to event
cycle end date. This is the expected behavior.

Case-2. (current issue)

Daily cycle forward fee with proration settings: "Charge for the entire cycle" (or any other proration setting) for purchase and cancel in proration tab
In balance impact tab "Proration" flag is unset, grantable flag is set. start_date = 1 event
cycle, end_date = 1 day.
Offer is bought for /service/telco/data.
If account's status is changed to inactive the validity period is NOT changed but another
sub-balance array/bucket is created with the validity period from the cancellation date till the
date gratable period (1 year in this case). This is the incorrect behavior.

If account's status is changed to active the validity period is NOT changed but another
sub-balance array/bucket is created with valdity start = validity end date. This is the incorrect
behavior.

The problem reported is in case-2. Here after cancellation the validity period should be set to 1
event cycle and there should not be any extra bucket generated.

Cause

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