Discounting Did Not Work Properly for Backdated Cancellations of Cycle Arrears (Doc ID 2224337.1)

Last updated on SEPTEMBER 08, 2023

Applies to:

Symptoms

Actual Behavior:

It was required to be able to cancel recurring charge products in the past, i.e. to perform backdated cancellation. This scenario worked fine for cycle forward products in 7.5, but for cycle arrears products, there was an issue. While the cancellation did complete, the events generated as a result were not as what was expected.

Expected Behavior:

For example, an account is created at the start of April, it has cycle forward and cycle arrears products and discounts purchased that have a $10 monthly charge and a 50% discount. For each product each month, events are generated that result in a charge of $5, i.e. $10 - 50% = $5. If the product is cancelled in November with the cancellation backdated to mid-April, one would expect to see inverted cycle fees for the period from mid-April to the current date. These inverted cycle fees should also take the discount into account, i.e. the result should be that for each full month, a credit of $5 should hit the account (-$10 - 50% = -$5). These credits would all hit the bill in progress in November.

This was indeed what happened for cycle forward. But for cycle arrears, while the product was cancelled and inverted events were generated, they still have the full $10. The discount was NOT present. It seemed that the discount information was not populated on the event prior to rating for some unknown reasons. So, instead of triggering op_rate_and_discount_event and redirecting to PCM_OP_RATE_DISCOUNT_EVENT to invoke the Real Time Discounting Pipeline, only rating occurred with no discounting.


Steps to reproduce:

1. Purchase cycle arrears discount (-10%) on 1st April 
2. Purchase cycle arrears product on 1st April configured to charge $100 per month 
3. Run billing on 1st May. This charges $100 - 10% = $90. 
4. Run billing on 1st June. This charges $100 - 10% = $90. 
5. Cancel the PRODUCT only backdating the cancellation to 1st May. 
    Expect BRM to apply the discount (which is still there) to the negative cycle generated as part of the cancellation. So that the "refund" the customer gets back is -($100 - 10%) = -$90, which is exactly what it was originally charged. Instead, the discount is not even listed in the list of discounts passed to the main rating and discounting opcode. 

Changes

Cause

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