Cancellation of Future Dated Disconnect is Not Working as Expected.
(Doc ID 2873307.1)
Last updated on APRIL 08, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Cancellation of future dated disconnect is not working as expected.
Below steps can be done to reproduce the issue:
----------------------------------------------------------------------
1. Create an account, service and purchase a Monthly Cycle Forward(MCF) product. [ Pin Virtual Time(PVT): 30th Jan 2022]
-- cycle_forward for 30th Jan-31st Jan is triggered
2. Do a bill run. (1 day delay is configured). [PVT: 2nd Feb 2022]
-- cycle_forward for 1st Feb-28th Feb is triggered
3. Change PVT to 10th Feb 2022, and do a future disconnect.
4. Change CYCLE_END_T using PCM_OP_SUBSCRIPTION_SET_PRODINFO to 28th Feb 2022
-- refund of 1 day is triggered.
5. After few minutes, cancel the future disconnect.
6. Change CYCLE_END_T using PCM_OP_SUBSCRIPTION_SET_PRODINFO to "0", unlimited.
7. Do a bill run. (1 day delay is configured). [PVT: 2nd March 2022]
Expectation: Charges should continue to trigger.
Actual: Charges stops triggering.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |