Posting a call activity to close Bankruptcy Condition Not Updating Stop Correspondence Flag to N
(Doc ID 2901858.1)
Last updated on OCTOBER 11, 2022
Applies to:
Oracle Financial Services Lending and Leasing Cloud Service - Version 14.10.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Account migrated to OFSLL with bankruptcy condition. Posting a call activity to close Bankruptcy Condition Not Updating Stop Correspondence Flag to N at customer level.
EXPECTED BEHAVIOR
-----------------------
System should have updated the STOP CORRESPONDENCE FLAG to ‘N’ both at Customer and Account Level, when call activity is posted to close BKRP condition
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Migrate a legacy account with account condition(Bankruptcy)
2. Check whether the account got migrated with account condition(Bankruptcy)
3. Post a call activity to close the bankruptcy condition
4. Check whether the stop correspondence flag is set to N at account level and customer level
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 |