1.3 Integration Process

The following are the integration processing of OBTF with FCUBS for accounting.

EAC Interface

During the save of an OBTF transaction, OBTF initiates an External Account Check request to DDA (FCUBS) using the DDA EAC web service and waits for the response from DDA system. Upon receiving the success or failure response from DDA system OBTF decides on transaction completion. OBTF communicates synchronously with DDA system hence it helps in OBTF for further transaction processing.

Refer the “Oracle FLEXCUBE UBS - External Accounting Interface” - section 2.3.1 “Account Service Validations” to understand more on how the request is handled at DDA system for various request tags like CUSTACBRN, CCY, CUST_AC_NO and DCINDICATOR.

ECA Interface

As a continuation of OBTF EAC transaction (on save), OBTF decides on initiating the ECA call to DDA system based on the “External Credit Approval Required flag” maintained in “External Customer Account Input” screen. If the flag is chosen OBTF calls the ECA web service of DDA system. In the framed request accounts involved in transaction, account branch, account currency, partial block required for account, partial release block required for account and ECA requested block amount should be available for the DDA system to complete an ECA request from OBTF.

OBTF places the request into the queue and saves the transaction. Now a scheduler “TF_ECA_CALL” picks record from the queue and posts to DDA system for processing. So for ECA OBTF communicates asynchronously with DDA system. Once the DDA system responds with success or failure OBTF updates the external system (DDA) processing status of ECA. Upon ECA successful response from DDA system, OBTF initiates EA asynchronously.

• In case of success response from DDA, OBTF decides to trigger EA actual accounting handoff for the transaction at DDA
• In case of failure response from ECA, OBTF transaction will not be allowed for further actions like authorization.
  1. User can manually reinitiate the request using “IFSTFERQ – Trade Finance Core Entity Error Queue” after making the modifications in DDA / OBTF. The modifications mentioned can be a technical glitch or the functional case like insufficient funds at customer account.
  2. User also has the provision to view the error codes and messages retrieved from DDA system for the corresponding message id and service code in IFSTFERQ screen. Based on it necessary actions can be taken by user.
• Refer the “Oracle FLEXCUBE UBS - External Accounting Interface” - section 2.3.3 “Handling External Credit Approval (ECA) Requests” to understand more on how the request is handled at DDA system for various request tags like CUSTACNO, CUSTACBRN, CUSTACCCY, PARTIALBLKREQD, PARTIALRELEASEALLOWED and UPDASERRIFANYFAIL.

EA Interface

After saving a transaction at OBTF it is time for accounting hand off to DDA system for further processing. OBTF initiates EA to DDA system after save of a transaction asynchronously.

• If accounts involved does not require the external customer credit approval EA will be initiated to DDA after save (Auto Authorisation user) and on Authorisation (Non-auto authorization user)
• If the Accounts having external customer credit approval OBTF will initiate EA only upon the successful ECA response from DDA (Auto/Non-Auto Authorization user) post that only authorization is allowed for the transaction either automatically(Auto Authorisation user) or manually (Non-Auto authorization user).
• Failure EA requests can be resend using the same “IFSTFERQ – Trade Finance Core Entity Error Queue” and error messages can also be viewed using the screen.

Refer the “Oracle FLEXCUBE UBS - External Accounting Interface” - section 2.3.4 “Triggering Accounting Entries to FCUBS” to understand more on how the request is handled at DDA system for various request tags like EVNTSRNO, UNIQUEEXTREFNO, EVENT, TRNREFNO, REFERRALALLOWED, DRCRIND, RELATEDCUSTOMER, TRNREFNO, EVENT, EVENTSRNO, VALUEDT, MODULE, AMTTAG, ACCCY, ACBRANCH, ACNO, LCYAMT, TRNCODE and SOURCE_CODE.