Bookshelf Home | Contents | Index | PDF     

Siebel CRM Integration to Oracle FLEXCUBE Universal Banking Implementation Guide > Performing Batch Data Loading and Synchronization >

About Batch Data Loading and Synchronization

Oracle Data Integrator is used to perform the initial and on-going batch synchronization of data between Oracle FLEXCUBE Universal Banking and Siebel CRM. Oracle Data Integrator synchronizes data for the following entities:

  • Branch

    In Siebel CRM, a branch is mapped to a Siebel division.

  • Product
  • Product Rate
  • Contracts
  • Limit
  • Mandate

During the Oracle Data Integrator configuration process, you generate scenarios for the Oracle Data Integrator packages that are provided with the Integration, as described in Generating Scenarios for Integration Packages.

NOTE:  In this guide, the term, the Integration, refers to Siebel CRM Integration to Oracle FLEXCUBE Universal Banking.

As shown in Figure 3, the scenarios perform the following steps:

  1. Extract the data from the Oracle FLEXCUBE Universal Banking staging tables.
  2. Load the extracted data into the Siebel Enterprise Integration Manager (EIM) tables.
  3. Update the batch number variables, and start the Siebel EIM jobs using Siebel Server Manager.

    The batch number variables are used as input for running the Siebel EIM jobs.

  4. The EIM jobs import the data into Siebel base tables.

Figure 3 illustrates the batch data synchronization process.

Figure 3. Batch Data Synchronization Process

For each entity that is batch loaded, Table 4 lists the Oracle FLEXCUBE Universal Banking staging table that stores the data that is transferred to Siebel CRM. Table 4 also lists the corresponding Siebel EIM table that the staging table data is loaded into.

Table 4. Staging Tables and Siebel EIM Tables Used in the Integration
Entity
Oracle FLEXCUBE Universal Banking Staging Tables
Siebel EIM Tables

Branch

STTM_BRANCH_HANDOFF
  • EIM_FN_ACCNT1
  • EIM_ADDR_PER

Product

 

CSTM_PRD_HANDOFF

 
  • EIM_PROD_INT
  • EIM_PROD_LN
  • EIM_PROD_INT1

Account Class

STTM_ACLASS_HANDOFF

Rate (Loans)

CLTM_LOAN_RATE_HDF
  • EIM_FN_CNDTN
  • EIM_FN_PRDINT1

Rate (Corporate Deposit)

LDTM_CDRATE_HANDOFF

Rate (CASA and Retail Deposit)

STTM_ACCLASS_UDE_VALHF; STTM_CHGRATE_HANDOFF

Contract (Bills and Collections)

BCTB_CONTRACT_HANDOFF
  • EIM_ASSET
  • EIM_FN_ASSET
  • EIM_FN_ASSET3

Contract (Letter Of Credit and Guarantees)

LCTB_CONTRACT_HANDOFF

Limit

GETM_LIMITS_HANDOFF

EIM_FN_LIMIT

Mandate

PCTM_CLIENT_HANDOFF

EIM_FN_ASSET1

Table 5 lists each of the packages used by the Integration and the task performed by each package.

Table 5. Packages Used by the Integration
Package
Task

FINS_BIB_INITIAL_SETUP

Runs scripts to create the database entities required for other packages.

FINS_BIB_BRANCH_PKG

Loads branch data.

FINS_BIB_PRODUCT_PKG

Loads product data.

FINS_BIB_PRODUCT_RATE_PKG

Loads product rate data.

FINS_BIB_LIMIT_PKG

Loads limit data.

FINS_BIB_MANDATE_PKG

Loads mandate data.

FINS_BIB_CONTRACT_PKG

Loads contract data.

The way in which data in the staging tables is mapped to data in the Siebel EIM tables during the batch integration process is described in Data Mappings to Siebel EIM Tables.

      
Siebel CRM Integration to Oracle FLEXCUBE Universal Banking Implementation Guide Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.