1. CRM Integration to Oracle FLEXCUBE Universal Banking Implementation Guide
  2. What's New in This Release

4Performing Batch Data Loading and Synchronization

Performing Batch Data Loading and Synchronization

This chapter describes how to perform the initial loading of batch data from Oracle FLEXCUBE Universal Banking to Siebel CRM and the ongoing synchronization of that data. It includes the following topics:

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 the following image, 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.

The following illustrates the batch data synchronization process.

Batch Data Synchronization Process

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

Table 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

The following lists each of the packages used by the Integration and the task performed by each package.

Table 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

Performing Batch Data Loading

This topic describes how to perform the initial batch loading of data from Oracle FLEXCUBE Universal Banking to Siebel CRM.

To perform the initial batch loading of data

  1. Set up Oracle FLEXCUBE Universal Banking for the batch data integration as follows:

    • Create a user with read-only access to the staging tables from which Oracle Data Integrator extracts the data to be uploaded to Siebel CRM.

    • The staging tables are populated with data by batch programs after the end-of-day process is run, so ensure the following events have occurred:

      • The batch programs are configured in Oracle FLEXCUBE Universal Banking.

      • The end-of-day process is completed.

    For information on these tasks, see Siebel CRM Integration Interface User Manual.

  2. Locate the Siebel EIM configuration files provided with the Integration; the EIM configuration file extension is .ifb.

    These files are located in Siebel\8.2\Tools_1\REPPATCH\ACR548.zip, where Siebel\8.2\Tools_1 is the Siebel Tools 8.2 installation directory. For additional information, see Accessing the Integration Files.

    The Siebel EIM configuration files specify the type of EIM process to perform, data import in this case, define the data to import, and indicate the batch numbers to use. For additional information on Siebel EIM configuration files, see Siebel Enterprise Integration Manager Administration Guide.

  3. Place the Siebel EIM configuration files in the SIEBSRVR_ROOT\ADMIN directory, where SIEBSRVR_ROOT is the Siebel Server installation directory on the computer where the Siebel Server is installed.

  4. Run the Oracle Data Integrator integration scenarios to start the batch data loading.

    To start the batch loading of data from Oracle FLEXCUBE Universal Banking to Siebel CRM, run each of the following scenarios that you generated in Generating Scenarios for Integration Packages:

    • FINS_BIB_PRODUCT_PKG

    • FINS_BIB_PRODUCT_RATE_PKG

    • FINS_BIB_LIMIT_PKG

    • FINS_BIB_MANDATE_PKG

    • FINS_BIB_CONTRACT_PKG

    • FINS_BIB_BRANCH_PKG

    You can run scenarios using one of the following methods:

    • From the ODI Studio

    • From a command line

    • From the Standalone Agent if it is installed

    • From the ODI scheduler

    • From an external scheduler

    For information on the various methods available for running scenarios, see Oracle® Fusion Middleware Developer’s Guide for Oracle Data Integrator 11g Release 1.

  5. After performing the batch data loading, check the following log files for errors:

    • Log table BIB_ODI_ERROR_LOG.

    • Siebel EIM log files.

      The EIM log files are Server Manager error log files which are located in the directory specified by the FINS_BIB_Log_Path variable.

    For information on these log files, see Siebel Log Files During Batch Data Loading.

  6. After importing data into the Siebel Financial Services application, use the business service simulator to run the ISS Authoring Import Export Service to release the imported data so it can be used in the Siebel application. Perform the following steps:

    1. Log in to the Siebel Financial Services application.

    2. Navigate to the Administration - Business Service screen, then the Simulator view.

    3. In the Simulator list, click the New tab.

    4. In the Service Name field, select ISS Authoring Import Export Service.

    5. In the Method Name field, type the value Post_EIM_Upgrade. This method is hidden.

    6. In the Input Arguments list, create a new record.

    7. Set the Test Case# field to 1.

    8. In the Property Name field, create a new property with the following values:

      • Property Name: ReportOnly

      • Property Value: FALSE

    9. Click the Run tab to run the service.

Performing Siebel Configuration Tasks After Importing Batch Data

This topic describes the Siebel configuration tasks that must be performed after Oracle FLEXCUBE Universal Banking data has been batch loaded into Siebel CRM.

To perform Siebel configuration tasks after importing batch data

  1. Stop the Workflow Monitor Agent.

    For information on this task, see Siebel Business Process Framework: Workflow Guide.

  2. Generate and verify triggers as follows:

    1. Use the following srvrmgr (Server Manager) command to generate triggers:

      			start task for comp gentrig with 
			exec=True,remove=False,PrivUser=UserName,PrivUSerPass=Password

      where UserName and Password are the assigned privileged user name and password.

    2. Verify the task:

      1. Log in to the Siebel Financial Services application.

      2. Navigate to the Administration-Server Management screen, then the Components view.

      3. In the components list, select Generate Triggers, then click the Tasks view and verify that the most recent task for the Generate Triggers component completed successfully.

      For additional information on generating triggers, see Siebel Business Process Framework: Workflow Guide.

  3. Restart the Workflow Monitor Agent component.

  4. Create an integration user as follows:

    1. Log in to the Siebel Financial Services application.

    2. Navigate to the Administration - User screen, then the Employees view.

    3. In the employees list, select the record for the Siebel administrator.

    4. Select the check box in the Integration User Flag field for this employee.

    A user must be designated as the integration user; this user’s credentials are used by the Siebel application to accept inbound Web service calls from Oracle FLEXCUBE Universal Banking and to create, update, and query Siebel records. Designate the Siebel administrator as the integration user.

Batch Loading of Customer and Financial Account Data

The Oracle Data Integrator interfaces provided by the Integration do not support batch loading of Oracle FLEXCUBE Universal Banking Customer and Financial Account data to Siebel CRM. Therefore, you must create Siebel Enterprise Integration Manager (EIM) mappings and interfaces to perform the batch loading of this data. For examples of the data mappings used for each entity that is integrated using the batch data loading process, see Data Mappings to Siebel EIM Tables.

Updating Batch Data Periodically

You use Oracle Data Integrator to perform the initial batch loading of certain data entities from Oracle FLEXCUBE Universal Banking to Siebel CRM. Oracle Data Integrator can also be used to perform periodic updates to this data in Siebel CRM, if required.

After the end-of-day process is run in Oracle FLEXCUBE Universal Banking, the staging tables are purged and are populated with updated data; that is, data created or modified on that business day. The staging tables do not contain historical data. You can upload this updated data to the Siebel integration tables so that it can be imported into Siebel CRM by rerunning the scenarios generated for the integration packages as described in Performing Batch Data Loading.

When the integration packages are run again, Oracle Data Integrator removes any existing information from the Siebel EIM tables before populating them with the updated data from the Oracle FLEXCUBE Universal Banking staging tables.

During the periodic updates performed by Oracle Data Integrator, data from Oracle FLEXCUBE Universal Banking is upserted in the Siebel database; that is, data entities loaded from the staging tables that do not already exist in Siebel CRM are created in the Siebel database, and data entities that do already exist in the Siebel database are updated with new information from Oracle FLEXCUBE Universal Banking.

You can run scenarios on request or schedule them to run periodically using the Oracle Data Integrator scheduler or an external scheduler. In all cases, schedule the scenarios to run after the end-of-day process is completed in Oracle FLEXCUBE Universal Banking. For information on the various methods available for running scenarios, see Oracle® Fusion Middleware Developer’s Guide for Oracle Data Integrator 11g Release 1.