Scribd
Upload
130 views1 page

Advance Collections

The Universal Work Queue in Oracle Advance Collections(R12) is not showing complete details for delinquent accounts. Fresh delinquencies are not visible due to a new parameter called "Diagnostic Maximum Records" that was added during an upgrade, which limits score evaluation to only 1000 records. To fix the issue, the program needs to be run without this parameter or the concurrent request set triggering the program needs to be modified to remove the 1000 record limit.

Uploaded by

harishna
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
130 views1 page

Advance Collections

The Universal Work Queue in Oracle Advance Collections(R12) is not showing complete details for delinquent accounts. Fresh delinquencies are not visible due to a new parameter called "Diagnostic Maximum Records" that was added during an upgrade, which limits score evaluation to only 1000 records. To fix the issue, the program needs to be run without this parameter or the concurrent request set triggering the program needs to be modified to remove the 1000 record limit.

Uploaded by

harishna
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Title: Universal Work Queue in Oracle Advance Collections(R12) shows incomplete details in Delinquent Account Node

Author: Mayank Daga (Motorola Mobility India Pvt. Ltd.) Date: 25.05.2012 Applies to: Oracle Advanced Collections R12 Symptoms: Fresh delinquencies are not visible in the Universal Work Queue in delinquent account node and the fresh delinquencies for the customer are not being calculated although there exists fresh delinquent transactions against the same customer Past delinquencies are still visible in the Work Queue in Delinquent Account Node, although Custom/Account is not delinquent any longer Stale/Old information is available on Universal Work Queue in Delinquent Account Node

Cause:

The reason is that the new parameter(added during upgrade of 11i to 12i) 'Diagnostic Maximum Records' in the program IEX: Scoring Engine Harness has a default value of 1000 Reason: This way it limits the score evaluation to only 1000 records(as it internally sets the Universe Size as 1000) Diagnostic Maximum Records does specify that the records should be processed in multiples of 1000, but instead it limits the entire set that needs to be processed to 1000 Fix: 1. The program needs to be run with this parameter blank to have all delinquencies picked up 2. Alternatively, if you are running/scheduling the IEX: Oracle Collections Concurrent Request Set, changes ought to be made in that stage within the request set which triggers IEX: Scoring Engine Harness and the default condition from the parameter 'Diagnostic Maximum Records' needs to be removed, so that the program evaluates the delinquencies completely.

You might also like