ADM Select Record Picking Accounts With Last Credit Review Date As Null, Even When The Minimumreivew
(Doc ID 3014057.1)
Last updated on APRIL 05, 2024
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.8.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 2.8.0.0.0 version, ENV - Environment
ACTUAL BEHAVIOR
---------------
ADM Select Record Picking Accounts with Last Credit Review Date as null, even when the minimum review days parameter as 'N'.
Batch job 'ADM' is configured with the minimum review days parameter as 'N'. The job is expected to process only the records present in the ADM review schedule table. But after the upgrade from 2.6 CC&B to 2.8 CC&B, ADM is picking extra records with the last credit review date field as null.
The SQL causes this issue in the select record algorithm. The condition to check for ACCT.CR_REVIEW_DT is null is becoming true irrespective of the minimum review days parameter value.
The account id in the log provided has no entry in the ADM review schedule table, but the last credit review date is null.
EXPECTED BEHAVIOR
-----------------------
The ADM should select record-picking accounts with the Last Credit Review Date as null
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Set the “incMinDaysRvw” to N, on the ADM batch.
2. Go to the test account and check if the “last credit review date” is blank
3. Run the ADM batch job
4. The batch job ran without any issues.
5. Notice that after the batch was run, the last Credit Review Date was added (it has the same date as when the batch was run).
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |