My Oracle Support Banner

OBCL14.6_Error Reason For ECA Failures (Error/Rejection) Are Not Captured In Contract Exception Log (Doc ID 2948690.1)

Last updated on MAY 21, 2023

Applies to:

Oracle Banking Corporate Lending - Version to [Release 14]
Information in this document applies to any platform.


On : version, Implementation Support

OBCL14.6_Error Reason for ECA Failures (Error/Rejection) are not captured in Contract Exception Log

OBCL14.6 - Auto Fee Liquidation of Borrower Tranche is failed due to Unsuccessful ECA. ECA request did not receive response from FCUBS due to timeout/connectivity issue and the status is updated as E.

In contract exception log, system logged exception with error code: OL-ALQ110 for Unprocessed Fee component on schedule date.
But there is no exception logged to know the exact reason for ECA failur/eerror.

Similarly if ECA is rejected due to low account balance or account balance of one account is lesser in case of split settlement, system should capture the ECA failure reason in contract exception.


The issue can be reproduced at will with the following steps:
1. Create a Borrower Tranche with Auto Fee liquidation scheduled
2. Verify ECA request is triggered during batch liquidation of the fee components
3. Verify ECA failure reason (If rejected - Rejection Reason/If Error - Reason for Unsuccessful call) is captured in Contract Exception (OLSCEXPT)

Expectation: We should be able to trace the actual reason of failure even if it is timeout issue or host not reachable.


 Added Request and Response click to available in PISECAQU


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.