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

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.