Cycle Arrears Product Behavior If Purchased And Cancelled In Same Bill Cycle

(Doc ID 2332259.1)

Last updated on DECEMBER 05, 2017

Applies to:

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

Goal

The requirement: Customer want to charge from "product purchase date" to "next bill cycle date", not to the "product cancelled date for cycle Arrear event".

If cycle_arrear_proration parameter is set to 0 then "purchase time proration" setting is used.

 

Consider below scenario:
Set cycle_arrear_proration parameter to 0

Steps followed as below:

Create product of $300 with configuration "Charge for the entire cycle" on cancellation and "calculate the charge based on the amount used " on purchase (having cycle arrear event)

pin_virtual_time -m2 051311102018 --------13th May
Create Account on May 13 11:16:03 2018 and purchase the product

Push pvt: pin_virtual_time -m2 052311102018
Cancel the product ----23rd May

Push pvt : pin_virtual_time -m2 061311102018

Do Billing -13th June

Result: Product is charged $96.77as parameter is set to 0 purchase time proration setting is used.
==========

Here in this example, user purchased the product on 13th May and cancelled it on 23rd May hence it is giving 10 days charges.

==> 300/31*10 = 96.77 $.

But expected result is:  charge it up to 13th June ==> 300/31*21 = 203.22 $.

Solution

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