5About the Integration
About the Integration
This chapter describes the online data synchronization process and the data and business process integration points supported by Siebel CRM Integration to Oracle FLEXCUBE Universal Banking. It includes the following topics:
About Online Data Synchronization
The online data synchronization process uses a point-to-point integration methodology. Web services provided in the Integration incorporate Oracle Application Integration Architecture (AIA) Enterprise Business Message and Enterprise Business Object entities. These Web services provide the data object definitions and data operations required to synchronize data in the participating applications directly, without the need for middleware.
The Web services use request-and-response messages to exchange data between the participating applications. These request-and-response messages include and extend Oracle AIA Enterprise Business Message structures, and are designed to process the same message payload. In the online integration processes, Web services accept messages in Enterprise Business Message format as input and return messages in the same format as output.
The online synchronization processes are implemented as inbound and outbound synchronous Web services, and inbound and outbound fire-and-forget Web services. Inbound and outbound Web service calls are defined in terms of Siebel CRM. Detailed information on each type of Web service is given in the following topics. For additional information about the fire-and-forget Web services, see About Inbound Fire-and-Forget Web Services.
Synchronous Inbound Web Services
The operations supported by the synchronous inbound Web services, and the specific Web services used for each operation, are shown in the following table.
Table Synchronous Inbound Web Services
| Operation | Web Service |
|---|---|
Create |
FINS BIB Customer Info Create FINS BIB Service Request Info Upsert |
Query |
FINS BIB Customer Info Inquiry FINS BIB Query Offer FINS BIB Service Request Query SYNC |
Synchronous Outbound Web Services
The synchronous outbound Web services support query operations in the Integration. The following Web services perform query operations:
BankGuaranteeService
CustomerPartyService
DepositAccountService
DocumentaryCollectionService
DocumentaryCreditService
FinancialTransactionService
LineOfCreditService
LoanAccountService
Fire-and-Forget Inbound Web Services
The following are the fire-and-forget inbound Web services; these support create and update operations in the Integration:
FINCORP BIB Deposit Account Update
FINCORP BIB Deposit Account Upsert FAF
FINCORP BIB Loan Account Update FAF
FINCORP BIB Loan Account Upsert FAF
FINS BIB Call Customer Info Update FAF
FINS BIB Call Lead Info Upsert
FINS BIB Service Request Info Upsert FAF
BankingAndWealthManagementCustomerInteractionEBSV1
Fire-and-Forget Outbound Web Service
The fire-and-forget outbound Web service, CustomerPartyService, supports update operations in 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
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.
The following illustrates the flow of customer data during the data integration process. The data integration method used is online synchronization.
As shown in the following image, 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.
For additional information on the customer party integration objects, see CustomerPartyEBM.
The following integration points use customer data:
Limit Data Integration
Oracle FLEXCUBE Universal Banking is the master for limit data. The following illustrates the flow of limit data during the data integration process. The data integration methods used are online and batch synchronization.
As shown in this flow, 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.
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. The following illustrates the flow of financial account data during the data integration process. The data integration method used is online synchronization.
As shown in this flow, 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).
For additional information on the loan account, deposit account, and financial transaction integration objects, see Loan Account EBM, Deposit AccountEBM, and QueryFinancialTransactionListEBM.
The following integration points use financial account data:
Contract Data Integration
Oracle FLEXCUBE Universal Banking is the master for contract data. The following illustrates the flow of contract data during the data integration process. The data integration methods used are online and batch synchronization.
As shown in this flow, 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.
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. The following illustrates the flow of offer data during the data integration process. The data integration method used is online synchronization.
As shown in this flow, Oracle FLEXCUBE Universal Banking issues queries to retrieve offer data stored in Siebel CRM for customers.
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. The following 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 this flow, 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.
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. The following 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 this flow, 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.
For additional information on the service request integration objects, see ServiceRequestEBM.
The following integration points use service request data:
Activity Data Integration
Siebel CRM is the master for activity data. Oracle FLEXCUBE Universal Banking must be kept in synchronization with Siebel CRM. The following illustrates the flow of activity data during the data integration process. The data integration method used is online synchronization.
As shown in this flow, 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.
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.
Business Process Integration Points
The following are the high-level business process integration points between Siebel CRM and Oracle FLEXCUBE Universal Banking:
Inquiries from Siebel CRM
The Integration supports inquiries started from Siebel CRM to retrieve customer, financial account, and contract information from Oracle FLEXCUBE Universal Banking. The following information applies to this integration point:
Direction of Synchronization. Siebel CRM to Oracle FLEXCUBE Universal Banking.
Data Synchronized. See the following table.
Integration Object Name. See the following table.
The entities for which Siebel CRM can issue inquiries to retrieve additional information from Oracle FLEXCUBE Universal Banking are as follows:
Contacts and Accounts
Customers in Oracle FLEXCUBE Universal Banking are mapped to Contacts (retail customers) and Accounts (corporate customers) in Siebel CRM. Non-Siebel CRM customer data from Oracle FLEXCUBE can be displayed in Siebel CRM.
Financial Accounts:
Current and savings accounts and related standing instructions
Retail deposits, which refer to term deposits and recurring deposits
Corporate deposits
Loans
Financial transactions
Siebel CRM does not maintain financial transactions data but retrieves this data from Oracle FLEXCUBE Universal Banking and displays it in the Siebel application user interface.
Contract
Siebel CRM retrieves contract data from Oracle FLEXCUBE Universal Banking and displays it in the Siebel application user interface.
For each Siebel CRM inquiry integration point, the following illustrated shows the integration objects used for the Integration and the data queried. For information about each of the integration objects, see EBM Mappings Used in Online Synchronization
Table Integration Points and Integration Objects Used for Inquiries from Siebel CRM
| Integration Point | Integration Object Name | Data Queried |
|---|---|---|
Retrieves customer data from Oracle FLEXCUBE Universal Banking. |
QueryCustomerPartyEBM QueryCustomerPartyResponseEBM |
Customer |
Retrieves limit information from Oracle FLEXCUBE Universal Banking. |
QueryLineOfCreditEBM QueryLineOfCreditResponseEBM |
Limit |
Retrieves financial account (deposit) information from Oracle FLEXCUBE Universal Banking. Retrieves deposit account standing instruction information from Oracle FLEXCUBE Universal Banking. |
QueryDepositAccountEBM QueryDepositAccountResponseEBM |
Financial Account |
Retrieves financial account (loan) information from Oracle FLEXCUBE Universal Banking. |
QueryLoanAccountEBM QueryLoanAccountResponseEBM |
Financial Account |
Retrieves financial transactions from Oracle FLEXCUBE Universal Banking. |
QueryFinancialTransactionListEBM QueryFinancialTransactionListResponseEBM |
Financial Account |
Retrieves contract (bills and collections) information from Oracle FLEXCUBE Universal Banking. |
QueryDocumentaryCollectionEBM QueryDocumentaryCollectionResponseEBM |
Contract |
Retrieves contract (letters of credit) information from Oracle FLEXCUBE Universal Banking. |
QueryDocumentaryCreditEBM QueryDocumentaryCreditResponseEBM |
Contract |
Retrieves contract (bank guarantee) information from Oracle FLEXCUBE Universal Banking. |
QueryBankGuaranteeEBM QueryBankGuaranteeResponseEBM |
Contract |
Inquiries from Oracle FLEXCUBE Universal Banking
The Integration supports inquiries started from Oracle FLEXCUBE Universal Banking to retrieve customer, offer, and service request information from Siebel CRM. The following information applies to this integration point:
Direction of Synchronization. Oracle FLEXCUBE Universal Banking to Siebel CRM.
Data Synchronized. See the following table.
Integration Object Name. See the following table.
The entities for which Oracle FLEXCUBE Universal Banking retrieves additional information from Siebel CRM are as follows:
Customer data. Customer or prospect data can be retrieved from Siebel CRM.
Offer data. Information relating to personalized and localized offers for existing customers stored in Siebel CRM can be retrieved.
Service request data. Information on service requests stored in Siebel CRM can be retrieved, for example, information on the current status of the service request.
For each Oracle FLEXCUBE Universal Banking inquiry integration point, the following table shows the integration objects used for the Integration and the data queried. For detailed information on each of the integration objects, see EBM Mappings Used in Online Synchronization
Table Integration Points and Integration Objects Used for Inquiries from Oracle FLEXCUBE Universal Banking
| Integration Point | Integration Object Name | Data Queried |
|---|---|---|
Retrieves contact or account data from Siebel CRM. Retrieves prospect data from Siebel CRM. |
QueryCustomerPartyListEBM QueryCustomerPartyListResponseEBM |
Customer |
Retrieves offers with a status of All Active from Siebel CRM. Retrieves offers with a status of Contact Specific - Active from Siebel CRM. |
QueryMarketingOfferListEBM QueryMarketingOfferListResponseEBM |
Offer |
Retrieves service request data from Siebel CRM. |
QueryServiceRequestListEBM QueryServiceRequestListResponseEBM |
Service request |
Origination of Customers and Financial Accounts
The Integration supports the synchronization of new financial account data, and new and updated customer data between Siebel CRM and Oracle FLEXCUBE Universal Banking. The following information applies to this integration point:
Direction of Synchronization. Bidirectional.
Data Synchronized. Customer and financial account.
Integration Object Names. See the following table.
Siebel CRM is the master for customer data and Oracle FLEXCUBE Universal Banking is the master for financial account data. The origination of customer (contact and account in Siebel CRM) and financial account data is as follows:
Customer
Customers can be created in Oracle FLEXCUBE Universal Banking; these customers are synchronized with Siebel CRM.
Note: All Oracle FLEXCUBE Universal Banking customers exist in Siebel CRM, but customers can exist in Siebel CRM who do not exist in Oracle FLEXCUBE Universal Banking.Financial Account:
Origination of the following financial accounts occurs in Oracle FLEXCUBE Universal Banking only:
Savings account
Current account
Loan account
Cluster deposit accounts
Recurring deposit accounts
Term deposit accounts
Links between customers and financial accounts are created in Oracle FLEXCUBE Universal Banking; when a financial account is created, the data is synchronized with Siebel CRM.
For each origination integration point, the following table shows the integration object used for the Integration and the data queried. For detailed information on each of the integration objects, see EBM Mappings Used in Online Synchronization .
Table Integration Points and Integration Objects Used for Originations
| Integration Point | Integration Object Name | Data Queried |
|---|---|---|
Customers created in Oracle FLEXCUBE Universal Banking are synchronized with Siebel CRM. |
CreateCustomerPartyEBM CreateCustomerPartyResponseEBM |
Customer |
Prospects converted to customers in Oracle FLEXCUBE Universal Banking are synchronized with Siebel CRM. |
UpdateCustomerPartyEBM |
|
Links between customers and deposit accounts that are created in Oracle FLEXCUBE Universal Banking are synchronized with Siebel CRM. |
CreateDepositAccountEBM |
Financial Account |
Links between customers and loan accounts that are created in Oracle FLEXCUBE Universal Banking are synchronized with Siebel CRM. |
CreateLoanAccountEBM |
Customer Transactions
The Integration supports the synchronization of updates to customer data made in either Siebel CRM or Oracle FLEXCUBE Universal Banking. The following information applies to this integration point:
Direction of Synchronization. Bidirectional.
Data Synchronized. Customer.
Integration Object Name. UpdateCustomerPartyEBM.
Customer and customer relationship data is synchronized between the applications as follows:
Customer data
Updates to the following customer data can be made in either Siebel CRM or Oracle FLEXCUBE Universal Banking; the following changes in one application are synchronized with the other application:
Changes to customer names
Changes to contact and account addresses
Status changes
Changes to other customer data that is common between Oracle FLEXCUBE Universal Banking and Siebel CRM
Updates to Know Your Customer (KYC) data in Oracle FLEXCUBE Universal Banking are synchronized with Siebel CRM
Relationship data:
Customer relationships created or updated in Siebel CRM are synchronized with Oracle FLEXCUBE Universal Banking.
Changes to the relationship type values, for example, father or spouse, are made in Siebel CRM and are synchronized with Oracle FLEXCUBE Universal Banking.
Changes to customer-to-customer relationships that exist in both applications are synchronized with the other application.
Account Transactions
The Integration supports the synchronization of account transaction data between the applications. The following information applies to this integration point:
Direction of Synchronization. Oracle FLEXCUBE Universal Banking to Siebel CRM.
Data Synchronized. Financial account and customer.
Integration Object Names. UpdateLoanAccountEBM and UpdateDepositAccountEBM.
The following account transactions are initiated in Oracle FLEXCUBE Universal Banking and synchronized with Siebel CRM:
An assignment of a customer to a home loan account
An update to a demand deposit account to add a new title, for example, when a customer is added as a coholder to a savings account
An update to a demand deposit account to delete a title, for example, when a customer is removed as a coholder to a savings account
Creation of Leads
The Integration supports the synchronization of leads created in Oracle FLEXCUBE Universal Banking with Siebel CRM for customers who exist in both applications. The following information applies to this integration point:
Direction of Synchronization. Oracle FLEXCUBE Universal Banking to Siebel CRM.
Data Synchronized. Lead.
Integration Object Name. CreateSalesOpportunityEBM.
The Integration supports the synchronization of the following lead data:
Contact and prospect data can be retrieved from Siebel CRM if a customer exists in both of the participating applications.
Lead data captured in Oracle FLEXCUBE Universal Banking, and offer acceptance details retrieved from Siebel CRM, are synchronized to create a lead in Siebel CRM.
Lead data captured in Oracle FLEXCUBE Universal Banking and product interest data are synchronized to create a lead in Siebel CRM.
A customer negative response to an offer is synchronized with Siebel CRM.
Service Requests
The Integration supports the synchronization of service request data between the applications. The following information applies to this integration point:
Direction of Synchronization. Oracle FLEXCUBE Universal Banking to Siebel CRM.
Data Synchronized. Service request.
Integration Object Names. CreateServiceRequestEBM and UpdateServiceRequestEBM.
Service request data is not stored in Oracle FLEXCUBE Universal Banking but service request data can be entered in Oracle FLEXCUBE Universal Banking; this data is synchronized to create or update a service request in Siebel CRM. Service request data stored in Siebel CRM can be retrieved and updated from Oracle FLEXCUBE Universal Banking.
Creation of Activities
The Integration supports the creation of activities in Siebel CRM when specific transactions are executed in Oracle FLEXCUBE Universal Banking. The following information applies to this integration point:
Direction of Synchronization. Oracle FLEXCUBE Universal Banking to Siebel CRM.
Data Synchronized. Activity.
Integration Object Name. CreateCustomerInteractionEBM.
Certain business transactions executed in Oracle FLEXCUBE Universal Banking require follow-up activities to be performed in Siebel CRM. An activity is created in Siebel CRM when each of the following transactions occurs in Oracle FLEXCUBE Universal Banking:
Creating a standing instruction in an account
Issuing a check book
Requesting to stop a check payment