Collection Action's Status Is Not Correct When Performing Scheduling With Slip Days
Last updated on AUGUST 19, 2013
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
Issue identified on BRM 7.5 PS4, Collections
Issue is that the action's status is not correct when performing scheduling with slip days.
1. Assume that one needs to reschedule the first pending action to be after 10 days and also choose a 'slip days' for the remaining actions as 10 days.
2. The result is that the first action is inserted as waiting for dependency and the second action is inserted as pending.
3. Above that, when one tries to insert an action to be the first action, the action is inserted with status "Waiting for dependency" and all the scenario actions are updated to the same status, which means that we have a scenario with no pending actions.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms