Siebel CRM Integration to Oracle FLEXCUBE Universal Banking Implementation Guide > About the Integration >

Data Integration Points

The data integration points enabling the integration of business processes between the participating applications are described in this topic. A data integration point refers to the data elements that comprise a data entity, such as an account data entity, that are synchronized between Siebel CRM and Oracle FLEXCUBE Universal Banking. Two methods are used to synchronize the data:

• Batch synchronization of data. This synchronization is always unidirectional: from Oracle FLEXCUBE Universal Banking to Siebel CRM.
• Online synchronization of data. This synchronization can be unidirectional or bidirectional.

During the data synchronization process, information retrieved from Oracle FLEXCUBE Universal Banking at run-time that is not stored in Siebel CRM is displayed in the Siebel user interface using virtual business components (VBCs). The data integration points are described in the following topics:

• Customer Data Integration
• Limit Data Integration
• Financial Account Data Integration
• Contract Data Integration
• Offer Data Integration
• Lead Data Integration
• Service Request Data Integration
• Activity Data Integration
• Product Data Integration
• Branch Data Integration
• Mandate Data Integration

Customer Data Integration

Siebel CRM is the master for customer data. Siebel CRM is also the master for customer relationship data. Oracle FLEXCUBE Universal Banking must be kept in synchronization with Siebel CRM.

Figure 4 illustrates the flow of customer data during the data integration process. The data integration method used is online synchronization.

As shown in Figure 4, customer (contact and account) and customer relationship data can be updated or queried by either application; updates made in either application are synchronized with the other. Customer data created in Oracle FLEXCUBE Universal Banking is synchronized with Siebel CRM. Contact and account relationship data created in Siebel CRM is synchronized with Oracle FLEXCUBE Universal Banking.

Figure 4. Customer Data Flow During Data Integration Process

For additional information on the customer party integration objects, see CustomerPartyEBM.

The following integration points use customer data:

• Inquiries from Siebel CRM
• Inquiries from Oracle FLEXCUBE Universal Banking
• Origination of Customers and Financial Accounts
• Customer Transactions

Limit Data Integration

Oracle FLEXCUBE Universal Banking is the master for limit data. Figure 5 illustrates the flow of limit data during the data integration process. The data integration methods used are online and batch synchronization.

As shown in Figure 5, limit data created or modified in Oracle FLEXCUBE Universal Banking is passed to Siebel CRM in batch mode using Oracle Data Integrator. Online inquiries to retrieve additional limit information for display in Siebel CRM are also supported.

Figure 5. Limit Data Flow During Data Integration Process

For additional information on the line of credit integration objects, see QueryLineOfCreditEBM.

The following integration point uses limit data: Inquiries from Siebel CRM.

Financial Account Data Integration

Oracle FLEXCUBE Universal Banking is the master for financial account data. Figure 6 illustrates the flow of financial account data during the data integration process. The data integration method used is online synchronization.

As shown in Figure 6, links between customers and deposit accounts, and between customers and loan accounts that are created or updated in Oracle FLEXCUBE Universal Banking are synchronized with Siebel CRM. Online inquiries from Siebel CRM to retrieve loan account and deposit account information for display in Siebel CRM are also supported.

Siebel CRM does not maintain financial transaction data but retrieves this information from Oracle FLEXCUBE Universal Banking and displays it in the Siebel user interface using virtual business components (VBCs).

Figure 6. Financial Account Data Flow During Data Integration Process

For additional information on the loan account, deposit account, and financial transaction integration objects, see Loan AccountEBM, Deposit AccountEBM, and QueryFinancialTransactionListEBM.

The following integration points use financial account data:

• Inquiries from Siebel CRM
• Origination of Customers and Financial Accounts
• Account Transactions

Contract Data Integration

Oracle FLEXCUBE Universal Banking is the master for contract data. Figure 7 illustrates the flow of contract data during the data integration process. The data integration methods used are online and batch synchronization.

