‘Account Stop Correspondence ‘ Transaction Through Events not working
(Doc ID 2853832.1)
Last updated on MARCH 08, 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
‘Account stop correspondence ‘ transaction through events not working as expected.‘Account stop correspondence ‘ transaction is setup at event configuration.
As per expectation stop correspondence indicator should get updated at account level , however primary customer account stop correspondence is getting updated
ERROR
-----------------------
01/05/2022 13:04:30 SessionID=1932730 AppUser=INTERNAL OSUser=oracle
OFSLL Error Msg :
Ora Error Code : 904
Ora Error Msg : ORA-00904: "TNM_ACC_STOP_CORR_IND": invalid identifier
Context : Error in : evatnm_en_100_01.post_batch_tnm
Context : Error in : evatnm_en_100_01.process_tnm_action
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create an account where stop correspondence value is empty for account level and customer level in the Account information
2. Configure the event setup to post ‘Account stop correspondence ‘ transaction
Event Setup
Event Code Entity Type Event Type
POST_MAT_STMT_COND Accounts Event To process Actions when new account condition is created for an account
Event Criteria
Query Name Query Description
ADD_Bankruptcy ADD_Bankruptcy
Criteria details
Parameter Operator Value
Account Condition Code Equals BKRP
Action Action code Enabled
Post non monetary transaction Stop Correspondence Y
3. Post the condition on the account
Account Condition Condition start dt Follow up dt
BANKRUPTCY 03/01/2018 01/05/2022
4. Check whether account level stop correspondence posted to the account
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 |