SI: SI Contracts Logged Into Exception On BOD Is Deleted In EOD Batch.
(Doc ID 2668253.1)
Last updated on NOVEMBER 28, 2022
Applies to:
Oracle FLEXCUBE Universal Banking - Version 12.2 and laterInformation in this document applies to any platform.
Symptoms
SI: SI Contracts logged into exception during BOD are deleted in EOD batch which is not correct.
ACTUAL BEHAVIOR
---------------
1) SI contract of payment type is created to be executed on BOD. The contract is created such that the Action Code is ‘Full Pending’ and the debit account doesn’t have sufficient balance to cover the payment amount.
2) On Running EOD system correctly rejects the payment and the error is logged in cstb_contract_exception.
3) However, on running the same day EOD system deletes the exception log for the contract rejected during BOD. Any reports taken to identify reason for failure is missing.
EXPECTED BEHAVIOR
-----------------------
System should not delete the record from cstb_contract_exception
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 |
| References |