Uni Bank Imp
Uni Bank Imp
Oracle FLEXCUBE
Universal Banking
Implementation Guide
Siebel Innovation Pack 2017
July 2017
Copyright © 2005, 2017 Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions
on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in
your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any
means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-
free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing
it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users
are “commercial computer software” pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and
adaptation of the programs, including any operating system, integrated software, any programs installed
on the hardware, and/or documentation, shall be subject to license terms and license restrictions
applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and
other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any
damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Devices. UNIX is a registered trademark of The Open Group. Android is a trademark of Google Inc.
Apple and iPad are registered trademark of Apple Inc.
This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and
its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use
of third-party content, products, or services, except as set forth in an applicable agreement between you
and Oracle.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website
at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle
Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Contents
CreateSalesOpportunityEBM 196
ServiceRequestEBM 198
CreateServiceRequestEBM 199
UpdateServiceRequestEBM 202
QueryServiceRequestListEBM 204
CreateCustomerInteractionEBM 207
Deposit AccountEBM 211
CreateDepositAccountEBM 211
UpdateDepositAccountEBM 218
QueryDepositAccountEBM 226
QueryFinancialTransactionListEBM 251
Loan AccountEBM 253
CreateLoanAccountEBM 254
UpdateLoanAccountEBM 256
QueryLoanAccountEBM 259
Index
This chapter introduces Siebel CRM Integration to Oracle FLEXCUBE Universal Banking. It includes
the following topics:
NOTE: In this guide, the term, the Integration, refers to Siebel CRM Integration to Oracle FLEXCUBE
Universal Banking.
In the Integration, data is transferred between the applications using a point-to-point architecture
model; that is, data flows directly between the participating applications without the use of
middleware. Data is synchronized between the applications using Oracle Data Integrator, for initial
batch uploading of data, and Web service calls, for the online synchronization of data.
Siebel CRM Integration to Oracle FLEXCUBE Universal Banking supports the business process
integration points described in Table 2. For each integration point, the source and target applications
are indicated. The participating application that issues a Web service call to create or update a data
entity, or that issues a data query, is termed the source application. The application in which the data
entity is updated or created, or the application that provides the data requested in a query, is the
target application.
Inquiry from Siebel CRM to Oracle FLEXCUBE Siebel CRM Oracle FLEXCUBE
Universal Banking: Universal Banking
■ Limit inquiry
■ Guarantees inquiry
New customer data, including Know Your Customer Oracle FLEXCUBE Siebel CRM
(KYC) validation Universal Banking
Customer CASA information and customer CASA Oracle FLEXCUBE Siebel CRM
amendment information Universal Banking
Term deposit account and term deposit account Oracle FLEXCUBE Siebel CRM
amendment information Universal Banking
■ The files provided by the Integration to allow the batch synchronization of data support Oracle
Database only.
■ Only the primary customer address is synchronized between Oracle FLEXCUBE Universal
Banking and Siebel CRM.
■ If the lengths defined for corresponding columns in Siebel CRM and Oracle FLEXCUBE Universal
Banking differ, then the data in the longer column is truncated during the synchronization process
if the target column is smaller than the source column.
■ Siebel CRM is the master application for the following data:
■ Customer
■ Service request
■ Activity
■ Offers
■ Leads
■ Customer relationships
■ Oracle FLEXCUBE Universal Banking is the master application for the following data:
■ Products and prices
■ Branch
■ Financial account
■ Limit
■ Mandate
■ Standing instructions
■ Contracts
■ Transactions
■ A limited set of Oracle FLEXCUBE Universal Banking bank branch information is stored in Siebel
CRM as an internal division.
Software Requirements
Siebel CRM Integration to Oracle FLEXCUBE Universal Banking requires the following software:
For information on obtaining and installing Siebel CRM and Oracle FLEXCUBE Universal Banking, see
the product documentation.
Related Documentation
This topic lists additional documentation that provides information for Siebel CRM Integration to
Oracle FLEXCUBE Universal Banking.
These documents are provided on the CD containing the Oracle FLEXCUBE Universal Banking
software.
■ Oracle® Fusion Middleware Developer's Guide for Oracle Data Integrator 11g Release 1
■ Oracle® Fusion Middleware Installation Guide for Oracle Data Integrator 11g Release 1
■ Oracle® Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration
Architecture Foundation Pack 11g Release 1
■ Oracle® Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration
Architecture Foundation Pack 11g Release 1
This chapter describes how to install and configure Siebel CRM Integration to Oracle FLEXCUBE
Universal Banking. It contains the following topics:
■ Process of Importing the Integration Repository Files in an Oracle Data Integrator Development
Environment on page 20
NOTE: In this guide, the term, the Integration, refers to Siebel CRM Integration to Oracle FLEXCUBE
Universal Banking.
To install and configure the Integration, perform the following tasks and processes:
4 “Process of Importing the Integration Repository Files in an Oracle Data Integrator Development
Environment” on page 20.
This task is a step in “Roadmap for Installing and Configuring the Integration” on page 17.
For more information, see Siebel Installation Guide for the operating system you are using.
2 In the Siebel Tools installation directory, navigate to the REPPATCH directory, for example,
navigate to \Siebel\8.2\Tools_1\REPPATCH\, and locate the ACR548.zip file.
3 Unpack the ACR548.zip file to extract the integration files. These include:
■ The Oracle Data Integrator work and master repository files used for the batch data loading
process
■ Siebel Enterprise Integration Manager configuration files (IFB files) used for the batch data
loading process
This task is a step in “Roadmap for Installing and Configuring the Integration” on page 17.
■ Create a database schema to store the Oracle Data Integrator work repository and master
repository.
■ Ensure that the schema owners of the Oracle FLEXCUBE Universal Banking and Siebel
databases are assigned the following privileges:
2 Install Oracle Data Integrator as described in Oracle® Fusion Middleware Installation Guide for
Oracle Data Integrator. Select the following installation options:
■ In the Select Installation Type screen, select ODI Studio (with local agent). You can optionally
choose to install the Standalone Agent.
■ In the Repository Configuration screen, select the Skip Repository Configuration option.
3 After the installation process has completed, configure a connection between Oracle Data
Integrator and the master repository as follows:
b From the ODI menu, choose File, and then the New menu item.
c In the New Gallery window, select ODI from the General category, then select the option, Create
a New ODI Master Login.
d In the Repository Connection Information window, enter ODI and database connection
information using values similar to that shown in the following table.
Oracle Data Login Name Enter a connection alias, for example, Master
Integrator Repository.
Connection
User Enter the value SUPERVISOR for the ODI
supervisor user name.
Database Connection User Enter the user ID of the owner of the tables
(Master Repository) created for the master repository.
f Click OK.
This process is a step in “Roadmap for Installing and Configuring the Integration” on page 17.
For additional information on these tasks, see Oracle® Fusion Middleware Developer's Guide for
Oracle Data Integrator 11g Release 1.
This task is a step in “Process of Importing the Integration Repository Files in an Oracle Data Integrator
Development Environment” on page 20 and “Process of Implementing the Integration in an Oracle Data
Integrator Production Environment” on page 30.
2 From the ODI menu, choose File, and then the New menu item.
5 In the Repository Connection screen, specify Database Connection and Repository Configuration
information as follows:
■ Database Connection. The values you specify for the Database Connection parameters
must be the same as those specified when you configured the connection between Oracle
Data Integrator and the master repository as described in Step 3 on page 19.
Click the Test Connection button to test the database connection, then click Next. Ensure the
connection is working before proceeding.
■ Repository Configuration. Select the Use a Zip File option, and enter the path to the
Master_Repository.zip file that you accessed in Siebel Tools. For information, see “Accessing
the Integration Files” on page 18.
6 In the Password Storage screen, accept the default option, Use Password Storage Configuration
specified in Export. By selecting this option, the user name and password values that are
configured in the repository are used to log in to Oracle Data Integrator. These values are:
■ User: SUPERVISOR
■ Password: SUPERVISOR
7 Click Finish.
This task is a step in “Process of Importing the Integration Repository Files in an Oracle Data Integrator
Development Environment” on page 20 and “Process of Implementing the Integration in an Oracle Data
Integrator Production Environment” on page 30.
4 In the ODI Work Repository connection properties screen, specify the values listed in the
following table.
Parameter Value
Technology Select the technology of the server that is to host the work repository,
for example, Oracle.
JDBC Driver Specify the driver required to connect to the database where the work
repository is defined.
JDBC URL Enter the complete path of the data server hosting the work
repository.
User Enter the user ID of the owner of the tables that are to be created for
the work repository.
Password Enter the password associated with the table owner user ID.
5 Click the Test Connection button to verify that the connection is working, then click Next.
6 On the Specify ODI Work Repository properties screen, specify values for the parameters listed
in the following table.
Parameter Value
7 Click Finish.
8 Disconnect from the master repository by navigating to the ODI menu option, then selecting the
Disconnect “repository_name” option.
This task is a step in “Process of Importing the Integration Repository Files in an Oracle Data Integrator
Development Environment” on page 20.
2 From the ODI menu, choose File, and then the New menu item.
5 In the Repository Connection Information screen, specify the connection information as follows:
■ Oracle Data Integrator Connection. Enter the same values for the Connection parameters
that you specified when configuring the connection between Oracle Data Integrator and the
master repository as described in “Installing Oracle Data Integrator” on page 18.
■ Database Connection (Master Repository). Enter the same values for the Database
Connection parameters that you specified when configuring the connection between Oracle
Data Integrator and the master repository as described in “Installing Oracle Data Integrator”
on page 18.
■ Work Repository. In the Work repository field, enter the name of the work repository you
created in “Creating a Work Repository” on page 21, for example, WORKREP1.
7 Click the Connect to Repository… link, then select the Work Repository connection.
8 Right-click the Designer Navigator, select Import, and then select the Work Repository option.
9 In the Import work repository dialog box, select the import mode from the Import Mode list.
Select one of the following options:
10 Select the Import from a Zip file option, and enter the path to the workrep.zip file. For
information on this file, see “Accessing the Integration Files” on page 18.
NOTE: The import process can take between 30 and 50 minutes to complete. Wait until the
import has completed before attempting to perform other operations in Oracle Data Integrator.
When the work repository import is completed the Import Report is displayed.
11 Perform the following substeps to explicitly import the work repository projects for the
Integration to the work repository. Performing these steps ensures that global variables are
mapped to scenarios when the scenarios are generated at a later stage.
b Open the Operator navigator, right-click Scenarios, then select the Import Scenario menu item.
c In the File import directory field, enter the name of the folder containing the unzipped
Workrep.zip file.
d Select all the scenarios in the Select the file(s) to import list, then click OK.
This process is a step in “Roadmap for Installing and Configuring the Integration” on page 17.
1 “Connecting to the Oracle FLEXCUBE Universal Banking and Siebel CRM Databases” on page 24
This task is a step in “Process of Configuring Oracle Data Integrator in a Development Environment” on
page 24.
USING 'dbstring';
where:
■ database link name is the name you assign to the database link
■ oracle user id is the user ID used to connect to the remote Oracle FLEXCUBE database
■ remote oracle user's password is the password associated with the oracle user ID
2 Use the following query to verify that the database link is successfully created:
For example, the following SQL statements create a database link in the local Siebel database that
connects to the AAADEV2 database, with the FCDEV116 user ID, using the service name AAADEV2.
CONNECT TO FCDEV116
IDENTIFIED BY FCDEV116
USING '(DESCRIPTION =
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = AAADEV2 )
)'
2 Open the Topology Navigator, then navigate to Physical Architecture, Technologies, Oracle, and
then Oracle FC Server.
■ In the Instance/dblink (Data Server) field, enter the name assigned to the database link you
created in “Creating the Database Link” on page 24.
■ In the User and Password fields, enter the user name and password that are used to connect
to the remote Oracle FLEXCUBE Universal Banking database. Enter the same user and
password values as those specified when creating the database link.
5 Click the JDBC tab, then specify values for the following parameters:
■ In the JDBC Driver field, select the driver used to access the Oracle FLEXCUBE database, for
example, the Oracle JDBC driver.
■ In the JDBC URL field, enter the complete path to the Oracle FLEXCUBE Universal Banking
database.
6 On the Topology Navigator, expand Oracle FC Server, select the FLEXCUBE data server, and select
the Definition tab to view the Physical Schema definition details.
■ Enter the name of the Oracle FLEXCUBE database in the Schema (Schema) and Schema
(Work Schema) fields.
The Work Schema is a temporary store for objects required at run time. Depending on how
you have implemented Oracle Data Integrator, the Schema and Work Schema can be the
same or different. If these schemas are different, the user specified in Step 4 on page 26
must have privileges to both.
2 Open the Topology Navigator, then navigate to Physical Architecture, Technologies, Oracle, and
then Oracle Release Server.
3 In the Data Server editor, specify values for the following Data Server definition parameters:
■ In the Instance/dblink (Data Server) field, enter the name of the Siebel database.
■ In the User and Password fields, enter the user name and password that are used to connect
to the Siebel database.
4 Click the JDBC tab, then specify values for the following parameters:
■ In the JDBC Driver field, select the driver used to access the Siebel database, for example,
the Oracle JDBC driver.
■ In the JDBC URL field, enter the complete path to the Siebel database.
5 Click the Test Connection button to verify that the connection settings are correct.
6 In the Topology Navigator, expand Oracle Release Server, select the Siebel data server, and open
the Physical Schema definition.
■ Enter the name of the Siebel database in the Schema (Schema) and Schema (Work Schema)
fields.
The Work Schema is a temporary store for objects required at run time. Depending on how
you have implemented Oracle Data Integrator, the Schema and Work Schema can be the
same or different. If these schemas are different, the user specified in Step 3 on page 26
must have privileges to both.
This task is a step in “Process of Configuring Oracle Data Integrator in a Development Environment” on
page 24
■ Create a new context for running the ODI interfaces by right-clicking, and selecting New
Context.
■ Select the existing default value, Release Context, for running ODI Interfaces.
4 If you are creating a new context, then enter the context name in the Name field.
5 To relate the logical and physical schemas for the Oracle FLEXCUBE and Siebel database servers,
do the following:
b In the Logical Schema column, select the Siebel CRM logical schema.
c In the associated Physical Schemas column, select the physical schema to associate with the
Siebel CRM logical schema.
d Repeat steps Step b and Step c for the Oracle FLEXCUBE logical schema.
6 To verify that the context, for example, Release Context, is correctly assigned to the Siebel CRM
and Oracle FLEXCUBE logical schemas, do the following:
a In the Topology Navigator, navigate to Logical Architecture, Technologies, Oracle, and then
Oracle FC Server.
b In the Logical Schema editor, verify that the context specified for Oracle FC Server is Release
Context.
c In the Topology Navigator, select the Oracle Release Server.
d In the Logical Schema editor, verify that the context specified for Oracle Release Server is
Release Context.
Oracle Data Integrator variables store single values, for example, a string, a number, or a date, which
can be updated at run time. This topic describes how to modify the global and project variables
required by the Integration.
This task is a step in “Process of Configuring Oracle Data Integrator in a Development Environment” on
page 24
2 Open the Designer navigator, then navigate to Others, and then Global Variables.
3 Select each of the variables shown in the following table in turn, open the variable, and in the
Variable editor screen, set the default value of the variable as indicated in the following table.
FINS_BIB_Gateway_Server Specify the name and port number of the Siebel Gateway
Name Server.
FINS_BIB_Log_Path Enter the path to the directory where you want to store
Server Manager log files for Enterprise Integration Manager
jobs.
FINS_BIB_Username The Siebel user name used for connecting to the Siebel
Enterprise, for example, SADMIN.
FINS_BIB_Password The password associated with the Siebel user name defined
in FINS_BIB_Username.
FINS_BIB_Siebel_Path Enter the full path to the Siebel installation directory that
contains the srvrmgr.exe file.
FINS_BIB_Siebel_Server Specify the name of the Siebel Server on which the Siebel
Enterprise Integration Manager component runs.
FINS_BIB_Default_Organization Specify the name of the organization for which you want to
load data. This variable is applicable for Product and Branch
data only.
FINS_BIB_EIM_ErrorFlags Specify the event log level for the Siebel Enterprise
Integration Manager component. For additional information
on changing log levels, see Siebel Enterprise Integration
Manager Administration Guide.
FINS_BIB_EIM_TraceFlags Specify the trace log level for the Enterprise Integration
Manager component. For additional information, see Siebel
Enterprise Integration Manager Administration Guide.
4 In the Designer navigator, navigate to Projects, BIB BRANCH, Variables, and then
FINS_BIB_Organization.
5 In the Variable editor screen, set the default value of the variable to the name of the bank for
which branch data is to be loaded.
6 A Siebel organization must be created for the bank for which branch data is to be loaded before
starting the branch data load. To create a Siebel organization, perform the following steps:
c In the form, add a new record and complete the necessary fields.
For detailed information on creating organizations and divisions, see Siebel Security Guide.
This task is a step in “Process of Configuring Oracle Data Integrator in a Development Environment” on
page 24.
The following procedure describes how to generate scenarios for the Integration packages.
2 Open the Designer navigator, then navigate to Projects, BIB BRANCH, First Folder, Packages, and
then FINS_BIB_BRANCH_PKG.
3 Right-click the package, then select the Generate Scenario menu item.
4 Click OK in the New Scenario dialog box to select the default scenario name and version.
5 In the Designer navigator, navigate to the relevant project for each package listed in the
following table, then repeat Step 3 and Step 4 for each of the packages.
This process is a step in “Roadmap for Installing and Configuring the Integration” on page 17.
To implement the Integration in an Oracle Data Integrator production environment, perform the
following tasks:
This task is a step in “Process of Implementing the Integration in an Oracle Data Integrator Production
Environment” on page 30.
When Oracle Data Integrator scenarios are generated in a development environment, the default
values of the global and project variables used in the scenarios relate to the development
environment. When Oracle Data Integrator is then deployed in the production environment, these
default values might not apply.
To ensure that the values of the variables used in scenarios are appropriate when scenarios are
transferred to the production environment, use one of the following methods:
■ Change the values of the Global and Project variables in the development environment to the
correct values for the production environment, and then generate the scenarios. For more
information, see “Configuring Integration Variables” on page 28.
■ Manually modify the Global and Project variables used in the scenarios in the production
environment. For more information, see “Modifying Scenario Variables in the Production
Environment” on page 32.
■ Pass the correct values of the Global and Project variables for the production environment to
Oracle Data Integrator each time a scenario is run. Oracle Data Integrator overrides the default
value of the variable with the value that is passed.
This option is available only if you have installed the Oracle Data Integrator Standalone Agent
and can run scenarios from the command line. For additional information, see Oracle® Fusion
Middleware Developer's Guide for Oracle Data Integrator 11g Release 1.
c In the Export Directory field, enter the path to the directory where you want to export the
scenario, then click OK.
2 To import the scenarios into the production environment work repository, perform the following
steps:
a In the production environment, start ODI Studio, and connect to the ODI work repository.
b Open the Operator navigator, right-click Scenarios, then select the Import Scenario menu item.
c In the File import directory field, enter the name of the file import directory. Specify the name
of the directory that you exported the scenario to in Step 1.
d Select the files that you want to import, and then click OK.
e Click Yes to continue the import if a warning message appears stating that you are about to
delete or replace objects.
When the import process is completed, a list of the imported objects is displayed.
where:
2 In the Scenario Variable editor, change the value in the Default Value field to the appropriate
value for the production environment.
3 For each of the imported scenarios, repeat Step 1 and Step 2 for the following variables:
■ FINS_BIB_Default_Organization
■ FINS_BIB_EIM_ErrorFlags
■ FINS_BIB_EIM_SQLFlags
■ FINS_BIB_EIM_TraceFlags
■ FINS_BIB_Enterprise_Server
■ FINS_BIB_Gateway_Server
■ FINS_BIB_Log_Path
■ FINS_BIB_Organization
■ FINS_BIB_Password
■ FINS_BIB_Siebel_Path
■ FINS_BIB_Siebel_Server
■ FINS_BIB_Username
This process is a step in “Roadmap for Installing and Configuring the Integration” on page 17.
■ “Configuring JMS for Outbound Web Services Using Advanced Queuing” on page 35
This task is a step in “Process of Configuring Siebel Business Applications” on page 33.
The Integration uses the Workflow Monitor Agent BIB Customer workflow to monitor customer
workflow policies. Configuring this component involves:
2 Navigate to the Administration - Server Configuration screen, Enterprises, and then the
Component Definitions view.
3 In the Component field, select Workflow Monitor Agent, and then make a copy of the record by
selecting the Copy Record menu item.
4 Set values for the new record as shown in the following table.
Field Value
Alias WorkMonBiBCust
5 Click the Activate button to activate the new component, then Click the Synchronize button to
synchronize the component.
2 Navigate to the Administration - Server Configuration screen, then the Servers view.
3 In the Siebel Servers list, select the server that you want to configure.
5 In the Parameters form, set the values of the parameters as shown in the following table.
Parameter Value
Action Interval 5
Sleep Time 10
Default Tasks 1
This task is a step in “Process of Configuring Siebel Business Applications” on page 33.
2 Navigate to the Administration - Server Configuration screen, Servers, and then the Components
view.
4 In the Parameters form, select Business Service Query Access in the Parameter field, and set the
Value field to Workflow Process Manager.
When each of these workflows is invoked, it submits a request, using the EAI JMS Transport business
service, to the JMS queue hosted by Oracle FLEXCUBE Universal Banking. This topic describes how
to set up the Java environment for the Integration and how to configure and test the EAI JMS
Transport business service used in the Siebel outbound Web services.
This task is a step in “Process of Configuring Siebel Business Applications” on page 33.
For information on downloading JRE, see Siebel System Requirements and Supported Platforms
on Oracle Technology Network.
a Copy the following Siebel JAR files from the SIEBSRVR_ROOT\CLASSES directory to D:\JMS.
❏ Siebel.jar
❏ SiebelJI_enu.jar
The wlfullclient.jar file is provided by Oracle FLEXCUBE Universal Banking, the Web service
provider.
3 Create the jndi.properties file on the Siebel Server in the D:\JMS directory. The jndi.properties
file specifies the connection values that the Siebel Server uses to look up queues and their
connection factories dynamically. Specify the following values for the jndi.properties file:
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.security.principal=weblogic
java.naming.security.credentials=weblogic#1
where FLEXCUBE ipaddress and port name is the remote method invocation (RMI) URL used to
connect to Oracle FLEXCUBE Universal Banking.
4 Create the JVM subsystem used in Siebel CRM, and specify the profile parameters for the
subsystem as shown in the following table.
JVM DLL DLL String The path to the JVM library file, for example, in a
Name Windows environment:
C:\Sun\SDK\jdk\jre\bin\server\jvm.dll
JVM Options VMOPTIONS String JVM-specific options for the log file, for example:
-Djms.log=D:\JMS\log\jms.log
For detailed information on creating a JVM subsystem, see Transports and Interfaces: Siebel
Enterprise Application Integration.
5 Stop and restart the Siebel Server for the changes to take effect.
The following procedure describes how to run the Business Service Simulator to test the EAI JMS
Transport business service configuration.
3 In the Simulator list, click New, and specify the values shown in the following table.
Field Value
4 In the Input Arguments list, specify the input parameters for the Business Service method by
clicking New and specifying the values shown in the following table.
Field Value
Test Case # 1
Type PropertySet
Field Value
Property Value JNDI name of the JMS connection factory, for example:
java:comp/env/jms/MDBQCF
5 To create an additional property set, click New again and specify the values shown in the
following table.
Field Value
Test Case # 1
Type PropertySet
Property Value JNDI name for the JMS queue. For example: MDB_QUEUE_DA
To update queue and connection factory details for outbound Web services
1 In Siebel Tools, navigate to the Workflow Processes Object List Editor.
c In the Send Message to JMS Queue step of the workflow, change the values for the following
process properties to the values tested in “Configuring and Testing the EAI JMS Transport
Business Service” on page 37:
❏ ConnectionFactory
❏ SendQueue
e Publish and activate the workflow by clicking the Publish/Activate button on the WF/Task Editor
toolbar.
For detailed information on editing workflows using Siebel Tools, see Siebel Business Process
Framework: Workflow Guide and Using Siebel Tools.
This task is a step in “Process of Configuring Siebel Business Applications” on page 33.
2 Navigate to the Administration - Data screen, then the List of Values view.
4 Enter the Display Value for the record that you want to change in the Display Value field, for
example, Citizen.
A list of records appears that includes the display value that you entered.
6 Select the record that you want to modify, and make the change. For example, for the record
with a Display Value of Citizen, deselect the Active field.
7 Perform Step 4 to Step 6 for each of the records in the following table.
NOTE: If you choose to enable citizenship values other than Indian, British, or American, then
set the Order field to a value of less than 100.
8 To see the modified list-of-values in the Siebel application, click Clear Cache.
■ Overdraft Facility
■ Passbook Facility
■ ATM Facility
■ ILM Applicable
You can create additional product features in Siebel CRM if necessary. For more information, see
Siebel Product Administration Guide.
This task is an optional step in “Process of Configuring Siebel Business Applications” on page 33.
This task is a step in “Process of Configuring Siebel Business Applications” on page 33.
2 Navigate to the Administration-Business Process screen, then the Workflow Deployment view.
3 In the Repository Workflow Processes list, query the Name field for each of the Integration
workflows.
4 For each of the workflows, select the record, and click Activate.
■ Get Treatment Id
For detailed information on activating workflows in a Siebel client, see Siebel Business Process
Framework: Workflow Guide.
This task is a step in “Process of Configuring Siebel Business Applications” on page 33.
3 In the Service Ports list, change the address field to the URL of the Oracle FLEXCUBE Universal
Banking server.
4 Perform Step 2 and Step 3 for each of the following Web services in turn:
■ BankGuaranteeService
■ CustomerPartyService
■ DepositAccountService
■ DocumentaryCollectionService
■ DocumentaryCreditService
■ FinancialTransactionService
■ LineOfCreditService
■ LoanAccountService
This task is a step in “Process of Configuring Siebel Business Applications” on page 33.
2 Navigate to the Administration - Application screen, then the System Preferences view.
3 Click the New button to create a new system preference, and enter the values shown in the
following table.
Field Value
This task is a step in “Roadmap for Installing and Configuring the Integration” on page 17.
2 Consolidate the sources from the following releases in the order shown:
a FC_UBS_V.UM_11.0.0.0
For information on this task, see the Oracle FLEXCUBE Universal Banking documentation that is
provided with the product software.
4 Install and configure the Oracle FLEXCUBE Universal Banking integration components (the EBO
Direct Build utility) that allow the Oracle FLEXCUBE Universal Banking and Siebel CRM
applications to be integrated.
For detailed information on these tasks, see FCUBS EBO Direct Build Utility User Guide.
After configuring the Oracle FLEXCUBE Universal Banking integration components, you must perform
several other tasks before the Oracle Data Integrator batch data processes can run. For information
on these tasks, see “Performing Batch Data Loading” on page 47.
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:
■ Branch
■ 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” on page 30.
NOTE: In this guide, the term, the Integration, refers to Siebel CRM Integration to Oracle FLEXCUBE
Universal Banking.
As shown in Figure 3 on page 46, 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.
For each entity that is batch loaded, Table 3 lists the Oracle FLEXCUBE Universal Banking staging
table that stores the data that is transferred to Siebel CRM. Table 3 also lists the corresponding Siebel
EIM table that the staging table data is loaded into.
Table 3. Staging Tables and Siebel EIM Tables Used in the Integration
■ EIM_ADDR_PER
■ EIM_PROD_LN
Table 3. Staging Tables and Siebel EIM Tables Used in the Integration
■ EIM_FN_ASSET
Contract (Letter Of Credit and LCTB_CONTRACT_HANDOFF
■ EIM_FN_ASSET3
Guarantees)
Table 4 lists each of the packages used by the Integration and the task performed by each package.
Package Task
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 Appendix B, “Data Mappings to Siebel EIM Tables.”
■ 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:
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.
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” on page 30:
■ 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
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:
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” on page 73.
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:
b Navigate to the Administration - Business Service screen, then the Simulator view.
d In the Service Name field, select ISS Authoring Import Export Service.
e In the Method Name field, type the value Post_EIM_Upgrade. This method is hidden.
h In the Property Name field, create a new property with the following values:
For information on this task, see Siebel Business Process Framework: Workflow Guide.
where UserName and Password are the assigned privileged user name and password.
❏ 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.
c In the employees list, select the record for the Siebel administrator.
d 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.
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” on page 47.
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.
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:
NOTE: In this guide, the term, the Integration, refers to Siebel CRM Integration to Oracle FLEXCUBE
Universal Banking.
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 on page 92.
■ BankGuaranteeService
■ CustomerPartyService
■ DepositAccountService
■ DocumentaryCollectionService
■ DocumentaryCreditService
■ FinancialTransactionService
■ LineOfCreditService
■ LoanAccountService
■ BankingAndWealthManagementCustomerInteractionEBSV1
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:
Figure 4 on page 56 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.
For additional information on the customer party integration objects, see “CustomerPartyEBM” on
page 125.
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.
For additional information on the line of credit integration objects, see “QueryLineOfCreditEBM” on
page 170.
The following integration point uses limit data: “Inquiries from Siebel CRM” on page 62.
As shown in Figure 6 on page 58, 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 AccountEBM” on page 253, “Deposit AccountEBM” on page 211, and
“QueryFinancialTransactionListEBM” on page 251.
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.
The following integration point uses contract data: “Inquiries from Siebel CRM” on page 62.
As shown in Figure 8, 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”
on page 194.
The following integration point uses offer data: “Inquiries from Oracle FLEXCUBE Universal Banking”
on page 64.
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.
The following integration point uses lead data: “Creation of Leads” on page 68
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” on
page 198.
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.
The following integration point uses activity data: “Creation of Activities” on page 69.
The entities for which Siebel CRM can issue inquiries to retrieve additional information from Oracle
FLEXCUBE Universal Banking are as follows:
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:
■ 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, Table 6 shows the integration objects used for the
Integration and the data queried. For information about each of the integration objects, see
Appendix C, “EBM Mappings Used in Online Synchronization.”
Table 6. Integration Points and Integration Objects Used for Inquiries from Siebel CRM
Data
Integration Point Integration Object Name Queried
Table 6. Integration Points and Integration Objects Used for Inquiries from Siebel CRM
Data
Integration Point Integration Object Name Queried
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, Table 7 shows the integration
objects used for the Integration and the data queried. For detailed information on each of the
integration objects, see Appendix C, “EBM Mappings Used in Online Synchronization.”
Table 7. Integration Points and Integration Objects Used for Inquiries from Oracle FLEXCUBE
Universal Banking
Data
Integration Point Integration Object Name Queried
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
■ 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, Table 8 shows the integration object used for the Integration
and the data queried. For detailed information on each of the integration objects, see Appendix C,
“EBM Mappings Used in Online Synchronization.”
Data
Integration Point Integration Object Name Queried
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:
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:
■ 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.
Account Transactions
The Integration supports the synchronization of account transaction data between the applications.
The following information applies to this integration point:
The following account transactions are initiated in Oracle FLEXCUBE Universal Banking and
synchronized with Siebel CRM:
■ 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:
■ 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.
Service Requests
The Integration supports the synchronization of service request data between the applications. The
following information applies to this integration point:
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:
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:
This chapter provides information on troubleshooting Siebel CRM Integration to Oracle FLEXCUBE
Universal Banking. It contains the following topics:
■ How Siebel CRM Handles Errors During Online Data Synchronization on page 71
For information on the log files generated by Siebel CRM, see Siebel System Monitoring and
Diagnostics Guide.
The error-handling mechanism that is used depends on the type of Siebel Web service that generates
the error, as described in Table 9.
Synchronous Inbound Create or Query The error message in the EBM format is
transformed using the EAI XSLT Service and
is sent to Oracle FLEXCUBE Universal
Banking.
where
9110970000009273DAUpdate.XML
Table 10 shows the log files created for each integration object if errors occur during create and
update operations.
MessageIdDACreate.XML
Loan Account LA MessageIdLAUpdate.XML
MessageIdLACreate.XML
If an error occurs while running the packages for the batch data loads, then the error message
is logged in the table BIB_ODI_ERROR_LOG in the Siebel database. This table stores the
following information about the error:
■ Package name
■ Step name
■ Step type
■ Error code
■ Error message
■ Created date
During the batch data loading, Oracle Data Integrator loads data from Oracle FLEXCUBE
Universal Banking staging tables into Siebel EIM tables. Oracle Data Integrator starts the Siebel
EIM jobs, using the Siebel Server Manager utility. If an error occurs in a Siebel EIM job, then a
log file is created in the location you specified for the variable FINS_BIB_Log_Path. For additional
information, see “Configuring Integration Variables” on page 28.
Check the log files for any errors during the Siebel EIM job processing.
This chapter provides information on how to extend or customize Siebel CRM Integration to Oracle
FLEXCUBE Universal Banking. It contains the following topics:
■ Installing the Oracle AIA Foundation Pack Enterprise Object Library on page 80
■ Synchronize additional fields for an entity that is already integrated, for example, synchronize
additional address fields
To customize or extend the batch data loading files provided with the Integration, you can edit the
Oracle Data Integrator packages provided with the Integration or create new packages. You must
also create EIM mappings between the Siebel CRM and Oracle FLEXCUBE Universal Banking data to
be integrated. For information on working with Oracle Data Integrator packages, see Oracle® Fusion
Middleware Developer’s Guide for Oracle Data Integrator 11g Release 1. For examples of the data
mappings used for each entity that is integrated using the batch data loading, see Appendix B, “Data
Mappings to Siebel EIM Tables.”
To customize or extend the data that is synchronized online, you must import Oracle Application
Integration Architecture (AIA) Enterprise Object Library artifacts into Siebel CRM. These artifacts
create or extend Web services to perform the required processing. This chapter describes how to
perform this type of customization, using the loan account business entity as an example.
NOTE: In this guide, the term, the Integration, refers to Siebel CRM Integration to Oracle FLEXCUBE
Universal Banking.
Enterprise Business Objects (EBOs) provide definitions of standard business data objects, such
as a loan account or a sales order, and reusable data components. The collection of EBOs
provided in the Enterprise Object Library constitutes a data model that facilitates the integration
of data in applications and systems. Each application data schema is mapped only once to the
EBO data model, thereby eliminating the requirement to map data directly from one application
to another. The EBOs are provided as XML Schema Definition (XSD) files.
Enterprise Business Services (EBSs) represent standard Web service definitions for performing a
business task, such as creating an account. These services provide message-driven interfaces
(described in XML) for the purpose of exchanging data between applications, both synchronously
(request-and-response) and asynchronously (fire-and-forget). These services can be
implemented by applications that participate in the Integration.
The interface definitions for the EBSs are defined in Web Service Definition Language (WSDL)
files, which list the operations, message exchange pattern, and payload that are applicable for
each operation of a service. This interface description is composed of all details required for a
client application to call the service. An EBS takes an EBM as input and provides another EBM as
output.
Enterprise Business Messages (EBMs) are the messages that are exchanged between the
participating applications in the Integration. The EBM represents the specific content of an EBO
needed for performing a specific operation on a business object, such as creating a loan account
or deleting a sales order. The metadata about the message is specified in the message header
section.
The relationship between EBOs, EBMs, and EBSs in a direct integration is illustrated in Figure 12 for
a Loan Account business entity. As shown in Figure 12, an EBM exists for each operation supported
for the Loan Account EBO. WSDL files provide service definitions for each of the operations performed
by the Loan Account EBS.
Figure 12. Relationship Between EBOs, EBMs, and EBSs for a Loan Account Business Entity
For additional information on the Oracle AIA framework, architecture, and concepts, see Oracle®
Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture
Foundation Pack.
■ Involve the business users to identify the specific fields that are to be synchronized, and start
detailed mappings between the data in Siebel CRM and the data in Oracle FLEXCUBE Universal
Banking.
■ Identify any EBOs, EBMs, and EBSs that are required for the customization.
■ Determine the operations that are to be performed on the data. These operations can be any of
the operations defined in an EBM; that is, create, retrieve, update or delete operations.
The number of EBM-based integration objects required for the synchronization of a data entity is
determined by the number of operations required for each entity and the Web service type (request-
and-response or fire-and-forget).
Table 11 lists the operations supported for each entity in the Integration, the type of Web service
used to perform the operation, and the EBMs used to generate the integration objects that are
required to support the operation. When customizing the Integration, you might have to define
additional operations for an entity and use EBMs other than those listed to achieve the data
integration required.
Table 11. Operations Supported for Entities in Siebel CRM Integration to Oracle FLEXCUBE
Universal Banking
CreateCustomerPartyResponseEBM
Update Fire-and-forget UpdateCustomerPartyEBM
QueryCustomerPartyListResponseEBM
QueryCustomerPartyEBM
QueryCustomerPartyResponseEBM
QueryDepositAccountResponseEBM
QueryLoanAccountResponseEBM
QueryBankGuaranteeResponseEBM
Line of Credit Query Request-response QueryLineOfCreditEBM
QueryLineOfCreditResponseEBM
Table 11. Operations Supported for Entities in Siebel CRM Integration to Oracle FLEXCUBE
Universal Banking
CreateServiceRequestResponseEBM
QueryServiceRequestListResponseEBM
QueryMarketingOfferListResponseEBM
1 “Installing the Oracle AIA Foundation Pack Enterprise Object Library” on page 80
http://edelivery.oracle.com
2 Install the Oracle AIA Foundation Pack as described in Oracle® Fusion Middleware Installation
and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack 11g Release
1 (11.1.1.4.0).
■ Select the following installation options: Select the Copy AIA Software Only option.
Choosing this option requires that you manually complete the installation.
3 After the installation, verify that the Oracle AIA Foundation Pack directory structure is as follows
on your local computer:
AIA_HOME\AIAMetaData\AIAComponents\EnterpriseObjectLibrary\Industry\BankingA
ndWealthManagement\EBO\Entity\
AIA_HOME\AIAMetaData\AIAComponents\EnterpriseBusinessServiceLibrary\Industry
\BankingAndWealthManagement\EBO\Entity\
where:
■ The document tag used by Oracle AIA objects exceeds the limit of 255 characters for comments
in Siebel CRM.
■ Weakly typed schema (##any, ##other) are not supported in Siebel CRM.
To prepare to import the enterprise objects into Siebel Tools, perform the steps in the following
procedure.
2 Edit each file as indicated in the Changes Required column of Table 12.
\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement None
\EBO\Enity\V1\EnityEBM.xsd
\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement None
\Common\V2\Meta.xsd
\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement None
\Common\V2\CodeLists.xsd
\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement None
\Common\V2\DataTypes.xsd
\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement None
\Custom\Common\V2\CustomCommonComponents.xsd
\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement None
\Custom\EBO\LoanAccount\V1\CustomLoanAccountEBO.xsd
\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement None
\Common\V2\WS-Addressing.xsd
\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement None
\Common\V2\access_control-xacml-2.0-context-schema-cd-
04.xsd
\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement None
\Common\V2\access_control-xacml-2.0-policy-schema-cd-04.xsd
\EnterpriseObjectLibrary\Infrastructure\V1\Meta.xsd ■ Put
<xsd:documentation>
tag text in a comment.
<xsd:import
namespace="http://
schemas.xmlsoap.org/
ws/2003/03/addressing"
schemaLocation="WS-
Addressing.xsd"/>
c Browse to the location of the XSD file that you want to use as follows, then click Next:
AIA_HOME\AIAMetaData\AIAComponents\EnterpriseObjectLibrary\Industry\BankingA
ndWealthManagement\EBO\Entity\V1\Entity\EBM.xsd
where:
6 Select the source object according to the operation required, for example,
CreateLoanAccountResponseEBM, and assign the same name to the integration object. Click
Next.
7 On the Choose Integration Components screen, click the plus sign to expand the list of
integration components, then select the integration components you require for the new
integration object. Click Next.
After the successful import of the EBM.xsd file, an integration object with the name you assigned
in Step 6 is created. You can view integration objects in the Integration Objects list.
The EAI Extensible Stylesheet Language Transformation (XSLT) service is used to transform data
from an external integration object structure to a Siebel integration object structure. XSL
transformation (XSLT) files for each entity and operation used in the Integration are available in the
SIEBSRVR\XSLT directory, where SIEBSRVR is the Siebel Server installation directory. These files are
called at run-time by the Integration workflows to map data between Oracle FLEXCUBE Universal
Banking and Siebel CRM. For information on the Integration workflows, see Siebel Finance Guide.
When customizing the Integration, verify that an XSLT file exists for the entity required for your
customization, and that it supports the field data mapping required. If a file does not exist, or if it
does not support the field mappings required, you must create a new XSLT file or amend an existing
XSLT file for the new entities or fields being synchronized, as described in the following procedure.
■ If you have imported a new entity into Siebel Tools to use in the Integration, as described in
“Importing EBMs into Siebel Tools” on page 80, you must create an XSLT file for the new entity.
Proceed to step Step 2.
■ If the customization involves mapping additional fields for an entity that is already supported
in the Integration, an XSLT file for the entity already exists in the SIEBSRVR\XSLT directory.
Proceed to Step 3.
2 Create a new XSLT file for the entity and add it to the SIEBSRVR\XSLT directory.
For an example of an XSLT file created for an entity imported into Siebel Tools for use in the
Integration, see “Example of an XSLT File Created For a New Entity” on page 84.
3 Edit the appropriate XSLT file for the entity using an XML editor and add the new data mapping
information.
NOTE: The file in this topic is listed for example purposes only; it is not an actual representation of
either an AIA EBM or a Siebel CRM XSD file.
<xsl:template match="/">
<xsl:apply-templates select="CreateLoanAccountResponseEBM"/>
</xsl:template>
<xsl:template match="CreateLoanAccountResponseEBM">
<xsl:apply-templates select="EBMHeader"/>
</xsl:template>
<xsl:template match="EBMHeader">
<xsl:apply-templates select="Sender"/>
</xsl:template>
<xsl:template match="Sender">
<SiebelMessage>
<Account>
<AccountId>
<xsl:value-of select="Id"/>
</AccountId
<FullName>
<xsl:value-of select="Name"/> <!-- this step maps the value in the Name field
(Aaron)in the source XML file to the FullName field in the Target xml file-->
</FullName>
</Account>
</SiebelMessage
</xsl:template>
</xsl:stylesheet>
After you create a new workflow or customize an existing workflow, you must deploy the relevant
workflow by publishing it as an inbound Web service and then generating a WSDL file for the new
Web service. Both tasks are described in this topic.
For detailed information on each of the workflows used in the Integration, see Siebel Finance Guide.
The workflow XML files for the Loan Account create and upsert workflows used in the Integration are
listed in Appendix A, “Sample Workflow Files.” You can use these workflow files as a reference when
customizing workflows for your integration environment.
For more information, see Integration Platform Technologies: Siebel Enterprise Application
Integration.
When publishing the workflow as an inbound Web service, specify the values shown in the
following table.
Field Value
Name (Service Ports list) When creating the inbound service port record, the name
assigned to the port in the Name field must be the same as the
port name defined in the EBS WSDL.
Name (Operations list) When creating the operation record for the new service port, the
operation name must be the same as the operation name defined
in the EBS WSDL.
For example, for the Loan Account entity, the port name is
BankingAndWealthManagementLoanAccountEBS and the operation name is CreateLoanAccount.
a Navigate to the Administration - Web Services screen, then the Inbound Web Services view.
b Select the inbound Web service that you want to publish, then click Generate WSDL.
3 Test each operation in the WSDL file, using the soapUI testing tool.
AIA_HOME\AIAMetaData\AIAComponents\EnterpriseBusinessServiceLibrary\Industry\Ba
nkingAndWealthManagement\EBO\Entity\V1
where:
■ Entity is the name of the entity, for example, Loan Account, used in the customization
■ AIA_HOME is the Oracle AIA Foundation Pack installation directory
2 Edit the WSDL file you have just copied by replacing the sections of the file that relate to the
operation specified when you deployed the customized workflow (Step 1 on page 87) with the
corresponding sections of the WSDL file you generated in the Siebel application (Step 2 on
page 87).
NOTE: Do not change the names of the namespaces in the Oracle AIA WSDL file when copying
information from the Siebel WSDL file. Continue to use the ebo and ebs prefixes.
■ <schema>
■ <message>
■ <ports>
■ <binding>
3 Save the changes you made to the WSDL file, and place it in the same directory where it was
originally located, that is, in:
AIA_HOME\AIAMetaData\AIAComponents\EnterpriseBusinessServiceLibrary\Industry\Ba
nkingAndWealthManagement\EBO\Entity\V1.
Use this WSDL file for future testing and publishing to consumer applications.
4 In the Siebel application, navigate to the Administration - Web Services screen, then the Inbound
Web Services view.
5 Select the customized inbound Web service previously deployed in “Deploying a Customized
Workflow” on page 86.
6 In the Namespace field, change the name to the namespace name specified in the EBS WSDL
located in:
AIA_HOME\AIAMetaData\AIAComponents\EnterpriseBusinessServiceLibrary\Industry\
BankingAndWealthManagement\EBO\Entity\V1
For example, for the LoanAccount Create workflow, the following values are specified:
❏ Inbound Web service name: FINCORP BIB Loan Account Upsert FAF Workflow
❏ Operation: CreateLoanAccount
NOTE: The WSDLs for the Siebel CRM Web services used in the Integration 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” on page 18.
** Oracle Corporation **
** This is an Entity EBS, BASED ON CRUD OPERATIONS **
** We always include the wsdl,xsd, soap, our documentation, and Core Common
namespaces. Always the same prefixes. **
** Need to define namespaces for EBO and EBS, and always use these same prefixes -
ebo and ebs. **
** Need to define the target namespace equal to the EBS namespace. Also define a
name, in the form of - name+EBS. **
Copyright (c) 2007, 2010, Oracle and/or its affiliates. All rights reserved.
<types>
<xsd:schema targetNamespace="http://xmlns.oracle.com/EnterpriseServices/
LoanAccount/V1" elementFormDefault="qualified">
<xsd:import namespace="http://xmlns.oracle.com/EnterpriseObjects/Core/
EBO/LoanAccount/V1" schemaLocation="../../../../../../EnterpriseObjectLibrary/
Industry/BankingAndWealthManagement/EBO/LoanAccount/V1/LoanAccountEBM.xsd" />
<xsd:import namespace="http://xmlns.oracle.com/EnterpriseObjects/Core/
Common/V2" schemaLocation="../../../../../../EnterpriseObjectLibrary/Industry/
BankingAndWealthManagement/Common/V2/Meta.xsd" />
</xsd:schema>
<xsd:element name="UpdateLoanAccount_Input">
<xsd:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="CreateLoanAccount_Input">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="ebo:CreateLoanAccountEBM"></xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
<message name="UpdateLoanAccount_Input">
<part name="UpdateLoanAccount_Input"
element="ebo:UpdateLoanAccount_Input"></part>
</message>
<message name="CreateLoanAccount_Input">
<part name="CreateLoanAccount_Input"
element="ebo:CreateLoanAccount_Input"></part>
</message>
<portType name="BankingAndWealthManagementLoanAccountEBS">
<operation name="UpdateLoanAccount">
<input message="ebs:UpdateLoanAccount_Input"></input>
</operation>
<operation name="CreateLoanAccount">
<input message="ebs:CreateLoanAccount_Input"></input>
</operation>
</portType>
<binding name="BankingAndWealthManagementLoanAccountEBS"
type="ebs:BankingAndWealthManagementLoanAccountEBS">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document" />
<operation name="UpdateLoanAccount">
<soap:operation soapAction="document/http://xmlns.oracle.com/
EnterpriseObjects/Core/EBO/LoanAccount/V1:UpdateLoanAccount"></soap:operation>
<input>
<soap:body use="literal"></soap:body>
</input>
</operation>
<operation name="CreateLoanAccount">
<soap:operation soapAction="document/http://xmlns.oracle.com/
EnterpriseObjects/Core/EBO/LoanAccount/V1:CreateLoanAccount"></soap:operation>
<input>
<soap:body use="literal"></soap:body>
</input>
</operation>
</binding>
<service name="BankingAndWealthManagementLoanAccountEBSV1">
<port binding="ebs:BankingAndWealthManagementLoanAccountEBS"
name="BankingAndWealthManagementLoanAccountEBS">
<soap:address location="http://sdc78514svqe/eai_enu/
start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&UserName=SADMIN&
amp;Password=MSSQL" />
</port>
</service>
</definitions>
■ Data area. It identifies the operation to be performed by the EBM and contains the content
payload.
■ EBM header. It contains information used to process the message content. For request-and-
response Web services, Oracle FLEXCUBE Universal Banking and Siebel CRM message IDs and
errors are captured in the Header section of the EBM.
This appendix lists the XML files for the Loan Account create and Loan Account upsert workflows used
in Siebel CRM Integration to Oracle FLEXCUBE Universal Banking. You can use these files as examples
if you want to change the existing integration workflows, or create new workflows, when customizing
the Integration. The files are listed in the following topics:
NOTE: In this guide, the term, the Integration, refers to Siebel CRM Integration to Oracle FLEXCUBE
Universal Banking.
</WF_STEP_BRANCH>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_BRANCH_CRITERIA>
</WF_STEP_BRANCH>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP>
</WORKFLOW_PROCESS>
</PROJECT>
</REPOSITORY>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP_BRANCH>
</WF_STEP>
</WF_STEP_BRANCH>
</WF_STEP_BRANCH>
</WF_STEP>
</WORKFLOW_PROCESS>
</PROJECT>
</REPOSITORY>
This appendix lists the data mappings used when Oracle Data Integrator retrieves data from Oracle
FLEXCUBE Universal Banking staging tables and loads it into the Siebel Enterprise Integration
Manager (EIM) tables during the batch data integration process. It includes the following topics:
■ Mapping of Contract Data (Bills and Collections) to Siebel CRM on page 122
NOTE: In the tables in this appendix, the term, the Integration, refers to Siebel CRM Integration to
Oracle FLEXCUBE Universal Banking.
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
Branch_Code Internal Location S_ORG_EXT LOC EIM_FN_ ACC_LOC
Division ACCNT1
Part of User
Key
PARDIV_
ACCNT_LOC
PARDIV_ACC
NT_NAME
ACCNT_
NAME
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
Address3 CUT Address Apartment S_ADDR_PER ADDR_LINE_3 EIM_ADDR_ AP_ADDR_
Number PER LINE_3
Table 14 shows the mapping of product data from the Oracle FLEXCUBE Universal Banking
CSTM_PRD_HANDOFF table to Siebel CRM.
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
PRD_CODE Internal Name S_PROD_INT NAME EIM_PROD_INT NAME
Product
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
RECORD Internal Version S_PROD_INT STATUS_CD EIM_PROD_INT STATUS_CD
STATUS Product Status
PROD_PROD
_NAME
Table 15 shows the mapping of account class data from the Oracle FLEXCUBE Universal Banking
STTM_ACLASS_HANDOFF staging table to Siebel CRM.
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
ACCOUNT_ Internal Name S_PROD_INT NAME EIM_PROD_INT NAME
CLASS Product
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
ACCOUNT_ Product Line Name S_PROD_LN NAME EIM_PROD_LN PRDLN_
CODE NAME
PROD_PROD
_NAME
BRANCH_LIST
■ Checking account, savings account (CASA) and retail deposit data is stored in the
STTM_ACCLASS_UDE_VALHF staging table.
This topic shows how the data stored in these tables is mapped to Siebel CRM.
Table 16 shows the mapping of loan product rate data from the Oracle FLEXCUBE Universal Banking
CLTM_LOAN_RATE_HDF staging table to Siebel CRM.
.
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Base Siebel Base Siebel EIM Table
Attribute ent Field Table Column Table Column
CCY_CODE Internal Currency S_PROD_INT CARY_COST_ EIM_FN_PRDI PROD_CARY
Product Code CURCY_CD NT1 COSTCURCY
(Currency)
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Base Siebel Base Siebel EIM Table
Attribute ent Field Table Column Table Column
RULE_ FIN Prod Rate S_CONDITION DESC_TEXT EIM_FN_CND CND_DESC_
DESCRIPTION Rate Condition TN TEXT
Condition
(Rule Condition S_CONDITION TYPE_CD CND_TYPE_C
Description) Type D
COND_CND_
TYPE_CD1
PRODRATE_ID RT_DEDUCT
_AMT
PROD_BI
PROD_NAME
RT_TYPE_CD
Table 17 shows the mapping of corporate deposit product rate data from the Oracle FLEXCUBE
Universal Banking LDTM_CDRATE_HANDOFF staging table to Siebel CRM.
Table 17. Mapping of Corporate Deposit Product Rate Data to Siebel CRM
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
PRODUCT_ FIN Product Product Id S_PROD_ PROD_ID EIM_FN_ PROD_NAME
CODE Rates RATE PRDINT1
PROD_BU
Table 17. Mapping of Corporate Deposit Product Rate Data to Siebel CRM
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
DEFAULT_ FIN Product Margin S_PROD_ MARGIN_ EIM_FN_PRDI RT_MARGIN_
SPREAD Rates Spread RATE SPREAD NT1 SPREAD
Table 18 shows the mapping of CASA and retail deposit product rate data from the Oracle FLEXCUBE
Universal Banking STTM_ACCLASS_UDE_VALHF staging table to Siebel CRM.
Table 18. Mapping of CASA and Retail Deposit Product Rate Data to Siebel CRM
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
BRANCH_ Internal Vendor S_PROD_INT OU_ID EIM_PROD_ VENDR_
CODE Product Location INT ACCNT_BU
VENDR_
ACCNT_LOC
VENDR_
ACCNT_NAME
Table 18. Mapping of CASA and Retail Deposit Product Rate Data to Siebel CRM
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
CHARGE_ FIN Product Min Amount S_PROD_ MIN_AMT EIM_FN_ RT_MIN_AMT
AMOUNT Rates RATE PRDINT1
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
Available FINS BIB Available S_FN_LIMIT AVAILABLE_ EIM_FN_ LMT_AVAILAB
Amount Limit Details Amount AMT LIMIT LE_AMT
LMT_CON_
PRIV_FLG
LMT_PERSON
_UID
LMT_ACCOUN
TACCNTLO
LMT_ACCOUN
TACCNTNA
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
Main Line ID FINS BIB Main Line S_FN_LIMIT PAR_LIMIT_ID EIM_FN_ LMT_PAR_
Limit Details ID LIMIT LIMIT_NUM
LMT_PAR_
LMT_ACC_BU
LMT_PAR_
LMT_ACCLOC
LMT_PAR_
LMTACCNAME
LMT_PAR_
LMT_CON_BU
LMT_PARLMT
CONPRIVF
LMT_PARLMT
PERSONUI
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
Product Code FINS BIB Product Code S_FN_ PROD_ID EIM_FN_ MNDT_PROD
Mandate MANDATE ASSET1 _NAME
MNDT_PROD
_BU
MNDT_CON_
PRIV_FLG
MNDT_CON_
BU
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
Customer FINS BIB Account Id S_FN_ ACCOUNT_ID EIM_FN_ MNDT_ACCO
Mandate MANDATE ASSET1 UNTACCNTN
MNDT_ACCO
UNTACCNTL
MNDT_ACCO
UNTACC_BU
AST_BU
AST_PROD_
BU
AST_PROD_
NAME
AST_REV_
NUM
Direct Debit FINS BIB Direct Debit S_FN_ DIRDBT_AGR_ EIM_FN_ MNDTDIRDB
Agreement Mandate Agreement MANDATE REQ_FLG ASSET1 TAGREXSFL
Flag Flag
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
CONT_REF_ FINS BIB Contract S_ASSET ASSET_NUM EIM_ASSET AST_ASSET_
NO Contract Reference NUM
Num
BRANCH_AC
CNT_LOC
BRANCH_AC
CNT_NAME
OWNER_ACC
NT_LOC
OWNER_ACC
NT_NAME
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
CUSTOMER_ FINS BIB Contact Id S_ASSET_CO CONTACT_ID EIM_ASSET CON_CON_
ID Contract N PRIV_FLG
CON_
PERSON_UID
CON_CON_
BU
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
CONTRACT_ FINS BIB Contract S_ASSET ASSET_NUM EIM_ASSET AST_ASSET_
REF_NO Contract Reference NUM
Num
Siebel
Oracle Business Siebel EIM
FLEXCUBE Compon- Siebel Siebel Siebel Base Siebel EIM Table
Attribute ent Field Base Table Column Table Column
PRODUCT_ FINS BIB Product Id S_ASSET PROD_ID EIM_ASSET AST_PROD_
CODE Contract NAME;
AST_PROD_
BU
BRANCH_
ACCNT_LOC
BRANCH_
ACCNT_
NAME
OWNER_
ACCNT_LOC
OWNER_
ACCNT_
NAME
CON_
PERSON_UID
CON_CON_
BU
This appendix lists the mappings between data in Oracle FLEXCUBE Universal Banking and data in
Siebel CRM that are used during the online synchronization of data in Siebel CRM Integration to
Oracle FLEXCUBE Universal Banking.
NOTE: In this guide, the term, the Integration, refers to Siebel CRM Integration to Oracle FLEXCUBE
Universal Banking.
CustomerPartyEBM
The CustomerPartyEBM integration objects, associated with the Customer Party EBO, are used in
create, update and query operations in the Integration. The application mappings used by the
CustomerPartyEBM integration objects for each of these operations is provided in the following
topics:
NOTE: In the tables in this appendix Oracle FLEXCUBE Universal Banking has been abbreviated as
follows: Oracle FLEXCUBE.
CreateCustomerPartyEBM
CreateCustomerPartyEBM is used to synchronize customers created in Oracle FLEXCUBE Universal
Banking with Siebel CRM.
Operation
Create
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
■ CreateCustomerPartyEBM
■ CreateCustomerPartyResponseEBM
CreateCustomerPartyEBM
Table 23 lists the mapping information for the CreateCustomerPartyEBM.
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
/TaxCode FCUBS ST-New FCUBS_ Contact Tax Code BIB Tax Code
Customer Customer- NOTIFICA- Account
Service Notify- TION BC
MSG.xsd /FCUBS_
NOTIF_
IDENTIFIER
Customer-
Full/
TAXGROUP
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
/Person/ FCUBS ST-New FCUBS_ BIB KYC Status BIB KYC Status
Person Customer Customer- NOTIFICA- Contact Account Flag
Financial Service Notify- TION BC BC
Profile MSG.xsd /FCUBS_
/Financial NOTIF_
Profile/Status/ IDENTIFIER
Code Customer-
Full
/Organization
/KYCSTAT
/Organization
Financial
Profile/
Financial
Profile/Status/
Code
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
/Customer FCUBS ST-New FCUBS_ BIB Bank Code BIB Bank Code
PartyFinancial Customer Customer- NOTIFICA- Contact Account
ServiceProfile Service Notify- TION BC
/Financial MSG.xsd /FCUBS_
Institution NOTIF_
Reference/ IDENTIFIER
PartyIdentific Customer-
ation/ID Full/LBRN
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
CreateCustomerPartyResponseEBM
Table 24 lists the mapping information for the CreateCustomerPartyResponseEBM.
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
QueryCustomerPartyEBM
QueryCustomerPartyEBM is used to retrieve customer data from Oracle FLEXCUBE Universal
Banking.
Operation
Query
Service Consumer
Siebel CRM
Service Provider
Oracle FLEXCUBE Universal Banking
■ QueryCustomerPartyResponseEBM/DataArea/QueryCustomerPartyResponse
QueryCustomerPartyEBM
Table 25 lists the mapping information for the QueryCustomerPartyEBM.
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compo- Account
XML Path Name Object Column ent Field nent Field
QueryCustomerPartyResponseEBM
Table 26 lists the mapping information for the QueryCustomerPartyResponseEBM.
Siebel Siebel
Oracle Oracle Contact Account
FLEXCUBE Oracle FLEXCUBE Business Siebel Business Siebel
Service FLEXCUBE Interface Compon- Contact Compon Account
XML Path Name Object Column ent Field -ent Field
Siebel Siebel
Oracle Oracle Contact Account
FLEXCUBE Oracle FLEXCUBE Business Siebel Business Siebel
Service FLEXCUBE Interface Compon- Contact Compon Account
XML Path Name Object Column ent Field -ent Field
/TaxCode FCUBS ST-Query FCUBS_RES_ Contact Tax Code BIB Tax Code
Customer Customer- ENVFCBUBS_ Account
Service Res-Full- BODY/ BC
MSG.xsd Customer-
Full/
TAXGROUP
/Customer Not Not Derived field. FINS BIB Main Line FINS BIB Main Line
PartyCredit applicable applicable Main Line Limit Number Limit Number
Profile/ taken from Details Details
Customer table.
PartyLineOf
Credit/Parent
LineOfCredit
Reference
/LineOfCredit
Identification
/ID
Siebel Siebel
Oracle Oracle Contact Account
FLEXCUBE Oracle FLEXCUBE Business Siebel Business Siebel
Service FLEXCUBE Interface Compon- Contact Compon Account
XML Path Name Object Column ent Field -ent Field
Siebel Siebel
Oracle Oracle Contact Account
FLEXCUBE Oracle FLEXCUBE Business Siebel Business Siebel
Service FLEXCUBE Interface Compon- Contact Compon Account
XML Path Name Object Column ent Field -ent Field
QueryCustomerPartyListEBM
QueryCustomerPartyListEBM is used to retrieve contact or account data from Siebel CRM and to
retrieve prospect data from Siebel CRM.
Operation
Query
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
■ Response. /QueryCustomerPartyListResponseEBM/DataArea/QueryCustomerPartyListResponse
QueryCustomerPartyListEBM
Table 27 lists the mapping information for the QueryCustomerPartyListEBM.
Value is
OVER
FLOW if
Contain
records
equals
MaxItems
QueryCustomerPartyListResponseEBM
Table 28 lists the mapping information for the QueryCustomerPartyListResponseEBM.
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
/Customer FCUBS ST-Query FCUBS_ BIB Bank Code BIB Bank Code
PartyFinancial Customer Customer- RES_ENV/ Contact BC Account
ServiceProfile Service Res-Full- FCBUBS_ BC
/Financial MSG.xsd BODY/
Institution Customer-
Reference Full/LBRN
/Party
Identification
/ID
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
UpdateCustomerPartyEBM
UpdateCustomerPartyEBM is used to:
Operation
Update
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
/TaxCode FCUBS ST-Modify FCUBS_ Contact Tax Code BIB Tax Code
Customer Customer NOTIFICAT Account
Service -Notify ION/ BC
-MSG.xsd FCUBS_NO
TIF_IDENTI
FIER/
Customer-
Full/
TAXGROUP
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
Siebel Siebel
Oracle Oracle Oracle Contact Account
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel Business Siebel
Service Interface Interface Compon- Contact Compon- Account
XML Path Name Object Column ent Field ent Field
QueryLineOfCreditEBM
The QueryLineOfCreditEBM integration objects, associated with the LineOfCredit EBO, are used in
query operations in the Integration to retrieve limit information from Oracle FLEXCUBE Universal
Banking. The application mappings used by the QueryLineOfCreditEBM integration objects for the
query operation are described in this topic.
Operation
Query
Service Consumer
Siebel CRM
Service Provider
Oracle FLEXCUBE Universal Banking
■ QueryLineOfCreditResponseEBM
QueryLineOfCreditEBM
Table 30 lists the mapping information for the QueryLineOfCreditEBM.
Oracle Oracle
Oracle FLEXCUBE FLEXCUBE Siebel Contact Siebel
FLEXCUBE Interface Interface Business Contact
XML Path Service Name Object Column Component Field
GEM_REQ_ENV/
GEM_BODY/
Facility-Full/
LINESERIAL
QueryLineOfCreditResponseEBM
Table 31 lists the mapping information for the QueryLineOfCreditResponseEBM.
GEM_RES_ENV/
GEM_BODY/
Facility-Full/
LINESERIAL
QueryDocumentaryCollectionEBM
The QueryDocumentaryCollectionEBM integration objects, associated with the Documentary
Collection EBO, are used in query operations in the Integration to retrieve contract information from
Oracle FLEXCUBE Universal Banking - Bills and Collections. The application mappings used by the
QueryDocumentaryCollectionEBM integration objects for the query operation are described in this
topic.
Operation
Query
Service Consumer
Siebel CRM
Service Provider
Oracle FLEXCUBE Universal Banking
■ QueryDocumentaryCollectionResponseEBM/DataArea/QueryDocumentaryCollectionResponse
QueryDocumentaryCollectionEBM
Table 32 lists the mapping information for the QueryDocumentaryCollectionEBM.
Siebel
Oracle Oracle Contact Siebel
FLEXCUBE FLEXCUBE Oracle FLEXCUBE Business Contact
XML Path Service Name Interface Object Interface Column Component Field
QueryDocumentaryCollectionResponseEBM
Table 33 lists the mapping information for the QueryDocumentaryCollectionResponseEBM.
Oracle Oracle
Oracle FLEXCUBE FLEXCUBE Siebel Contact Siebel
FLEXCUBE Interface Interface Business Contact
XML Path Service Name Object Column Component Field
Oracle Oracle
Oracle FLEXCUBE FLEXCUBE Siebel Contact Siebel
FLEXCUBE Interface Interface Business Contact
XML Path Service Name Object Column Component Field
/LineOfCredit Not applicable Not applicable Value is derived, FINS BIB LC Reference
Reference/ based on Contract Number
LineOfCredit OURLCREF or
Identification/Id THRLCREF.
Oracle Oracle
Oracle FLEXCUBE FLEXCUBE Siebel Contact Siebel
FLEXCUBE Interface Interface Business Contact
XML Path Service Name Object Column Component Field
/Financial Not applicable Not applicable Branch Code FINS BIB Branch Code
InstitutionBranch Contract
BusinessUnit
Reference/
BusinessUnit
Identification/ID
Drawee
Oracle Oracle
Oracle FLEXCUBE FLEXCUBE Siebel Contact Siebel
FLEXCUBE Interface Interface Business Contact
XML Path Service Name Object Column Component Field
/Documentary Not applicable Not applicable Country code FINS BIB Party
CollectionDrawee/ Contract Parties Country
Documentary VBC
CollectionDrawee
PersonParty/Person
PartyReference/
LocationReference/
Address/Country
Code
Drawer
/Documentary Not applicable Not applicable Country code FINS BIB Party
CollectionDrawer/ Contract Parties Country
Documentary VBC
CollectionDrawer
PersonParty/Person
PartyReference/
LocationReference/
Address/Country
Code
Oracle Oracle
Oracle FLEXCUBE FLEXCUBE Siebel Contact Siebel
FLEXCUBE Interface Interface Business Contact
XML Path Service Name Object Column Component Field
Discrepancy
QueryDocumentaryCreditEBM
The QueryDocumentaryCreditEBM integration objects, associated with the Documentary Credit EBO,
are used in query operations in the Integration to retrieve contract information from Oracle
FLEXCUBE Universal Banking- Letters Of Credit. The application mappings used by the
QueryDocumentaryCreditEBM integration objects for the query operation are described in this topic.
Operation
Query
Service Consumer
Siebel CRM
Service Provider
Oracle FLEXCUBE Universal Banking
■ QueryDocumentaryCreditEBMResponse/DataArea/QueryDocumentaryCreditResponse
QueryDocumentaryCreditEBM
Table 34 lists the mapping information for the QueryDocumentaryCreditEBM.
Oracle
Oracle FLEXCUBE Siebel Contact Siebel
FLEXCUBE Interface Oracle FLEXCUBE Business Contact
XML Path Service Name Object Interface Column Component Field
/Identification/ Not applicable Not applicable Branch Code FINS BIB Branch Code
ContextID (derived) Contract
QueryDocumentaryCreditResponseEBM
Table 35 lists the mapping information for the QueryDocumentaryCreditResponseEBM.
/Financial Not applicable Not applicable Branch Code FINS BIB Branch
Institution Contract Code
BranchBusiness
UnitReference/
BusinessUnit
Identification/ID
Applicant
/CustomerParty Not applicable Not applicable Party Country FINS BIB Party
Reference Contract Parties Country
/Location VBC
Reference/
Address/Country
Code
Advising Bank
/Documentary Not applicable Not applicable Party Country FINS BIB Party
CreditAdvising Contract Parties Country
Financial VBC
Institution/
Financial
Institution
Reference/
Location
Reference/
Address/Country
Code
Applicant’s Bank
/Documentary Not applicable Not applicable Party Country FINS BIB Party
CreditDrawee Contract Parties Country
Financial VBC
Institution/
Financial
Institution
Reference/
Location
Reference/
Address
/CountryCode
Beneficary
/Benificary/ Not applicable Not applicable Party Country FINS BIB Party
BenificaryPerson Contract Parties Country
Party/Person VBC
PartyReference/
Location
Reference/
Address/Country
Code
Confirming Bank
/Documentary Not applicable Not applicable Party Country FINS BIB Party
CreditConfirming Contract Parties Country
Financial VBC
Institution/
Financial
Institution
Reference/
Location
Reference/
Address/Country
Code
Reimbursing Bank
/Documentary Not applicable Not applicable Party Country FINS BIB Party
Credit Contract Parties Country
Reimbursing VBC
Financial
Institution/
Financial
Institution
Reference/
Location
Reference/
Address/Country
Code
Transferee 1
/Documentary Not applicable Not applicable Party Country FINS BIB Party
Credit Contract Parties Country
Transferring VBC
Financial
Institution/
Financial
Institution
Reference/
Location
Reference/
Address/Country
Code
Commissions
Goods Code
QueryBankGuaranteeEBM
The QueryBankGuaranteeEBM integration objects, associated with the BankGuarantee EBO, are used
in query operations in the Integration to retrieve contract information from Oracle FLEXCUBE
Universal Banking - Bank Guarantee. The application mappings used by the
QueryBankGuaranteeEBM integration objects for the query operation are described in this topic.
Operation
Query
Service Consumer
Siebel CRM
Service Provider
Oracle FLEXCUBE Universal Banking
■ QueryBankGuaranteeResponseEBM/DataArea/QueryBankGuaranteeResponse
QueryBankGuaranteeEBM
Table 36 lists the mapping information for the QueryBankGuaranteeEBM.
Siebel
Oracle Contact Siebel
FLEXCUBE Oracle FLEXCUBE Oracle FLEXCUBE Business Contact
XML Path Service Name Interface Object Interface Column Component Field
/Identification/ Not applicable Not applicable Branch Code FINS BIB Branch
ContextID Contract Code
QueryBankGuaranteeResponseEBM
Table 37 lists the mapping information for the QueryBankGuaranteeResponseEBM.
/FinancialInstitution Not applicable Not applicable Branch Code FINS BIB Branch
BranchBusinessUnit Contract Code
Reference/Business
UnitIdentification/ID
Applicant
FCUBS_RES_ENV/
FCUBS_BODY/
Contract-Details-
Full/Party-Details/
PRTYTYP
/CustomerParty Not applicable Not applicable Party Country FINS BIB Party
Reference/Location Contract Country
Reference/Address/ Parties VBC
CountryCode
Beneficiary
/Benificary/ Not applicable Not applicable Party Country FINS BIB Party
Benificary Contract Country
PersonParty/Person Parties VBC
PartyReference/
LocationReference/
Address/Country
Code
Advising Bank
FCUBS_RES_ENV/
FCUBS_BODY/
Contract-Details-
Full/Party-Details/
PRTYTYP
/BankGuarantee Not applicable Not applicable Party Country FINS BIB Party
AdvisingFinancial Contract Country
Institution/Financial Parties VBC
InstitutionReference/
LocationReference/
Address/
CountryCode
Commissions
QueryMarketingOfferEBM
The QueryMarketingOfferEBM integration objects, associated with the MarketingOfferEBO, are used
in query operations in the Integration to retrieve offers from Siebel CRM with a status of Contact
Specific - Active. The application mappings used by the QueryMarketingOfferEBM integration objects
for the query operation are described in this topic.
Operation
Query
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
■ QueryMarketingOfferListResponseEBM/DataArea/QueryMarketingOfferListResponse
QueryMarketingOfferEBM
Table 38 lists the mapping information for the QueryMarketingOfferEBM.
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Interface Oracle FLEXCUBE Business Contact
XML Path Service Name Object Interface Column Component Field
QueryMarketingOfferResponseEBM
Table 39 lists the mapping information for the QueryMarketingOfferResponseEBM.
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Interface Oracle FLEXCUBE Business Contact
XML Path Service Name Object Interface Column Component Field
CreateSalesOpportunityEBM
The CreateSalesOpportunityEBM integration object, associated with the SalesOpportunityEBO, is
used in the following create operations in the Integration:
The application mappings used by the CreateSalesOpportunityEBM integration object for this
operation are described in this topic.
Operation
Create
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
Table 40 lists the mapping information for the CreateSalesOpportunityEBM request message.
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Interface Oracle FLEXCUBE Business Contact
XML Path Service Name Object Interface Column Component Field
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Interface Oracle FLEXCUBE Business Contact
XML Path Service Name Object Interface Column Component Field
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Interface Oracle FLEXCUBE Business Contact
XML Path Service Name Object Interface Column Component Field
ServiceRequestEBM
The ServiceRequestEBM integration objects, associated with the ServiceRequestEBO, are used in
create, update and query operations in the Integration. The application mappings used by the
ServiceRequestEBM integration objects for each of these operations is provided in the following
topics:
CreateServiceRequestEBM
CreateServiceRequestEBM is used to create a service request in Siebel CRM.
Operation
Create
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
■ CreateServiceRequestEBM/CreateServiceRequestDataArea/CreateServiceRequestResponse
CreateServiceRequestEBM
Table 41 lists the mapping information for the CreateServiceRequestEBM message.
Oracle Siebel
FLEXCUBE Oracle Contact Siebel
Service FLEXCUBE Oracle FLEXCUBE Business Contact
XML Path Name Interface Object Interface Column Component Field
Not applicable Not applicable Not applicable Not applicable Service INS
Request Product
Oracle Siebel
FLEXCUBE Oracle Contact Siebel
Service FLEXCUBE Oracle FLEXCUBE Business Contact
XML Path Name Interface Object Interface Column Component Field
Oracle Siebel
FLEXCUBE Oracle Contact Siebel
Service FLEXCUBE Oracle FLEXCUBE Business Contact
XML Path Name Interface Object Interface Column Component Field
CreateServiceRequestResponseEBM
Table 42 lists the mapping information for the CreateServiceRequestResponseEBM.
Oracle Siebel
FLEXCUBE Contact Siebel
Service Oracle FLEXCUBE Oracle FLEXCUBE Business Contact
XML Path Name Interface Object Interface Column Component Field
Oracle Siebel
FLEXCUBE Contact Siebel
Service Oracle FLEXCUBE Oracle FLEXCUBE Business Contact
XML Path Name Interface Object Interface Column Component Field
UpdateServiceRequestEBM
UpdateServiceRequestEBM is used to update service request data in Siebel CRM.
Operation
Create
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
Table 43 lists the mapping information for the UpdateServiceRequestEBM request message.
Oracle Siebel
FLEXCUBE Oracle Contact Siebel
Service FLEXCUBE Oracle FLEXCUBE Business Contact
XML Path Name Interface Object Interface Column Component Field
Oracle Siebel
FLEXCUBE Oracle Contact Siebel
Service FLEXCUBE Oracle FLEXCUBE Business Contact
XML Path Name Interface Object Interface Column Component Field
QueryServiceRequestListEBM
QueryServiceRequestListEBM is used to retrieve service request data from Siebel CRM.
Operation
Query
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
■ QueryServiceRequestListResponseEBM/DataArea/QueryServiceRequestListResponse
QueryServiceRequestListEBM
Table 44 lists the mapping information for the QueryServiceRequestListEBM request message.
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Interface Oracle FLEXCUBE Business Contact
XML Path Service Name Object Interface Column Component Field
Element Path = Not applicable Not applicable Values are I or C Service Not
"Customer Type" (Individual customer, Request applicable
Corporate customer)
Element Value =
<Value>
QueryServiceRequestListResponseEBM
Table 45 lists the mapping information for the QueryServiceRequestListResponseEBM.
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Interface Oracle FLEXCUBE Business Contact
XML Path Service Name Object Interface Column Component Field
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Interface Oracle FLEXCUBE Business Contact
XML Path Service Name Object Interface Column Component Field
/CustomerParty Not applicable Not applicable Values are I or C Not applicable Not
Reference/Party (Individual customer, applicable
Identification/ Corporate customer)
ApplicationObject
Key/ContextID
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Interface Oracle FLEXCUBE Business Contact
XML Path Service Name Object Interface Column Component Field
CreateCustomerInteractionEBM
The CreateCustomerInteractionEBM integration object, associated with the CustomerInteractionEBO,
is used to create an activity in Siebel CRM. The application mappings used by the
CreateCustomerInteractionEBM integration object for this operation are described in this topic.
Operation
Create
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
FCUBS_
NOTIFICATION/
FCUBS_NOTIF_
IDENTIFIER/
Instruction-
Details/DRACC
FCUBS_
NOTIFICATION/
FCUBS_NOTIF_
IDENTIFIER/
Instruction-
Details/
DRACCBRN
Deposit AccountEBM
The Deposit Account EBM integration objects, associated with the Deposit Account EBO, are used in
create, update and query operations in the Integration. The application mappings used by the
DepositAccountEBM integration objects for each of these operations is provided in the following
topics:
CreateDepositAccountEBM
CreateDepositAccountEBM is used to create account links in Siebel CRM.
Operation
Create and Update
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
Table 47 lists the mapping information used by the CreateDepositAccountEBM when creating
checking and saving accounts (CASA accounts) and term deposit (TD) accounts, and when creating
corporate deposit accounts.
/FinancialAccount CASA and Not Not applicable Possible values FINCORP Sub Type
Identification TD applicable are CA or TD Account
/Application accounts (current or
ObjectKey savings
/ContextID account, term
deposit)
/Financial CASA and Not Not applicable Values are I or Not Not
AccountHolder/ TD applicable C (Individual applicable applicable
FinancialAccount accounts customer,
PersonHolder/ Corporate
PersonParty customer)
Reference/
/PersonName/ Corporate Not Not applicable Values are I or
Identification/ deposit applicable C (Individual
ApplicationObject accounts customer,
Key/ContextID Corporate
customer)
/Status/ CASA and Not Not applicable Not applicable FINCORP Contract
SubStatusCode TD applicable BIB Account Status
accounts
/Financial CASA and Not Not applicable Values are I or FINCORP Type
AccountHolder TD applicable C (Individual Account
/FinancialAccount accounts customer, Contact
PersonHolder Corporate
/PersonParty customer)
Reference/
/PersonName Corporate Not Not applicable Values are I or
/TypeCode deposit applicable C (Individual
accounts customer,
Corporate
customer)
UpdateDepositAccountEBM
UpdateDepositAccountEBM is used to:
Operation
Update
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
Table 48 lists the mapping information used by the UpdateDepositAccountEBM when checking and
saving accounts (CASA accounts) and term deposit accounts are updated.
QueryDepositAccountEBM
QueryDepositAccountEBM is used to:
Operation
Query
Service Consumer
Siebel CRM
Service Provider
Oracle FLEXCUBE Universal Banking
■ QueryDepositAccountResponseEBM/DataArea/QueryDepositAccountResponse
QueryDepositAccountEBM
Table 49 lists the mapping information for the QueryDepositAccountEBM when checking and saving
accounts (CASA accounts), term deposit accounts, and corporate deposit accounts are updated.
/Identification CASA and Not Not applicable Values are CA or Sub Type DTYPE_
/Application term deposit applicable TD (CASA TEXT
ObjectKey/ accounts account or term
ContextID deposit account)
QueryDepositAccountResponseEBM
Table 50 lists the mapping information for the QueryDepositAccountResponseEBM when checking and
saving accounts (CASA accounts), term deposit (TD) accounts, and corporate deposit (CD) accounts
are updated.
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
/FinancialAccount CASA and Not Not Values are CA, FINCORP Sub Type
Identification term applicable applicable TD, CD (Current Account
/ApplicationObject deposit or savings
Key/ContextID accounts account, term
deposit,
corporate
deposit)
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
/BookedDate CASA and Not Not Not applicable FINCORP Book Date
term applicable applicable BIB Account
deposit
accounts
/EffectiveDate CASA and Not Not Not applicable FINCORP Value Date
term applicable applicable BIB Account
deposit
accounts
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
/DepositAccount CASA and Not Not Not applicable FINCORP Start Date
Transaction term applicable applicable BIB Account
Schedule/Financial deposit Corporate
Transaction accounts Deposit
Schedule Schedule
/EffectiveTime Corporate FCUBSLD LDContract- FCUBS_RES_ENV VBC
Period/StartDate deposit Service Query-Res- /FCUBS_BODY/
Time accounts Full-MSG.xsd Cust-Account-
Full/Contract-
Schedules/
VALDT
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
Siebel
Oracle Oracle Oracle Contact
FLEXCUBE FLEXCUBE FLEXCUBE Business Siebel
Account Service Interface Interface Compon- Contact
XML Path Type Name Object Column ent Field
QueryFinancialTransactionListEBM
The QueryFinancialTransactionListEBM integration objects, associated with the Financial Transaction
EBO, are used in query operations in the Integration to retrieve financial transactions from Oracle
FLEXCUBE Universal Banking. The application mappings used by the
QueryFinancialTransactionListEBM integration objects for the query operation are provided in this
topic.
Operation
Query
Service Consumer
Siebel CRM
Service Provider
Oracle FLEXCUBE Universal Banking
■ QueryFinancialTransactionListResponseEBM/DataArea/QueryFinancialTransactionListResponse
QueryFinancialTransactionListEBM
Table 51 lists the mapping information for the QueryFinancialTransactionListEBM.
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Oracle FLEXCUBE Interface Business Contact
XML Path Service Name Interface Object Column Component Field
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Oracle FLEXCUBE Interface Business Contact
XML Path Service Name Interface Object Column Component Field
QueryFinancialTransactionListResponseEBM
Table 52 lists the mapping information for the QueryFinancialTransactionListResponseEBM.
Loan AccountEBM
The LoanAccountEBM integration objects, associated with the Loan Account EBO, are used in create,
update and query operations in the Integration. The application mappings used by the
LoanAccountEBM integration objects for each of these operations is provided in the following topics:
CreateLoanAccountEBM
CreateLoanAccountEBM is used to create account links in Siebel CRM.
Operation
Create
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
/FinancialAccount Not applicable Not applicable Value provided is FINCORP Sub Type
Identification/ CL Account
ApplicationObjectKey/
ContextID
Not applicable Not applicable Not applicable Not applicable FINCORP Acct Gen -
Account Primary
Contact Id
UpdateLoanAccountEBM
UpdateLoanAccountEBM is used to update a home loan account with a new customer ID in Siebel
CRM.
Operation
Update
Service Consumer
Oracle FLEXCUBE Universal Banking
Service Provider
Siebel CRM
Not applicable Not Not applicable Not applicable FINCORP Acct Gen -
applicable Account Primary
Contact Id
QueryLoanAccountEBM
QueryLoanAccountEBM is used to retrieve financial account information from Oracle FLEXCUBE
Universal Banking.
Operation
Query
Service Consumer
Siebel CRM
Service Provider
Oracle FLEXCUBE Universal Banking
■ QueryLoanAccountResponseEBM/DataArea/QueryLoanAccountResponse
QueryLoanAccountEBM
Table 55 lists the mapping information for the QueryLoanAccountEBM.
Oracle Siebel
Oracle FLEXCUBE Contact Siebel
FLEXCUBE Interface Oracle FLEXCUBE Business Contact
XML Path Service Name Object Interface Column Component Field
QueryLoanAccountResponseEBM
Table 56 lists the mapping information for the QueryLoanAccountResponseEBM.
/FinancialAccount Not applicable Not applicable Hard coded to CL FINCORP Sub Type
Identification Account
/ApplicationObjectKey
/ContextID
Not applicable Not applicable Not applicable Not applicable FINCORP Acct Gen -
Account Primary
Contact Id
Components
Schedules
/LoanAccount Not applicable Not applicable Running serial FINCORP BIB Component
ScheduledRepayment/ number Account Loan Id
Identification/ID Schedule VBC
/LoanAccount Not applicable Not applicable The amortized FINCORP BIB Amortized
ScheduledRepayment principal is Account Loan Principal
/EquatedInstallment derived based on Schedule VBC
TotalAmount the EMI amount
and the amount
due For the
interest
component.This
applies to
amortized loans
only.
A CreateCustomerPartyResponseEBM 143
account and contact data, inquiry from CreateDepositAccountEBM 211
Oracle FLEXCUBE 64 CreateLoanAccountEBM 254
account class data mapping 113 CreateSalesOpportunityEBM 196
account data CreateServiceRequestEBM 199
data integration 57 CSTM_PRD_HANDOFF staging table 113
transactions 67 customer address
activity data constraint 13
creating 69 updating 66
data integration 61 customer data
integration point 11 batch loading 50
CASA 11
inquiry from Siebel CRM 62
B integration 55
batch data integration origination 65
log files 47, 73 relationship details 66
overview 10 transactions 66
performing 47 customer information integration point 11
post data load tasks 49 customer modification integration point 11
process 45 customer or prospect search 11
running scenarios 47 customer workflow policies 34
staging tables 45 CustomerPartyEBM
updating periodically 50 CreateCustomerPartyEBM 126
BCTB_CONTRACT_HANDOFF staging CreateCustomerPartyResponseEBM 143
table 122
BIB_ODI_ERROR_LOG log table 73
branch data D
data integration 62 data integration
mapping 112 about 55
business process integration points activity data 61
about 11 batch synchronization 10
description 62 branch data 62
customer data 55
financial account data 57
C lead data 60
CASA and retail deposit data limit data 56
mapping 115 mandate data 62
staging table 115 offer data 59
CLTM_LOAN_RATE_HDF staging table 115 product data 62
column length, constraint 13 service request data 60
context for integration, configuring 27 data mapping
contract data, mapping 122 account class 113
corporate deposit account data branch data 112
mapping 115 CASA and retail deposit data 115
staging table 115 contract (bills and collections) 122
synchronization 11 contract (letters of credit) 123
CreateCustomerInteractionEBM 207 corporate deposit account data 115
CreateCustomerPartyEBM 126 CreateCustomerPartyEBM 127