Incorrect Due Date For Collection Actions During Replace Scenario
Last updated on DECEMBER 13, 2017
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 : 18.104.22.168.0 version, Core Billing
After Replace Scenario, Due Date Calculation is not similar to when the account entered into collections.
Some of the collections actions share same due date because of wrong due date calculation.
During collections entry, Action 3 took the Due Date as a relative date based on Action 2.
During replace scenario, Action 3 took same Due Date as Action 2 based on config, instead of taking a relative date based on Action 2 which is not expected.
Steps to replicate:
The issue can be reproduced at will with the following steps:
1.Let's consider a collections scenario with below 3 collections actions.
Action 1's Due_Day = 1 day
Action 2's Due_Day = 2 days
Action 3's Due_Day = 4 days
2.Say, if the account enters collections on Aug 31, 2017 (Thursday), then the following collections actions are generated.
Action 1 with Due Date as --> Sep 1, 2017 (Friday)
Action 2 with Due Date as --> Sep 4, 2017 (Monday)
Action 3 with Due Date as --> Sep 6, 2017 (Thursday)
3.If replace scenario is performed on Aug 31, 2017 (Thursday), the following collections actions are generated.
Action 1 with Due Date as Sep 1, 2017 (Friday)
Action 2 with Due Date as Sep 4, 2017 (Monday)
Action 3 with Due Date as Sep 4, 2017 (Monday)
The expectation is to have same behavior for both Collections Entry & Replace Scenario.
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