Collection Group Owners Have No Pending Collections Actions After Executing pin_deferred_act
(Doc ID 2462801.1)
Last updated on DECEMBER 11, 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.
On all versions of Oracle Communications Billing and Revenue Management (BRM), a Collections Group owner can have no PENDING collections actions remaining after pin_deferred_act is executed. Any previously PENDING actions are moved to WAITING_ON_DEPENDENTS.
As a result, the account(s) is/are incorrectly stuck in collections.
To reproduce this issue:
1. Change the collections target action to 1 or 2
where the ENUM values represent:
2. Have the parent and member accounts enter collections
3. Run pin_deferred_act
A secondary issue also exists where schedule actions for collections group members get stuck in the SCHEDULE_T despite being completed. Over time, this table may fill up with leftover data.
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