ISSUES WHEN ECA AND SANCTION ENABLED FOR THE CUSTOMER.
(Doc ID 3031846.1)
Last updated on AUGUST 07, 2024
Applies to:
Oracle Banking Payments - Version 14.7.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.7.0.3.0 version, Implementation Support
ECA and sanction enabled for the customer.
Scenario 1)
----------
1. Day 1 - Upload pacs008 and transaction moved to sanction queue. (24/11)
2. Day 2 - Approved from external sanction system response and EAC response from External system (27/11)
3. Underlying Transactions are processed.
Issues:
----------
1. Instruction date and Transaction date remain unchanged.
2. Transaction date showing as back dated (24/11) even when transaction is approved from SC on day2 (27/11).
Expected:
----------
1. Activation date should be updated as SC/EAC response is received on day2 (27/11).
2. Transaction date should be current application date (27/11) and accounting value date should be back dated (24/11).
----------
Scenario 2)
----------
1. Day 1 - Upload pacs008 and transaction moved to any of the exception queue (Auth limit queue, sanction queue, EAC queueu) 24/11)
2. Day 2 - Approved from Transaction from queue from OBPM queue screens (27/11). System display an override message that 'Activation date will be re-derived'.
3. Underlying Transactions are processed.
Issues:
----------
1. Instruction date also re-derived in PADIVIEW as on Day2 (27/11).
2. Value date in accounting entries also displayed day2 date (27/11).
Expected:
----------
1. Transaction date should be current application date (27/11) and accounting value date should be back dated (24/11).
2. Only Activation date should be re-derived. Instruction date should not be re-derived
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 |
Cause |
Solution |