Product Is Rated With Incorrect Scale When Cycling After charged_from/to Dates Have Been Changed (Doc ID 1602376.1)

Last updated on AUGUST 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

On : BRM 7.5 PS4 (Patch 16429299) and following patches (upgraded from 7.2.1):
  Patch 17026131
  Patch 17175573

Product is rated with incorrect scale at billing after charged_from and charged_to dates have been changed. There are customizations involved.

ACTUAL BEHAVIOR
-------------------------------
At the end of the first recurring cycle of the 2nd product, the service is charged with a scaled down value for only 1 month despite it being a quarterly product.

EXPECTED BEHAVIOR
-----------------------------------
At the end of the first recurring cycle of the 2nd product, the service should be charged for the entire full term of the product, in this case 3 months.
Note that this worked correctly in 7.2.1.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Create 2 price plans. Both quarterly but 1 ends after 3 cycles (used for commit customer) and the other one has not end date (this will be used during the purchase deal)
2) Created an account using the first quarterly plan on 09/01/2013. Charges and cycle fee dates look good to this point.
3) Move pvt to 10/01/2013 and execute PCM_OP_BILL_MAKE_BILL.
4) Move pvt to 10/10/2013 and called PCM_OP_SUBSCRIPTION_PURCHASE_DEAL. There is a customization in SPEC_CYCLE_FEE_INTERVAL opcode to asses the cycle fee now but set the charged_from_t to the end of the first product. Customized file is also attached.
5) Move pvt to 11/01/2013 and execute PCM_OP_BILL_MAKE_BILL.
6) End of first cycle product. Move pvt to 12/01/2013 and execute PCM_OP_BILL_MAKE_BILL. There is a customization to PRE_FOLD to cancel the product upon next bill run after its expiry. Customized file is attached. The first product has been canceled now and the 2nd product is active.
7) Move pvt to 01/01/2014 and execute PCM_OP_BILL_MAKE_BILL.
8) Move pvt to 02/01/2014 and execute PCM_OP_BILL_MAKE_BILL.
9) End of 2nd product’s first cycle. Move pvt to 03/01/2014 and execute PCM_OP_BILL_MAKE_BILL.


BUSINESS IMPACT
-----------------------
It's impacting QA of the 7.5 upgrade project and might have an impact on the overall schedule.

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