Last updated on JULY 18, 2017
Applies to:Oracle Public Sector Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
ETPM Collections Case Monitor (C1CLPR) does not create To Do's as expected in v22.214.171.124.0
The expected process flow is as follows for the Collection Case.
The LRA will print a letter – this is shown in the log. After serving the letter to the Taxpayer, the LRA records the serve date using a custom script that records the date as a custom Customer Contact.
When C1-CLCPR runs, the script will look at the last entry in the Customer Contact Log. If this entry is for the letter that has been served, it will not look at the time since this action. If this is more than 7 days, a To Do will be created for the Collections User to indicate that there was no action on this Collection Case since the letter has been served.
A second letter is then be printed and served to the taxpayer. Again C1-CLCPR runs and checks the last log entry. If this is a letter served entry and it is more than 7 days in the past, a second To Do is created.
This triggers a third letter to be sent and served. When C1-CLCPR runs on the third time, it again verifies that more than 7 days lapsed before a third To Do is created.
We use Time Travel to simulate the three 7 day periods. We created 5 test cases and ran C1-CLPR 3 times without closing any To Do's or any other action. The first and second sets of To Do's are created as expected. The third set of To Do's are created only when the second set of To Do's was closed prior to the C1-CLCPR run. Thus If we close 3 of the second's run To Do's; the process created 3 To Do's during the third run of C1-CLCPR.
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