Topics:
· Integration Activities in Oracle FLEXCUBE Universal Banking System
· Extraction Process for Tables of Flexcube Module
· Data Transfer from FCUBS to OFSAA
Data Integration Hub (DIH) helps load the data from the source systems to the OFSAA staging tables, through logical interfaces known as Application Data Interfaces (ADI). DIH provides a set of User Interfaces (UI), which are used to define and maintain External Data Descriptors (EDD), Application Data Interfaces, and map the EDDs and ADIs through Connectors. The mappings can be one-to-one, one-to-many, and many-to-many.
The source systems that supply data include the core banking systems, rating systems, modeling systems, and so on. In the absence of DIH, the data from the source systems are extracted, transformed, and loaded (ETL process) to the physical tables in Oracle Data Integrator (ODI). With DIH, the ETL activity is not replaced; but DIH serves as an abstract, logical layer to the physical tables
Oracle Financial Services Analytical Applications (OFSAA) enables financial institutions to measure and meet risk-adjusted performance objectives, cultivate a risk management culture, lower the costs of compliance and regulation, and improve customer insight.
Oracle FLEXCUBE Universal Banking (FCUBS) supports the changing landscape of retail, corporate, and investment banking requirements with strong transaction banking and Islamic banking capabilities.
The current FCUBS-OFSAA interfaces transfer all key data elements across various modules within FCUBS to OFSAA Common Staging Area (CSA).
The integration between Oracle FCUBS and OFSAA enables financial institutions to:
· Get insight into customer patterns based on the data captured in core banking.
· Achieve end-to-end improvement in business delivery.
· Achieve effective performance and risk-free management using the available customer data.
This integration is achieved by handing off FCUBS core banking data with OFSAA through the FLEXCUBE Information Server (FIS) and DIH.
NOTE:
FCUBS versions 14.3.0.0 and 14.4.0.0 are supported.
Figure 1: OFS FCUBS Data Flow
Procedures which are packaged within FCUBS populate data from various tables in FCUBS to several landing area tables after execution. Essentially a one-to-one mapping is done between the landing area table (EDD) and OFSAA staging area table (ADI). Most of the calculations and transformations are done within these extraction routines. The DIH connector pulls data from the landing tables and populates the same in the staging area tables.
The following integration activities take place in Oracle FLEXCUBE Universal Banking System.
Table1: Integration Activities in Oracle FLEXCUBE Universal Banking System
Module |
Handoff Details |
|---|---|
Core Entities |
· Customer address, phone numbers, and email IDs · Customer education and employment details · Customer marital status · Customer relationship details · Details of organizations that are the customers · Exchange rate information · Details of all geographical locations and transaction channels of the bank · Details of the loan product category and list of all products |
Current Account and Savings Account |
· All personal and business addresses, email IDs and phone numbers associated with an account · List of branch transactions · CASA account ledger and transactions on OD accounts · Interest rates of CASA and OD accounts |
Consumer Lending |
· All personal and business addresses, email IDs and phone numbers associated with an account · Loan contract transactions details · Repayment schedules of contracts like loan, mortgages, OD and credit cards |
Term Deposit |
· Term deposit product processor and term deposit ledger table details |
Enterprise Limits and Collateral Management |
· Details of the collaterals submitted by the customer for various loan contracts · Customer credit line details · Market value and the original value of the collaterals |
General Ledger |
· GL book parameters and the list of GL items available in FCUBS · GL balance of the customer · Interbank correspondent transactions of a customer |
Foreign Exchange |
· Foreign exchange account transaction data of a customer · Foreign exchange contracts of a customer · Exchange rates between two currencies |
Money Market |
· Borrowing records of the customer · Money market transaction data |
Corporate Deposits |
· Corporate deposit product processor and Corporate deposit ledger table details |
Securities Repo and Reverse Repo |
· Repo and Reverse Repo record details · Repo and Reverse Repo Transaction details |
Securities |
· Instrument Contract Customer data · Market Instrument Contract Data · Instrument Market Prices |
Exchange Traded Derivatives |
· Future Contracts Data · Future Contracts Transaction Data |
Letter Of Credit |
· Letter of Credit Contract Data · Letter of Credit Transaction Data |
Bills and Collections |
· Payment and collection details · Bills and Collections Transaction Data |
Derivatives |
· Hedging Data of Forwards, Futures, Options, and Swaps · Derivatives Transaction data |
Over the Counter ( OTC) Options |
· Option Contracts data · Option Contracts Transaction data |
Syndication Loans and Commitments |
· Loan Write-Off and Recovery details |
Leasing |
· Lease contract Data |
Collections |
· Collection Data |
Retail Lending |
· Loan Write-off and Recovery Details |
FLEXCUBE Information Server (FIS) is used as the gateway in the FCUBS-OFSAA integration. FCUBS internally uses FIS framework components to extract data and store the data in the staging tables of FCUBS. During the End of Financial Input (EOFI) batch, the module data in FIS is extracted to staging tables in FCUBS. FCUBS provides a control table to indicate successful data extraction. OFSAA pulls the data from the tables in FCUBS using the DIH connector. If the source and target systems are in the same database, then data from the source staging table are transformed and loaded to fact and dimension tables in the target system using synonyms. If the source and target systems are in a different database, then data from the source staging table are loaded to target staging tables using transportable tablespaces. The transfer or extraction of data from FCUBS to OFSAA differs based on the staging tables as follows:
· Master table: Incremental data between two extraction dates are transferred.
· Maintenances and contract tables: Entire transaction data are transferred in each extraction.
· Transaction table: Data related to the transactions created on the extraction date is transferred.
The core banking data in Oracle FCUBS are transferred to OFSAA using FIS. The data in FCUBS staging tables are mapped to the FIS staging table. During the end of the day, the core banking data are sent to FIS. OFSAA then picks the data from FIS through DIH.
For details on data transfer from FCUBS to OFSAA, see the FCUBS OFSAA Data Transfer .
The file has the following details:
· Source System
· Target System
· Data Transferred
· Source System Module
· FCUBS Staging Table Name
· Extraction Package Name
· Target System Table Name
· Extraction Routine
· Data Included in the Extraction
The following modules are used in Flexcube:
· Current and Savings Account
· Consumer Lending (CL)
· CORE
· Enterprise Limits and Collateral Management (ELCM)
· Foreign Exchange (FX)
· General Ledger (GL)
· Money Market (MM)
· Term Deposit (TD)
· Corporate Deposits (CD)
· Securities Repo and Reverse Repo (SR)
· Securities (SE)
· Exchange Traded Derivatives (ETD)
· Letter of Credit (LC)
· Bills and Collections (BC)
· Derivatives (DV)
· Over the Counter Option (OT)
· Syndication Loans and Commitments (LS)
· Leasing (LE)
· Collections (CN)
· Retail Lending (RL)
· Oracle Banking Corporate Lending (OBCL)