1.2.2.7 Forward Liquidation

• As part of loans batch process, amount requested (From payment screen) for liquidation of a contract must be sent to the DDA system for approval (ECA_CHECK_REQD parameter maintained at cstb_param, Branch Param, and CASA level table and verify funds flag at contract level). Only after receiving an approval from the DDA system, the system proceeds with liquidation of the schedule.
• First process in OL and LS batch( for Fwd liquidation) ,would compute the requested amount for a contract and place the request into ECA table with the current status as Unprocessed. A Java program would constantly poll the table for any unprocessed records and transform the records into an ECA request XML and place the same into a IN queue of the external system configured.
• Upon receipt of any response from the DDA system in the OUT queue of OL and LS module, the response would be parsed by the JAVA program and update the status response status (Approved/Rejected) in OLTB_ECA_REQ_MASTER and OLTB_ECA_REQ_DETAIL table.
• When ECA block is successfully created on the accounts (Full), liquidation happens in OL module and perform OL accounting with handoff status as No.
• ECA request for liquidation should not be created from OL and LS module where GL is chosen as settlement account. For example, for a contract having Principal and Interest as components and GL is chosen as a settlement account then no ECA request should be created by OL and LS module. However, if GL is chosen only for Interest and for Principal a valid customer account is chosen as settlement account, then ECA request should be created only for Principal component.
• In a situation where ECA block is successful, but subsequent processing in OL and LS module fails auto retry mechanism should be available in OL and LS module.