PCM_OP_COLLECTIONS_REPLACE_SCENARIO Is Not Cancelling Actions If Called In Custom Opcode
(Doc ID 2789465.1)
Last updated on JULY 07, 2021
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) 18.104.22.168.0 version, Collections Manager,
PCM_OP_COLLECTIONS_REPLACE_SCENARIO is not cancelling actions for which due date is before current date, if called from custom opcode.
Here it is observed that the code is setting action status as Pending as below , if PCM_OP_COLLECTIONS_REPLACE_SCENARIO called in some custom opcode from testnap.
PCM_OP_COLLECTIONS_REPLACE_SCENARIO should set cancel actions for which due date is before current date, if called from custom opcode
The issue can be reproduced at will with the following steps:
1) Create Scenario with few actions like SMS, OUTBAR, INBAR, DISCONNECT etc.
2) Complete Action till let SAY INBAR
3) REPLACE SCENARIO --In new scenario, all actions till INBAR needs to get cancelled and Dates for SMS and DISCONNECT will set as per logic written in fm_collections_pol_calc_due_date.c (Logic -- reduce number of days from first actions as a result subsequent actions due date will set as per configuration and first action due date)
4) In above Scenario, if one directly call PCM_OP_COLLECTIONS_REPLACE_SCENARIO from testnap, then code will set status of first action as cancelled:
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