My Oracle Support Banner

Inactivation End-Dates Sub-Balance Validity (Doc ID 797973.1)

Last updated on SEPTEMBER 01, 2020

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 and later
Information in this document applies to any platform.

Goal

If an account or service is inactivated, refund cycle forwards caused by the inactivation lead to balance group sub-balances being end-dated (valid_to changed to midnight of the current day). Reactivation leads to the total-balance being spread out of sub-balances with different valid_from/valid_to dates.

Below is the scenario described:

- create account with plan (MCF product, Balance Impact - one non-currency resource. Scaled Amount=100.00) on 18th Mar. A MCF in the product adds 100 to resource tokens. At this point there's one bucket with validity 18-Mar to <null>, balance 100.

- move virtual time forward one month and run billing. There's still the same bucket, but now with balance 200.

- inactivate account. The MCF is cancelled, and the bucket is end-dated. Bucket has validity 18-Mar to 18-Apr and balance 100.

- activate account. The MCF is charged again, the original bucket doesn't change, but there's a new bucket with validity 18-Apr to <null>, balance 100.

So, at this point we've got two buckets, each with a balance 100. The current balance (as shown by CC) is 100, because the first bucket's validity doesn't include today.

What may be desirable is just one bucket with balance 200 that means Customers may like to guarantee that resources have only one sub-balance which is "eternally" valid.

How to get the desired behaviour?

Solution

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
Goal
Solution
References

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