BRM 12 PS1 Fix is Not Working for Future-Dated Purchased Discount Cancellation
(Doc ID 2522635.1)
Last updated on APRIL 22, 2019
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 Oracle Communications Billing and Revenue Management (BRM) version 18.104.22.168, when a future-dated purchased discount is cancelled, the dates are not aligned correctly: /cycle/purchase/usage END_T < /cycle/purchase/usage START_T.
The scenario is as follows: At the time of INITIATE BILLING the products and discounts are purchased with future date. Once the provisioning is completed in the fulfilling flow, the purchased product and discounts dates are set to the date when provisioning is completed. When there is service cancellation after INITIATE billing, the cycle dates for purchases discount are incorrectly set: cycle/purchase/usage END_T < cycle/purchase/usage START_T.
It is expected that at the time of discount cancellation, only END_T is updated. The expectation is that the START_T as well as END_T should be set to cancellation dates.
The issue can be reproduced at will with the following steps after logging into Customer Center and run the following steps:
1. Create Account A1 (Account creation date is 10-JUN-2018)
- Service S1
- Purchase products in future date (CYCLE_START_T => Fri Feb 28 00:00:00 2020, CYCLE_END_T => 0)
- Purchase discount in future date (CYCLE_START_T => Fri Feb 28 00:00:00 2020, CYCLE_END_T => 0)
2. Once account is created successfully, cancel the Service S1 (Cancellation can happen on Thu Feb 28 06:09:29 2019)
Verify the purchased product date (CYCLE_START_T => Thu Feb 28 06:09:29 2019, CYCLE_END_T => Thu Feb 28 06:09:29 2019)
Verify the purchased discount date (CYCLE_START_T => Fri Feb 28 00:00:00 2020, CYCLE_END_T => Thu Feb 28 06:09:29 2019)
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