As shown in Figure 7, new or updated contract data is synchronized from Oracle FLEXCUBE Universal Banking to Siebel CRM in batch mode, using Oracle Data Integrator. Online inquiries from Siebel CRM to retrieve contract data for display in the Siebel user interface, using virtual business components (VBCs), are also supported.

Figure 7. Contract Data Flow During Data Integration Process

For additional information on the contract data integration objects, see QueryDocumentaryCreditEBM, QueryDocumentaryCollectionEBM, and QueryBankGuaranteeEBM.

The following integration point uses contract data: Inquiries from Siebel CRM.

Offer Data Integration

Siebel CRM is the master for offer data. Figure 8 illustrates the flow of offer data during the data integration process. The data integration method used is online synchronization.

As shown in Figure 8, Oracle FLEXCUBE Universal Banking issues queries to retrieve offer data stored in Siebel CRM for customers.

Figure 8. Offer Data Flow During Data Integration Process

For additional information on the marketing offer integration objects, see QueryMarketingOfferEBM.

The following integration point uses offer data: Inquiries from Oracle FLEXCUBE Universal Banking.

Lead Data Integration

Siebel CRM is the master for lead data. Figure 9 illustrates the flow of lead data during the data integration process; data flows in one direction only, from Oracle FLEXCUBE Universal Banking to Siebel CRM. The data integration method used is online synchronization.

As shown in Figure 9, updates to a customer's response to an offer are synchronized from Oracle FLEXCUBE Universal Banking to Siebel CRM. Lead data and product interest data that is created in Oracle FLEXCUBE Universal Banking is also synchronized with Siebel CRM.

Figure 9. Lead Data Flow During Data Integration Process

For additional information on the sales opportunity integration objects, see CreateSalesOpportunityEBM.

The following integration point uses lead data: Creation of Leads

Service Request Data Integration

Siebel CRM is the master for service request data. Figure 10 illustrates the flow of service request data during the data integration process; data flows in one direction only, from Oracle FLEXCUBE Universal Banking to Siebel CRM. The data integration method used is online synchronization.

As shown in Figure 10, service request data that is created or updated in Oracle FLEXCUBE Universal Banking is synchronized with Siebel CRM. Online inquiries from Oracle FLEXCUBE Universal Banking to retrieve service request data are also supported.

Figure 10. Service Request Data Flow During Data Integration Process

For additional information on the service request integration objects, see ServiceRequestEBM.

The following integration points use service request data:

• Inquiries from Oracle FLEXCUBE Universal Banking
• Service Requests

Activity Data Integration

Siebel CRM is the master for activity data. Oracle FLEXCUBE Universal Banking must be kept in synchronization with Siebel CRM. Figure 11 illustrates the flow of activity data during the data integration process. The data integration method used is online synchronization.

As shown in Figure 11, data relating to the execution of specific, nonfinancial, business transactions in Oracle FLEXCUBE Universal Banking is synchronized with Siebel CRM to create corresponding Siebel activities.

Figure 11. Activity Data Flow During Data Integration Process

For additional information on the customer interaction integration objects, see CreateCustomerInteractionEBM.

The following integration point uses activity data: Creation of Activities.

Product Data Integration

Oracle FLEXCUBE Universal Banking is the master for product and product pricing data. Product and pricing data created in Oracle FLEXCUBE Universal Banking is synchronized with Siebel CRM using Oracle Data Integrator and is updated in batch mode only.

Branch Data Integration

Oracle FLEXCUBE Universal Banking is the master for branch data. Branch data created in Oracle FLEXCUBE Universal Banking is synchronized with Siebel CRM using Oracle Data Integrator and is updated in batch mode only.

Mandate Data Integration

Oracle FLEXCUBE Universal Banking is the master for mandate data. Mandate data created in Oracle FLEXCUBE Universal Banking is synchronized with Siebel CRM using Oracle Data Integrator and is updated in batch mode only.