My Oracle Support Banner

Sub-bal Validity is Not Set for Recurring Cycle and Not Expired on Cancellation (Doc ID 2676583.1)

Last updated on MAY 07, 2021

Applies to:

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

Symptoms

On : 7.5.0.22.0 version, Pricing

When customer have a sub-balance validity for an cycle_forward_annual event as EventOccurence 12 Recurring Cycles. This is setting the validity of sub-balance as Event Occurrence-Never Ending(UNLIMITED). 

Then when customer set the purchase instance validity to 7 months. On cancellation(after running pin_cycle_fees and pin_discount_cleanup) it is not setting the end dates to the sub-balances but the products or discounts are getting Cancelled and the sub-balances are still left ACTIVE.

This is causing issue as even after expiry the balances are valid for consumption.
 

Test case 1
--------------
Step 1: Create an account and purchase a product with cycle event and sub balance validity as 'EventOccurence-12 recurring cycles' and purchase validity to 7 months (END_T is 7 months from the START_T)
Step 2: After 7 months cancel the product and run pin_cycle_fees and pin_discount_cleanup.

 

Expectation:
-----------------
Step 1 Expectation was validity of the sub balances is 12 cycles but it is coming as Unlimited(NeverEnding)

Step 2 Cancellation of the product is not setting the end dates of the sub balances but the products or discounts are getting cancelled and sub balances are still left active.

Test case 2
--------------

Step 1 : Purchase monthly cycle arrear product and discount on Jan 1st, bill for 2 months on Feb 2nd and March 2nd.
Step 2 : Cancel both on March 15th. We are passing the end-date to Jan 1(start of cycle) for one of the products, and the other is to be end-dated to March 15th (mid-cycle)
The discounts were cancelled first, and they were cancelled using PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO and PCM_OP_SUBSCRIPTION_SET_PRODINFO with the rate_cut_flag.

Expectation:
-----------------

Scenario 1: For the cancellation to start of cycle, a full refund for both January and February
Scenario 2: For the cancellation to mid-cycle, no refund. The product and discount should trigger the arrear event for the third month as well and charge.

Actual observation:
For scenario 1: A refund of the product for February month, no refund of the discount's charge.
For scenario 2: No refund. The product and discount triggered the arrear event for the third month as well and charged (no issue).


BUSINESS IMPACT
-----------------------
This is causing issue as even after expiry the balances are valid for consumption.

Changes

 

Cause

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
Symptoms
Changes
Cause
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.