Scoring Engine is Marked Successful Even When it Encounters Failure Due to Sequence Error
(Doc ID 2441716.1)
Last updated on MARCH 03, 2020
Applies to:Oracle Advanced Collections - Version 12.1.3 and later
Information in this document applies to any platform.
When IEX: Scoring Engine Harness runs, if the IEX_SCORE_HISTORIES_S sequence runs out of values (reaches Max Value) then the process fails to score the remainder of Customers/Accounts/Bill To/Delinquencies. However, the overall status of the Concurrent process is "S" and therefore it is successful.
If this process is being used in a Request Set, the next concurrent process will run, in this case IEX: Strategy Management which is dependent on Scoring. As a result the IEX: Strategy Management can reassign Strategies when it should not.
You can see in the logfile the following error, yet the status is S
ERROR IN CONCUR: IEX_SCORE: storeScoreHistory: UnExpected ErrorORA-08004:
sequence IEX_SCORE_HISTORIES_S.NEXTVAL exceeds MAXVALUE and cannot be
Profile:Store Score Histories for Transactions: Y
Scoring objects in batch 2 is 0 at 14:56:3535
Completed Scoring objects of type Account
Score Engine: 6 Status: S
The process needs to have a Status of E because when it's run in a request set, the E will cause the remainder of the request set to stop.
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
|1. Bug Summary|
|2. Fixed Files|
|4. Solution Steps|
|5. Screenshots of the new parameter in IEX: Scoring Engine Harness|