2. Oracle FCUBS - ELCM Integration

Banks extend various credit facilities like limits to its customers depending on their requirements. Based on the bank’s business model and their target customers they have one of the following scenarios:

• Banks extending basic credit facilities to customers like overdraft or small loans who will prefer to manage the limits within the core banking system (Standalone FCUBS installation)
• Banks dealing with corporates who require trade finance and treasury that requires limit to be routed through dedicated system to manage the collateral and limit details

This chapter contains the following sections:

• Section 2.1, "Scope"
• Section 2.2, "Prerequisites"
• Section 2.3, "Integration Process"

2.1 Scope

This section contains the following topic:

• Section 2.1.1, "FCUBS Installation Modes"

2.1.1 FCUBS Installation Modes

This document talks about two types of FCUBS installation modes. They are:

• FCUBS with No External Limits - For this installation mode limit support is within FCUBS through local facility and local collateral
• FCUBS with External Limits - The integration supports the following modes of FCUBS - Limits installation:
  • Standalone Limits system with FCUBS - SYNC Method
  • Standalone Limits system with FCUBS - ASYNC Method
  • Componentized limits installation - SYNC Method
  • Componentized limits installation - ASYNC Method
  • Embedded Limit Installation with FCUBS

    Details	Standalone		Componentized		Embedded (5)
    	SYNC (1)	ASYNC (2)	SYNC (3)	ASYNC (4)
    Data Stor­age	Different DB	Different DB	Same DB	Same DB	Same DB
    Deployment	Different App.	Different App.	Same App.	Same App.	Same App.
    Mode Inter­face	Web Ser­vices	Web Ser­vices	Web Ser­vices	Web Ser­vices	JDBC/POJO
    Limit Response Handling	Online	Deferred	Online	Deferred	Online

2.2 Prerequisites

Set up Oracle FLEXCUBE Universal Banking Application. ELCM user will have read-only access to this application. The access is provided only to particular extraction tables.

Refer the ‘Oracle FLEXCUBE Universal Banking Installation’ manual.

2.3 Integration Process

This section contains the following topics:

• Section 2.3.1, "Installation Modes"
• Section 2.3.2, "Integration Maintenance and Processing"

2.3.1 Installation Modes

The following installation modes are described in the upcoming sections:

• ASYNC Installation for Standalone and Componentized
• SYNC Installation for Standalone and Componentized
• Embedded Limit Installation with FCUBS

2.3.1.1 ASYNC Installation (Standalone and Componentized)

If the mode of limits installation is selected as ASYNC (Standalone/Componentized), the limits requests will be logged with Limits Pending Status in FCUBS Limits Queue. These pending limits requests are picked by a job to form the webservices XML requests. The status of the limit request will be updated in FCUBS based on the external limits response. The status can be Approved, Rejected or Timed-out. FCUBS will authorize the transactions that are in Approved status.

ASYNC Installation Architecture

Limit Processing Queue

You can query and perform manual actions on external limit requests using Limit Processing Queue screen. This screen supports user action only on timed out requests. You can invoke this screen by typing ‘SQSEXLMT’ in the top right corner of the Application toolbar and clicking the adjoining arrow button.

You can view records based on any or all of the following criteria:

• Branch Code
• Process Status
• Authorization Status
• Transaction Ref No
• External Status
• Customer No
• Destination Source

Select any or all of the parameters for a query and click ‘Search’ button. The records meeting the selected criteria are displayed.

External Limit Queue supports user actions only on a timed out request. A limit request is moved to ‘Timed-out’ status based on the time out parameter maintained. If response is not received from the external system within the given time, the status is marked as timed out. The following actions are allowed on a timed out requests:

• Approve - Manual approval of external limits
• Reject - Manual rejection of external limits
• Authorize - Authorization of external limits approval or reject done from queue
• Resend - Resend of timed-out request

2.3.1.2 SYNC Installation (Standalone and Componentized)

If the mode of limits installation is selected as SYNC (Standalone/Componentized):

• the limit transactions are processed in the transaction time window
• FCUBS creates the limit request during the transaction and sends it to the external limit system
• the response received from the external limit system along with the overrides and errors are displayed to the user during the transaction
• the user can approve the limits overrides and proceed with the transactions from FCUBS

SYNC Installation Architecture

2.3.1.3 Embedded Limit Installation with FCUBS

If mode of installation is selected as embedded limits installation, then FCUBS and ELCM are installed as embedded system. All the limit utilization will be processed online and the response is provided to the user in the transaction window.

2.3.2 Integration Maintenance and Processing

2.3.2.1 Installation Parameters

You can select the required external limit setup mode and communication mode during installation.

Limit Setup Mode (ELCM SETUP MODE)

The following parameters can be used for limit setup mode:

• N - Should be used for No External Limit setup (default)
• S - Standalone UBS - Limits setup/ Componentized Limits setup
• E - Embedded UBS Limit setup

External Limit Interface Mode (UBS_EL_COMM_MODE)

The following parameters can be used for external limit interface mode:

• A - Asynchronous
• S - Synchronous

This is applicable for Standalone UBS - Limits setup/ Componentized Limits setup.

2.3.2.2 FCUBS with No External Limits Installation

If FCUBS is installed with no external limits:

• Local facility can be created using ‘External Facilities Maintenance’ (STDCRFAC) screen
• Local collateral can be created using ‘Local Collateral Maintenance’ (STDCOLAT) screen
• Linkage can be done at customer account and module level as applicable
• FCUBS does the utilization tracking and validations for local facilities and collaterals

2.3.2.3 FCUBS with External Limits Installation

If FCUBS is installed with external limits, then:

• following limit details are replicated from external system to FCUBS:
  • Liability details
  • Customer liability linkage
  • Facility details
  • Collateral details
  • Collateral pool details

• local collateral can be created using the ‘Local Collateral Maintenance’ (STDCOLAT) screen
• linkage is done at customer account and module level
• for local facility and collateral FCUBS tracks the limit balances and performs the validations, and hands over the utilisation to the external system
• you can also link global limits as applicable based on the data replicated from external system
• for non-local limit types, FCUBS does the limit processing based on the external system response.
• in case of Batch operation FCUBS posts the utilisation to external limits as Force Post