Duplicated Event Reversal Generated When A Product Inactivation Occur On Collections Process
(Doc ID 2385005.1)
Last updated on JUNE 13, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
After the upgrade to 7.5 Patch set stream, issue was encountered when a product is deactivated by the collections process.
Because of this issue the already charged event period is reverted two times.
Below are the steps to reproduce this issue:
1.Create a proratable cycle_forward product with one month inadvance billing enabled
2.Move the pin_virtual_time to Jan 1st
Create a customer and purchase the above product (DOM will be set to 1)
3.Move the pin_virtual_time to Feb 5th:
Inactivate the service
4.Change DOM using below opcode and flist
# op_cust_set_billinfo input flist
# number of field entries allocated 20, used 3
0 PIN_FLD_POID POID  0.0.0.1 /account 1906531 10
0 PIN_FLD_PROGRAM_NAME STR 
0 PIN_FLD_BILLINFO ARRAY  allocated 20, used 3
1 PIN_FLD_POID POID  0.0.0.1 /billinfo 1906915 21
1 PIN_FLD_ACTG_FUTURE_DOM INT  5
5.Move the pin_virtual_time to Feb 10th:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!