Deal Cancellation Truncates Sub-Balances Granted By Another Deal (Doc ID 782340.1)

Last updated on JULY 26, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 and later
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

Issue is observed that disturbing behaviour with sub-balances truncated at deal closure.

As explained in the documentation, the PCM_OP_SUBSCRIPTION_CANCEL_DEAL opcode accepts a PIN_FLD_FLAGS that allows to truncate or extend (to the next billing cycle) the validity end date of the deal's sub-balances.

A problem/ambiguity occurs when a sub-balance has been manipulated by products belonging to
SEVERAL deals. A first deal creates the sub-balance, the second makes a simple non-grantable
impact on the same sub-balance : then when we close the second deal the sub-balance created by
the first one is truncated (or extended) whereas this is not expected since the first deal remains
active and untouched. Instead, it is expected to see the sub-balance keeping its end validity date as is.

The MAINTAIN flag extends sub-balances, instead of really maintaining the validity end date as is

Problem is that it cannot distinguish sub-balances for several deals, since we would be very limited when trying to align the validity end date of all these sub-balances to make as if there was a single one.

-- Steps To Reproduce:
1) Define a first deal D1 that, for instance, contains a products that grant a sub-balance starting at "now" and valid for "3 months".

2) Define a second deal D2 that contains a product which performs a NON-GRANTABLE impact on the same resource than D1 did

3) Create an account and a service

4) Purchase D1 on the account at T1 -> a sub-balance is created with validity from T1 to T1 + 3 months

5) Purchase D2 on the account at T2 = T1 + 15 days -> the existing sub-balance is impacted,none is created

6) At T3 = T1 + 20 days, close D2 in CUT mode (for instance) -> the sub-balance is truncated at T3, then is not available anymore for D1 which is still active



Changes

 

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