1.2 External Account processing
This topic explains the EAC interface, ECA, and EA interface.
EAC Interface
External Account Check (EAC) interface been provided to validate Account of external System (FCUBS). Interface shall validate account while saving a contract/deal. It shall be a synchronous call.
ECA Interface
External Credit Approval (ECA) interface shall block amount from an account that is to be debited for accounting. ECA will works in both Synchronous and Asynchronous mode:
Synchronous
System sends ECA synchronous request to DDA system during contract save. Upon a successful response, system saves the transaction. In case of error response from DDA system, transaction will not be saved and ECA error message will be shown accordingly.
New parameter OBTR_ECA_ONLINE is introduced in parameter table to enable synchronous ECA processing. If this parameter is disabled, ECA continuous to process asynchronously.
To enable the ECA check when saving a reversal, the new feature TR_ECA_ON_REVERSAL needs to be set up in the appropriate branch. When the OBTR_ECA_ONLINE setting is enabled and TR_ECA_ON_REVERSAL is set for a specific branch, OBTR sends a synchronous ECA request to the DDA system when a reversal transaction is saved. If there is not enough balance, the system shows an error message.
In case of force debit feature enabled at the product processor level, system sends single call (Synchronous call with force debit) to DDA system.
Asynchronous
For online transactions, ECA Block shall happen post saving the record. A Job shall run and pick the record for ECA processing in External System (FCUBS) post which the ECA block check will happen during authorization.
The following grid covers the possible scenarios for the ECA check with the Force debit combinations for both synchronous and asynchronous mode.
If the OBTR_ECA_ONLINE setting is not set up and TR_ECA_ON_REVERSAL is active for the branch, the system will show an error during authorization when the balance is insufficient.
Table 1-1 For Save - ECA Force Block - Synchronous/Asynchronous Mode
| S.no | ECA_ONLINE Parameter | Sufficient Balance Available in Account | Force Block | Synchronous/Asynchronous | Remarks |
|---|---|---|---|---|---|
| 1 | Y | Y | N | Synchronous |
On Save: ECA will be processed synchronously and contract save will be successful because of sufficient balance available in the account. On Auth: Contract Authorization Successful. |
| 2 | Y | N | Y | Synchronous |
On Save: Contract Booking will be successful. ECA will be processed with force block On Auth: Contract authorization will be successful. |
| 3 | Y | N | N | Synchronous |
On Save: Contract Booking will be failed. ECA will be processed synchronously, and Errors message will be shown in the contract booking online screen. |
| 4 | N | Y | N | Asynchronous |
On Save: Contract Booking will be successful. On Auth: ECA will be processed during authorization and the same will successfully authorized |
| 5 | N | N | Y | Asynchronous |
On Save: Contract Booking will be successful. On Auth: ECA will be processed asynchronously with force block. |
| 6 | N | N | N | Asynchronous |
On Save: Contract Booking will be successful. On Auth: ECA will be processed asynchronously, and Errors returned from FCUBS logged in error table and shown to the user during authorization. |
The following table covers the possible scenarios for the online ECA check with the Force debit combinations.
Table 1-2 For Reversal - ECA Force Block - Synchronous/Asynchronous Mode
| S.no | ECA_ONLINE Parameter | TR_ECA_ON_REVERSAL Feature | Sufficient Balance Available in Account | Force Block | Synchronous/Asynchronous | Remarks |
|---|---|---|---|---|---|---|
| 1 | Y | Y | Y | N | Synchronous |
On Reversal Save: ECA is processed synchronously and contract reversal save is successful due to sufficient balance in the account. On Reversal Auth: Contract Reversal Authorization Successful. |
| 2 | Y | Y | N | Y | Synchronous |
On Reversal Save: Contract Reversal is successful. ECA is processed with force block. On Reversal Auth: Contract reversal authorization is successful. |
| 3 | Y | Y | N | N | Synchronous |
On Reversal Save: Contract Reversal is failed. ECA is processed synchronously and Errors message is displayed in the contract screen. |
| 4 | N | N | Y | N | NA |
On Reversal Save: Contract reversal is successful. On Reversal Auth: Contract auth also successful |
| 5 | N | N | N | Y | NA |
On Reversal Save: Contract Reversal is successful. On Reversal Auth: Contract Authorization also successful. |
| 6 | N | N | N | N | NA |
On Reversal Save: Contract Reversal is successful On Reversal Auth: Contract authorization is also successful |
| 7 | N | Y | N | Y | Asynchronous |
On Reversal Save: Contract reversal is successful. On Reversal Auth: Contract reversal is successfully authorized and ECA is processed with force block. |
| 8 | N | Y | N | N | Asynchronous |
On Reversal Save: Contract Reversal is successful. On Reversal Auth: Contract reversal Authorization is failed with ECA error message |
| 9 | Y | N | Y | N | NA |
On Reversal Save: Contract reversal is successful. On Reversal Auth: Contract reversal is successfully authorized |
| 10 | Y | N | N | Y | NA |
On Reversal Save: Contract reversal is successful. On Reversal AuthContract reversal is successfully authorized |
| 11 | Y | N | N | N | NA |
On Reversal Save:Contract Reversal is successful. On Reversal Auth: Contract reversal is successfully authorized |
Note:
ECA check is applicable only for FX auto liquidation batch during EOD. The system performs ECA check for debit transactions and in case of insufficient balance, the system logs the FX contract in exception table and go ahead with further EOD processing.EA Interface
External Accounting Interface been provided to do External Accounting for a contract/deal. EA will happen post authorization of contract/deal. The posting of request to EA processing stage happens via an asynchronous call. A OBTR_EA_CALL Job shall run and pick the record for EA processing in External System (FCUBS).
The handoff preferences for accounting entries from product processors to DDA/GL system can be maintained in the Account Handoff Preference (IFDACHPF) screen.
EA processing call to external system (FUBS) can be synchronous or asynchronous. If the maintenance is available in the Integration parameter maintenance screen with WBS (web services) as the communication channel, then the communication mode will be synchronous. If the Communication channel is MDB, then the communication mode will be asynchronous. For more information on the Integration parameter maintenance (IFDINPRM) screen, refer to the Integration Parameter Maintenance. Based on the MDB queue maintenance, system post the request to the respective queue. Similarly, the response call will be received from the response queue based on the maintenance.
Response can be viewed in the External Accounting Entries Browser (TRSEACBR) screen. For more information, refer to the External Accounting Entries Browser.
For queue setup and the Foreign Server setup, refer to the Foreign Server Configuration section in the Treasury Management Weblogic JMS Configuration installation guide.
Parent topic: Treasury- FCUBS Integration