Wrong Dates Set in SET_PRODINFO in Case of In-advance Billing Charges
Last updated on APRIL 13, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Core Billing.
When cancelling a product with "in-advance billing" set on an account with quarterly billing frequency which was already billed with BillNow, wrong values are given to PIN_FLD_CYCLE_START_T and PIN_FLD_CYCLE_END_T fields in cycle_forward_monthly events created to refund already billed recurring charges.
Two "problematic" cycle_forward_monthly events :
Date of "Tue Jan 30 00:00:00 2018" is wrong as it's not the end date of a valid cycle interval. It should be date "Feb 1" instead.
The issue can be reproduced at will with the following steps:
1. Move pvt of 27-Dec-2017
2. Create account with quarterly billing frequency for which "current billing cycle" will be 27.12.2017-01.04.2018. Product activated will have "in-advance billing" with advance_billing_unit="month" and advance_billing_offset=3
Initially purchase, usage, and cycle end date are set as Never
3. Move pvt on 2-Jan-2018
4. Run BillNow for this account
Recurring charges applied as follows
Dec 27 00:00:00 2017 to Jan 1 00:00:00 2018 [proration]
Jan 1 00:00:00 2018 to Apr 1 00:00:00 2018 [Current Cycle]
5. Move pvt on 8-Jan-2018
6. Set purchase, usage, and cycle end date to '8-Jan-2018'
opcodes[PCM_OP_SUBSCRIPTION_SET_PRODINFO and PCM_OP_SUBSCRIPTION_CANCEL_PRODUCT] were called
During SET_PRODINFO call we observed wrong dates set in refund of recurring charges
Jan 8 00:00:00 2018 to Jan 30 00:00:00 2018 [one event]
Jan 30 00:00:00 2018 to Apr 1 00:00:00 2018 [Another event]
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