Oracle FLEXCUBE Wealth Management Interface User Manual

Oracle FLEXCUBE Wealth Management Interface User Manual
Oracle FLEXCUBE Wealth Management Interface
Oracle FLEXCUBE Universal Banking
Release 12.0.1.13.0
[April] [2013]
Oracle Part Number E51465-01
Oracle FCPB Interface
Table of Contents
1.
ABOUT THIS MANUAL................................................................................................................................ 1-1
1.1
INTRODUCTION ........................................................................................................................................... 1-1
1.2
AUDIENCE .................................................................................................................................................. 1-1
1.3
ORGANIZATION .......................................................................................................................................... 1-1
1.4
ACRONYMS AND ABBREVIATIONS .............................................................................................................. 1-2
1.5
TERMINOLOGY ........................................................................................................................................... 1-2
1.6
GLOSSARY OF ICONS .................................................................................................................................. 1-3
1.6.1
Conventions Used in this Manual ...................................................................................................... 1-3
2.
ORACLE FCUBS – FCPB INTERFACE ..................................................................................................... 2-1
2.1
INTRODUCTION ........................................................................................................................................... 2-1
2.1.1
Details Handed off from FCUBS to Oracle FCPB ............................................................................ 2-1
2.2
DEFINING INTERFACE DETAILS FOR ORACLE FCPB ................................................................................... 2-2
2.2.1
Defining Component Details.............................................................................................................. 2-4
2.3
FATCA INTERFACE BETWEEN ORACLE FCUBS AND FCPB ...................................................................... 2-5
2.4
PROCESSING ONLINE NOTIFICATIONS......................................................................................................... 2-5
2.5
DEFINING INTERFACE DETAILS FOR DATA HANDOFF ................................................................................. 2-7
2.5.1
Term Deposit Maturity with Interest Liquidation .............................................................................. 2-8
2.5.2
Daily Accrued Interest on Term Deposits .......................................................................................... 2-9
2.5.3
Penalty on Term Deposits ................................................................................................................ 2-11
2.5.4
Loan and Liability Information ........................................................................................................ 2-13
2.5.5
Term Deposit Rollover ..................................................................................................................... 2-16
2.5.6
Segmentation Status Information ..................................................................................................... 2-16
3.
ORACLE FCPB – FCUBS INTERFACE ..................................................................................................... 3-1
3.1
INTRODUCTION ........................................................................................................................................... 3-1
3.2
DETAILS OF DATA RECEIVED FROM ORACLE FCUBS TO ORACLE FCPB .................................................. 3-1
3.3
DEFINING INTERFACE DETAILS FROM FCUBS TO FCPB ............................................................................ 3-2
3.4
TRANSFERRING DATA USING XML FILES ................................................................................................... 3-2
3.4.1
Creating Customer Data .................................................................................................................... 3-2
3.4.2
Modifying Customer Data ................................................................................................................. 3-6
3.4.3
Client Suspended Status ..................................................................................................................... 3-8
3.4.4
Broker Data ....................................................................................................................................... 3-9
3.4.5
CASA Account Creation..................................................................................................................... 3-9
3.4.6
Customer CASA Account Balances Notification .............................................................................. 3-12
3.4.7
CASA Closure/Modification ............................................................................................................ 3-13
3.4.8
TD Account Creation ....................................................................................................................... 3-15
3.4.9
TD Modification............................................................................................................................... 3-18
3.4.10
TD Pre-Mature Withdrawal ............................................................................................................. 3-19
3.4.11
TD Rollover ..................................................................................................................................... 3-20
3.5
DATA TRANSFER USING FILE UPLOAD MECHANISM ................................................................................. 3-24
3.5.1
TD Maturity along with Interest Liquidation ................................................................................... 3-24
3.5.2
Daily Accrued Interest on TD .......................................................................................................... 3-26
3.5.3
Penalty on TD (applicable in case of pre-mature partial withdrawal and pre-mature complete
withdrawal)...................................................................................................................................................... 3-27
3.5.4
Loan and Liability Information ........................................................................................................ 3-27
3.6
SEGMENT UPGRADE/DOWNGRADE INTERFACES....................................................................................... 3-29
3.6.1
Customer File Upload – Segmentation Upgrade ............................................................................. 3-30
3.6.2
Customer Account File Upload – Segmentation Upgrade ............................................................... 3-30
3.6.3
Customer Balances File Upload – Segmentation Upgrade ............................................................. 3-30
3.6.4
Customer TD Deals File Upload – Segmentation Upgrade ............................................................ 3-31
3.6.5
Customer Online Notification – Segmentation Downgrade............................................................. 3-32
3.7
ASSUMPTIONS .......................................................................................................................................... 3-32
4.
ORACLE FCPB – FCDB INTERFACE........................................................................................................ 4-1
4.1
INTRODUCTION ........................................................................................................................................... 4-1
4.1.1
Rules for Single Sign-On from Oracle FCDB to FCPB ..................................................................... 4-1
4.1.2
Investment Portfolio Details from FCPB to FCDB ........................................................................... 4-1
5.
ORACLE FCDB – FCPB INTERFACE........................................................................................................ 5-1
5.1
5.2
5.3
5.4
5.5
6.
INTRODUCTION ........................................................................................................................................... 5-1
SESSION MANAGEMENT ............................................................................................................................. 5-1
CUSTOMER FOLIO ....................................................................................................................................... 5-2
MESSAGE PROCESS..................................................................................................................................... 5-2
DAY 0 PARAMETERS................................................................................................................................... 5-2
SCREEN GLOSSARY .................................................................................................................................... 6-1
6.1
FUNCTION ID LIST...................................................................................................................................... 6-1
1.
1.1
About this Manual
Introduction
This document is designed to help acquaint you with the interface among various Oracle
FLEXCUBE products, viz; Oracle FLEXCUBE Universal Banking Solutions (FCUBS), Private
Banking (FCPB), and Direct Banking (FCDB).
This manual explains the maintenances required for the exchange of data and the type of data
being transferred between;

FCUBS and FCPB

FCPB and FCUBS

FCPB and FCDB

FCDB and FCPB
This User Manual explains the extensibility features and provides insight into the design
guidelines and principles for external parties to leverage and develop the required extensions in a
non invasive way to the primary features and functionality of the application.
Besides this User Manual, while maintaining the interface related details, you can invoke the
context sensitive help available for each field. This help encapsulates the purpose of each field
within a screen. You can obtain this information by placing the cursor on the relevant field and
striking the <F1> key on the keyboard.
1.2
Audience
This manual is intended for the following User/User Roles:
1.3
Role
Function
Back office data entry Clerks
Input functions for maintenance related to the
interface
Back office Managers/Officers
Authorization functions
End of day operators
Processing during end of day/ beginning of day
Implementation Partners
Provide customization, configuration and
implementation services
Organization
This manual is organized into the following chapters:
Chapter 1
About this Manual gives information on the intended audience. It also lists the
various chapters covered in this User Manual.
1-1
1.4
1.5
Chapter 2
Oracle FCUBS- FCPB Interface deals with the maintenances required for the
interface and its further processing.
Chapter 3
Oracle FCPB – FCUBS Interface deals with the maintenances required in FCPB
to exchange information between FCUBS and FCPB
Chapter 4
Oracle FCPB – FCDB Interface deals with the maintenances required in FCPB to
exchange information between FCPB and FCDB
Chapter 5
Oracle FCDB – FCPB Interface deals with the maintenances required in FCDB to
exchange information between FCDB and FCPB
Acronyms and Abbreviations
Abbreviation
Description
System
Unless and otherwise specified, it shall always refer to Oracle FLEXCUBE
Universal Banking Solutions system
FCUBS
Oracle FLEXCUBE Universal Banking Services
FCDB
Oracle FLEXCUBE Direct Banking
FCPB
Oracle FLEXCUBE Private Banking
EOD
End of Day
Licensee
The LICENSEE is the Financial Institution, Application Services Provider or the
Bank which has licensed the Oracle FLEXCUBE Direct Banking application and
shall rollout the solution to its customers as an internet and / or mobile banking
channel
Implementer
The IMPLEMENTER is the Implementation Partner, Vendor, Application
Service Provider or the LICENSEE themselves who is responsible for rolling
out, configuring, extending or developing on Oracle FLEXCUBE Direct Banking
DB PB
Oracle FLEXCUBE Direct Banking – Oracle FLEXCUBE Private Banking
SSO
Single Sign On
Terminology
The following terms and terminology is used within the documents to explain underlying
processes, components, actions, actors etc.
Term
Definition
Business
Service
A Business Service or a Transaction Service is a coarse grained component that delivers a
particular service contract. The Service Interfaces and that make up the contract are each
1-2
implemented by their particular Service Endpoints.
POJO
A Plain Old Java Object (POJO) is exactly what it says. The term is used to differentiate
these simple objects from more specific or complex types such as EJB classes.
For example, when creating an EJB, a specific class must implement the Session Bean
interface. However, that class will often delegate much of its functionality to one or more
POJOs to aid maintainability and reuse of functionality.
Service
Implement
ation or
Service
Endpoint
A Service Implementation is a concrete implementation of a Service Interface.
Service
Interface
A Service Interface is a cohesive set of Service Methods that are grouped together in the
anticipation that they will be commonly used together by a consumer.
For example, the Service Interface for the Funds Transfer Service would contain a set of
Service Methods that perform different types of immediate money transfer between two
accounts.
1.6
Service
Method
A Service Method takes the form of a Java method implemented by the Service
Implementation and the Service Delegate. The consumer of the service will invoke one or
more Service Methods to help perform part of a business process.
Extension
Schema
The Extension Schema is a term used for the separate database schema as deployed by
Oracle FLEXCUBE Direct Banking to allow IMPLEMENTERS to extend the Oracle
FLEXCUBE Direct Banking application as per their needs.
Glossary of Icons
This user manual may refer to all or some of the following icons.
Icons
Function
Exit
Help
Add
Delete
View
1.6.1 Conventions Used in this Manual
Important information is preceded with the
symbol.
1-3
2.
2.1
Oracle FCUBS – FCPB Interface
Introduction
Oracle FLEXCUBE Private Banking (FCPB) helps banks, financial institutions and wealth
management service providers deliver advisory-driven solutions. The services include portfolio
management, management of multiple asset-classes and advisory services.
The interface between FCUBS and FCPB enables the exchange of information related to day-today transactions and maintenances. FCUBS generates the required data for exchange in ASCII
format and places the files in a pre-defined directory in the database server. This directory is
accessible by FCPB.
The data types permitted in a handoff file are given below:
Data Type
Description
Text
Text fields can have alphanumeric characters as per the length specified for the
field.
Numeric
Numeric fields contain the following information:
Amounts – This type of fields contain digits (0-9) and a decimal separator (.).
The number of decimal digits is driven by the currency maintenance of FCUBS.
Numbers without decimals – This type of fields contain digits (0-9) only.
Numbers with decimals – This type of fields contain digits (0-9) and a decimal
separator (.). However, these digits do not represent amounts. For example,
exchange rates of currencies may contain decimal.
Date
Dates are represented in YYYYMMDD format. For instance, March 30, 2012 is
represented as 20120330.
2.1.1 Details Handed off from FCUBS to Oracle FCPB
Oracle FLEXCUBE hands off the following details to Oracle FCPB:
Entity
Action
Frequency
Core/Security
TD Account Creation
Add
On-line
Core
TD Premature Withdrawal
Add
On-line
Core
CASA Account Creation
Add
On-line
Core
CIF Authorization/Modification/Closure
Add
On-line
Core
Broker Data
Add
On-line
Core
2-1
2.2
Entity
Action
Frequency
Core/Security
CASA Account Balances
Add
On-line
Core
Segmentation Information
Add
On-line
Core
TD Maturity with Interest Liquidation
Add
Batch
Core
Daily Accrued Interest on TD
Add
Batch
Core
Penalty on TD
Add
Batch
Core
Loan and Liability Information
Add
Batch
Core
Segmentation Status Information
Add
Batch
Core
Defining Interface Details for Oracle FCPB
In order to enable the interface, you need to define the interface details for Oracle FCPB in
FCUBS. You can define the format details and properties of interface files using ‘Interface
Definition’ screen. To invoke this screen, type ‘GIDIFTDF’ in the field at the top right corner of the
Application toolbar and click the adjoining arrow button.
2-2
You need to define the interface details.
External System
Specify the code that identifies the external system. The interface details defined on this screen
are applicable to the interface between FCUBS and the external system selected here.
For FCPB interface, you need to specify ‘FCPB’ as the external system.
Interface Code
Specify a unique code that identifies the interface between the above external system and
FCUBS.
Interface Type
Select the interface type from the following options:

Incoming - Select this for interfaces that upload data into FCUBS

Outgoing - Select this for interfaces that facilitate handoff of data from FCUBS
2-3
File Mask
Specify the file mask for the outgoing interface file. The system decides the name of the handoff
file based on the file mask defined here.
Format Type
Select the message format type. Choose one of the following format types based on the data
length:

Fixed - Select this format type if the interface data is within fixed width.

Delimited - Select this format type if the interface data is in delimited format.
If you select ‘Delimited’, the system enables the field ‘Delimiting Character’.
File Path
Specify the directory in which the interface file is stored.
For further details on the fields on ‘Interface Definition’ screen, refer to the section ‘Specifying
Interface Definition Details’ under chapter ‘Generic Interface’ of Generic Interface user manual.
2.2.1 Defining Component Details
As part of interface definition, you need to capture specific component details for both handoff
and upload. Click ‘Component Details’ button on the ‘Interface Definition’ screen.
2-4
You can capture the details of the header, body and footer under ‘Component Linkage’ section.
Below that, under ‘Component Field Linkage’ section, you can define the details pertaining to
table columns, field type, field length, field name and other relevant details.
For more details of the fields on this screen, refer the chapter ‘Generic Interface’ in the Generic
Interface User Manual.
2.3
FATCA Interface between Oracle FCUBS and FCPB
As part of the GIDPRSIF batch, Oracle FCUBS hands off FATCA (Foreign Account Tax
Compliance Act) related data to FCPB. This batch is part of the end of day operations. Once a
customer gets upgraded as per the segmentation rules, FCUBS generates a handoff file to
FCPB. Subsequently, the customers will areceive an online notification.
The system generates the following handoff files during EOD operations:
The Customer Master File
This file contains the following information related to FATCA.

Information available in the FATCA related fields

Any field information related to ‘Director’ in the existing customer master file will be
removed as part of the batch. Such details will form a part of the ‘Directors’ hand-off file.
The interface code for Customer Master File (UBS_SEG_CUSTOMER.CSV) is IFCUSSEG
Directors File
Any field information related to ‘Director’ will form a part of the ‘Directors’ hand-off file. This file
supports one-to-many relationships between customer and directors.
The interface code for Directors (UBS_SEG_AUTH_SIGN.CSV) is IFCUSCOR
Customer FATCA Classification File
This file contains FATCA classification details of the customers.
The interface code for Customer FATCA Classification file (UBS_SEG_CUST_FATCA.CSV) is
IFFATCA
2.4
Processing Online Notifications
FCUBS sends an online notification to Oracle FCDB at the following occasions:

Creation of term deposit account in FCUBS

Premature withdrawal (redemption before maturity date) of the term deposit amount

Creation of customer accounts in FCUBS

Change in the balance in the customer accounts

Creation, modification or closure of customer information

Creation of Brokers (customer under the customer category ‘Broker’) in FCUBS

Modification of term deposit account in FCUBS
2-5

Premature withdrawal (redemption before maturity date) of the term deposit amount
Online Notification for TD redemption through 1317 redemption screen is not
supported.

Rollover of Term deposit account in FCUBS

Creation of Recurring deposit account in FCUBS

Customer creation under ‘BROKER’ category

Amendment of the segmentation code, net worth amount, net worth currency and
customer currency of customer Segmentation

Amendment of the segmentation status from Upgraded to Downgraded and ReUpgraded to Downgraded
Notification will be fired only for segmented customer. That is when the segment status and
segment code for the customer are not null.
Customer status cannot be modified to downgrade on the same day of upgrade.
The details of online notification processed from FCUBS are given below:
Instance
Notification
Code
Operation
Service
XSD Name
TD account
creation
NOTIF_TD_TDA
CC_NEW
QuerycustAccount
Details
FCUBSAccServi
ce
TD-NewAccountNotify-MSG.xsd
TD Account
modification
NOTIF_TDMOD
_PB
QuerycustAccount
Details
FCUBSAccServi
ce
TD-NewAccountNotify-MSG.xsd
TD
premature
withdrawal
NOTIF_ICRED
M
QueryTDRedempti
on
FCUBSAccServi
ce
ICQueryTDRedemRes-FullMSG.xsd
ICQueryTDRedemReq-IO-MSG.xsd
TD rollover
NOTIF_TD_RO
LLOVER
QueryTDRollover
FCUBSTDServi
ce
STQueryTDRollover
-Req-IOMSG.xsd
STQueryTDRollover
-Res-FullMSG.xsd
CASA
account
creation
NOTIF_CA_CU
STACC_NEW
QuerycustAccount
Details
2-6
FCUBSAccServi
ce
CANewCustomerAc
count-NotifyMSG.xsd
Instance
Notification
Code
Operation
Service
XSD Name
CIF
authorizatio
n/
modification
/ Closure
NOTIF_CO_CU
STOMER_MOD
QueryCustomer
FCUBSCustome
rService
STModifyCustomerNotify-MSG.xsd
Broker
creation
NOTIF_CO_CU
STOMER_NEW
QueryCustomer
FCUBSCustome
rService
STNewCustomerNotify-MSG.xsd
CASA
account
balance
change
NOTIFY_AC_B
AL
QuerycustAccount
Details
FCUBSAccServi
ce
TD-AccStatNotif.xsd
Customer
creation
NOTIF_PB_CU
STOMER
Customer creation
under ‘Broker’
category
Segmentati
on code
NOTIF_PB_CU
STOMER
CUSTSEGCD
Net worth
Amount
NOTIF_PB_CU
STOMER
NETWORTH
Net worth
Currency
NOTIF_PB_CU
STOMER
NETWORTHCCY
customer
currency
NOTIF_PB_CU
STOMER
CUSTCCY
Segmentati
on status
NOTIF_PB_CU
STOMER
CUSTSEGSTAT
US
New tags CUSTSEGCD, CUSTSEGSTATUS, NETWORTH, NETWORTHCCY and CUSTCCY
will be available in the notification XSD.
2.5
Defining Interface Details for Data Handoff
FCUBS hands off the details of maintenances and transactions to Oracle FCPB for processing.
You need to maintain separate interface details to enable handoff of the following details:

TD maturity with interest liquidation

Daily accrued interest on TD

Penalty on TD

Loan and Liability Information
2-7
The maintenances required for enabling the data upload are discussed under the following
headings.
2.5.1 Term Deposit Maturity with Interest Liquidation
On the maturity date of a term deposit, FCUBS hands off the term deposit maturity details to
Oracle FCPB. In addition to that, the system also hands off the interest details after interest
liquidation.
This handoff happens only for the customers whose segment code and segment status are
defined in the system.
To enable the data handoff from FCUBS, you need to define the interface details as given in the
following table:
Field
Value
Interface Code
STOIMDTL
Interface Type
Outgoing
From System
FCUBS
To System
FCPB
Dateformat
YYYYMMDD
File Mask
/U/B/S/_/T/D/M/A/T$D$M$Y$h$m$s/E/N/D/./C/S/V
Whentorun
Beginning of day
Frequency
Daily
Character Set
ASCII
Format
Delimited
Delimiter
^
File Header record length
3 , Default value HDR
Body Record Length
36
File Footer record length
3, default value TLR
Numeric padding
Left padding with Zeros
Text padding
Left padding with spaces
Datalog Required
Yes
CRC Required
No
2-8
Field
Value
Triggering
System
In ‘Component Details’ sub-screen, you need to maintain the following details:
Field
Name
Table Name
Column
Name
HEADER
Data Type
Field
Length
Position
VARCHAR2
3
1
AC_REF_
NO
TDVWS_TD_MAT
URITY_DETAILS
AC_ENTRY
_SR_NO
NUMBER
10
1
CUST_NO
TDVWS_TD_MAT
URITY_DETAILS
CUSTOMER
_NO
VARCHAR2
9
11
CUST_NA
ME
TDVWS_TD_MAT
URITY_DETAILS
CUSTOMER
_NAME1
VARCHAR2
105
20
TD_ACC
TDVWS_TD_MAT
URITY_DETAILS
ACC
VARCHAR2
20
125
ACC_CLA
SS
TDVWS_TD_MAT
URITY_DETAILS
ACCOUNT_
CLASS
VARCHAR2
6
145
TRN_DT
TDVWS_TD_MAT
URITY_DETAILS
TRN_DT
DATE
10
151
LCY_AMO
UNT
TDVWS_TD_MAT
URITY_DETAILS
AMOUNT
NUMBER
22
161
DR_CR_A
CC
TDVWS_TD_MAT
URITY_DETAILS
AC_NO
VARCHAR2
20
183
AC_CCY
TDVWS_TD_MAT
URITY_DETAILS
AC_CCY
VARCHAR2
3
203
REC_STA
T
TDVWS_TD_MAT
URITY_DETAILS
RECORD_S
TAT
VARCHAR2
1
206
TXN_TYP
E
TDVWS_TD_MAT
URITY_DETAILS
TRANSACTI
ON_TYPE
VARCHAR2
9
207
VARCHAR2
3
1
TRAILER
2.5.2 Daily Accrued Interest on Term Deposits
FCUBS hands off the details of the accrued interest on the term deposits to Oracle FCPB on a
daily basis. This handoff happens only for the customers whose segment code and segment
status are defined in the system.
2-9
Discounted TD’s accrual record will not be sent to Oracle FCPB. Interest Liquidation for
Discounted TD’s will be sent upfront in TD Maturity with interest liquidation file.
To enable handoff of this data from FCUBS, you need to define the interface details as given in
the following table:
Field
Value
Interface Code
DLACCRNT
Interface Type
Outgoing
From System
FCUBS
To System
FCPB
Dateformat
YYYYMMDD
File Mask
/M/K$D$M$Y$h$m$s/E/N/D
Whentorun
End of Transaction input
Frequency
Daily
Character Set
ASCII
Format
Delimited
Delimiter
^
File Header record length
3 , Default value HDR
Body Record Length
36
File Footer record length
3, default value TLR
Numeric padding
Left padding with Zeros
Text padding
Left padding with spaces
Datalog Required
Yes
CRC Required
No
Triggering
System
In ‘Component Details’ sub-screen, you need to maintain the following details:
Field
Name
Table Name
Column Name
2-10
Data Type
Field
Length
Position
Field
Name
Table Name
Column Name
Data Type
Field
Length
Position
CUSTNO
ICVW_ACCRUAL_
DETAILS
CUST_NO
VARCHAR2
9
1
SHRTNM
ICVW_ACCRUAL_
DETAILS
SHORT_NAME
VARCHAR2
20
10
ACC
ICVW_ACCRUAL_
DETAILS
ACC
VARCHAR2
20
30
ACCL
ICVW_ACCRUAL_
DETAILS
ACCOUNT_CLA
SS
VARCHAR2
6
50
ACRAMT
ICVW_ACCRUAL_
DETAILS
ACCRUED_AMT
NUMBER
22
56
ENTDT
ICVW_ACCRUAL_
DETAILS
ENT_DT
VARCHAR2
10
78
CCY
ICVW_ACCRUAL_
DETAILS
CCY
VARCHAR2
3
88
PROD
ICVW_ACCRUAL_
DETAILS
PROD
VARCHAR2
4
91
HEADER
VARCHAR2
3
1
TRAILER
VARCHAR2
3
1
2.5.3 Penalty on Term Deposits
FCUBS hands off to Oracle FCPB the details of penalties applied on term deposits. This handoff
happens only for the customers whose segment code and segment status are defined in the
system.
To enable handoff of this data from FCUBS, you need to define the interface details as given in
the following table:
Field
Value
Interface Code
STOIMDTL
Interface Type
Outgoing
From System
FCUBS
To System
FCPB
Dateformat
YYYYMMDD
2-11
Field
Value
File Mask
/U/B/S/_/T/D/M/A/T$D$M$Y$h$m$s/E/N/D/./C/S/V
Whentorun
Beginning of day
Frequency
Daily
Character Set
ASCII
Format
Delimited
Delimiter
^
File Header record length
3 , Default value HDR
Body Record Length
36
File Footer record length
3, default value TLR
Numeric padding
Left padding with Zeros
Text padding
Left padding with spaces
Datalog Required
Yes
CRC Required
No
Triggering
System
In ‘Component Details’ sub-screen, you need to maintain the following details:
Field Name
Table
Name
Column Name
HEADER
Data Type
Field
Length
Position
VARCHAR2
3
1
AC_REF_N
O
TDVW_TD
_DETAILS
AC_ENTRY_SR_NO
NUMBER
10
1
CUST_NO
TDVW_TD
_DETAILS
CUSTOMER_NO
VARCHAR2
9
11
CUST_NAM
E
TDVW_TD
_DETAILS
CUSTOMER_NAME
1
VARCHAR2
105
20
TD_ACC
TDVW_TD
_DETAILS
ACC
VARCHAR2
20
125
ACC_CLAS
S
TDVW_TD
_DETAILS
ACCOUNT_CLASS
VARCHAR2
6
145
2-12
Field Name
Table
Name
Column Name
Data Type
Field
Length
Position
TRN_DT
TDVW_TD
_DETAILS
TRN_DT
DATE
10
151
LCY_AMOU
NT
TDVW_TD
_DETAILS
AMOUNT
NUMBER
22
161
DR_CR_AC
C
TDVW_TD
_DETAILS
AC_NO
VARCHAR2
20
183
AC_CCY
TDVW_TD
_DETAILS
AC_CCY
VARCHAR2
3
203
REC_STAT
TDVW_TD
_DETAILS
RECORD_STAT
VARCHAR2
1
206
TXN_TYPE
TDVW_TD
_DETAILS
TRANSACTION_TY
PE
VARCHAR2
9
207
VARCHAR2
3
1
TRAILER
2.5.4 Loan and Liability Information
FCUBS hands off the details of loan accounts to Oracle FCPB. This handoff happens only for the
customers whose segment code and segment status are defined in the system.
The handoff file contains the following details of the loan accounts maintained in FCUBS:

Principal outstanding amount

Maturity date

Interest rate

Tenor of the loan

Accrued amount

Amount paid

Last paid date
To enable handoff of this data from FCUBS, you need to define the interface details as given in
the following table:
Field
Value
Interface Code
CLOLNDTL
Interface Type
Outgoing
From System
FCUBS
2-13
Field
Value
To System
FCPB
Dateformat
YYYYMMDD
File Mask
/U/B/S/_/P/R/O/D/B/L$D$M$Y$h$m$s/E/N/D
Whentorun
End of Transaction input
Frequency
Daily
Character Set
ASCII
Format
Delimited
Delimiter
^
File Header record length
3 , Default value HDR
Body Record Length
36
File Footer record length
3, default value TLR
Numeric padding
Left padding with Zeros
Text padding
Left padding with spaces
Datalog Required
Yes
CRC Required
No
Triggering
System
In ‘Component Details’ sub-screen, you need to maintain the following details:
Field
Name
Table Name
Column Name
HEADER
Data Type
Field
Length
Position
VARCHAR2
3
1
CUSTID
CLVW_LOAN_
INT_DETAILS
CUSTOMER_ID
VARCHAR2
35
1
ACCNO
CLVW_LOAN_
INT_DETAILS
ACCOUNT_NUM
BER
VARCHAR2
35
2
PRODAC
CLVW_LOAN_
INT_DETAILS
DR_PROD_AC
VARCHAR2
20
36
PROD
CLVW_LOAN_
PRODUCT_COD
VARCHAR2
4
56
2-14
Field
Name
Table Name
Column Name
Data Type
Field
Length
Position
INT_DETAILS
E
BOOKDT
CLVW_LOAN_
INT_DETAILS
BOOK_DATE
VARCHAR2
10
60
VALDT
CLVW_LOAN_
INT_DETAILS
VALUE_DATE
VARCHAR2
10
70
PRNOUT
AMT
CLVW_LOAN_
INT_DETAILS
PRNOUTSTANDI
NG
NUMBER
22
80
CCY
CLVW_LOAN_
INT_DETAILS
CURRENCY
VARCHAR2
3
102
MATDT
CLVW_LOAN_
INT_DETAILS
MATURITY_DAT
E
VARCHAR2
10
105
ACCSTAT
CLVW_LOAN_
INT_DETAILS
ACCOUNT_STAT
US
VARCHAR2
1
115
ACSUBTY
P
CLVW_LOAN_
INT_DETAILS
ACCT_SUB_TYP
E
VARCHAR2
10
116
ACCBRN
CLVW_LOAN_
INT_DETAILS
DR_ACC_BRN
VARCHAR2
3
126
MICR
CLVW_LOAN_
INT_DETAILS
MICR
VARCHAR2
10
129
RSLDVAL
CLVW_LOAN_
INT_DETAILS
RESOLVED_VAL
UE
NUMBER
22
139
TENOR
CLVW_LOAN_
INT_DETAILS
TENOR
NUMBER
22
161
ACCRAM
T
CLVW_LOAN_
INT_DETAILS
ACCRAMT
NUMBER
22
183
LTINACD
T
CLVW_LOAN_
INT_DETAILS
LAST_INT_ACCR
_DATE
VARCHAR2
10
205
AMTSTLD
CLVW_LOAN_
INT_DETAILS
AMTSTLD
NUMBER
22
215
LTPMTDT
CLVW_LOAN_
INT_DETAILS
LAST_PMT_DT
VARCHAR2
10
237
ACTADD
CLVW_LOAN_
INT_DETAILS
ACCT_ADDRESS
VARCHAR2
10
247
2-15
Field
Name
Table Name
Column Name
Data Type
Field
Length
Position
HLDAMT
CLVW_LOAN_
INT_DETAILS
HOLD_AMOUNT
NUMBER
22
257
VARCHAR2
3
1
TRAILER
2.5.5 Term Deposit Rollover
FCUBS hands off the details of manual and automatic rollovers of term deposits to Oracle FCPB.
This handoff happens only for the customers whose segment code and segment status are
defined in the system.
The Notification contains the following details of the TD accounts maintained in FCUBS:

Branch

Deposit account number

Old maturity date

New maturity date

Renewal date

Rollover type

Total interest on the TD

Principal

Rollover amount

Balance interest paid out during rollover

Interest rate

Tenor

Customer number

Currency
2.5.6 Segmentation Status Information
When a customer segmentation status is updated to ‘Upgraded’ as per the segmentation rules,
FCUBS generates an End Of Day (EOD) and Beginning Of Day (BOD) files handoff for the
corresponding customers and triggers the handoffs to FCPB. As a part of this interface, the
following files will be generated whenever the customer segmentation status is upgraded:

Customer File
FCUBS will generate outgoing files for the upgraded customers and the account details
of the corresponding primary account holder will be handed off to FCPB.

Customer Account File
FCUBS will generate outgoing files for the CASA accounts of the upgraded customers
and the corresponding open accounts will be handed off to FCPB.

Customer Balances – CASA File
2-16
FCUBS will generate outgoing files for the CASA accounts and the balance of the
upgraded customers. The balance details of the corresponding open accounts will be
handed off to FCPB.

Customer Balances – Loan File
FCUBS will generate outgoing files for the Loan accounts and the balance of the
upgraded customers. The active loans of the corresponding customers will be handed off
to FCPB.

Customer TD Booked & Rollover File
FCUBS will generate outgoing files for the TD accounts which underwent the following
changes as of segmentation date:

Booked

Rollover

Partial Redemption
The following details are sent to the FCPB:

Details of all open TD accounts

Partial redeemed TD details

TD renewal details

Customer TD Interest Liquidation, Penalty File - Segment Upgrade Details
FCUBS will generate outgoing files at BOD, for the TD accounts undergoing the following
changes as of segmentation date:

Interest liquidation

Penalty
The following TD details are sent to FCPB:

TD with interest liquidation

TD with penalty entries for partial redemption
2.5.6.1 Segment Upgrade - File Formats
The formats of the above files are given below.
Customer File Format
The format of the customer file is given below.
FIELD
NAME
DESCRIPTION
MANDAT
ORY
FCUBS
COLUMN
NAME
TABLE NAME
LE
NG
TH
EXTERNAL
_ID
External client
id of customer
YES
EXT_REF_
NO
STTM_CUSTOME
R
20
SALUTATIO
N
Salutation
YES
CUSTOME
R_PREFIX
STTM_CUST_PE
RSONAL
30
FIRST_NAM
E
First Name
YES
FIRST_NA
ME
STTM_CUST_PE
RSONAL
105
MIDDLE_NA
ME
Middle Name
NO
MIDDLE_N
AME
STTM_CUST_PE
RSONAL
105
2-17
FIELD
NAME
DESCRIPTION
MANDAT
ORY
FCUBS
COLUMN
NAME
TABLE NAME
LE
NG
TH
LAST_NAM
E
Last Name
NO
LAST_NAM
E
STTM_CUST_PE
RSONAL
105
PHONE_HO
ME
Home Phone
NO
TELEPHON
E
STTM_CUST_PE
RSONAL
105
PHONE_MO
BILE
Mobile Phone
NO
MOBILE_N
UMBER
STTM_CUST_PE
RSONAL
22
PHONE_W
ORK
Work Phone
NO
E_TELEPH
ONE
STTM_CUST_PR
OFESSIONAL
10
EMAIL
Email
NO
E_MAIL
STTM_CUST_PE
RSONAL
255
GENDER
Gender:(M)
Male, (F)
Female
YES
SEX
STTM_CUST_PE
RSONAL
1
DOB
Date OF Birth
NO
DATE_OF_
BIRTH
STTM_CUST_PE
RSONAL
10
TAX_ID
Income Tax ID
YES
TAX_ID
STTM_CORP_DI
RECTORS
105
CLIENT_SE
G
Client Segment
YES
CUST_SEG
MENT_CO
DE
STTM_CUSTOME
R
OCCUPATI
ON
Occupation
YES
DESIGNATI
ON
STTMS_CUST_P
ROFESSIONAL
105
CLIENT_TY
PE
Client IT type
YES
CUSTOME
R_TYPE
STTM_CUSTOME
R
1
HOME_BRA
NCH
Branch code of
the customer
YES
LOCAL_BR
ANCH
STTM_CUSTOME
R
3
ACQ_DATE
Acquisition
Date
NO
BANKER
Banker Code
YES
ADDR_LINE
1
Mailing Address
1
NO
ADDR_LINE
Mailing Address
NO
NULL
BANK_COD
E
ADDRESS1
2-18
STTM_BANK
4
MSTM_CUST_AD
DRESS
105
MSTM_CUST_AD
105
FIELD
NAME
DESCRIPTION
MANDAT
ORY
FCUBS
COLUMN
NAME
TABLE NAME
ADDRESS2
DRESS
ADDRESS3
MSTM_CUST_AD
DRESS
LE
NG
TH
2
2
ADDR_LINE
3
Mailing Address
3
NO
STATE_MAI
LING
State of the
Mailing address
NO
COUNTRY_
MAILING
Country of the
mailing address
NO
ZIP_MAILIN
G
Zip code of the
mailing address
NO
ADDR_LINE
1
Home Address
1
YES
ADDRESS_
LINE1
STTM_CUSTOME
R
105
ADDR_LINE
2
Home Address
2
YES
ADDRESS_
LINE3
STTM_CUSTOME
R
105
ADDR_LINE
3
Home Address
3
YES
ADDRESS_
LINE2
STTM_CUSTOME
R
105
STATE_MAI
LING
State of the
Home address
NO
COUNTRY_
MAILING
Country of the
Home address
YES
ZIP_MAILIN
G
Zip code of the
Home address
NO
ADDR_LINE
1
Work Address 1
NO
E_ADDRES
S1
STTMS_CUST_P
ROFESSIONAL
105
ADDR_LINE
2
Work Address 2
NO
E_ADDRES
S2
STTMS_CUST_P
ROFESSIONAL
105
ADDR_LINE
3
Work Address 3
NO
E_ADDRES
S3
STTMS_CUST_P
ROFESSIONAL
105
STATE_MAI
LING
State of the
work address
NO
NULL
COUNTRY_
MAILING
Country of the
work address
NO
NULL
ZIP_MAILIN
Zip code of the
NO
NULL
105
NULL
COUNTRY
MSTM_CUST_AD
DRESS
3
NULL
NULL
COUNTRY
STTM_CUSTOME
R
3
NULL
2-19
FIELD
NAME
DESCRIPTION
MANDAT
ORY
FCUBS
COLUMN
NAME
TABLE NAME
LE
NG
TH
G
work address
FAX
Fax Number
NO
FAX_NUMB
ER
STTM_CUSTOME
R
105
NATIONALI
TY
Nationality
YES
NATIONALI
TY
STTM_CUSTOME
R
3
LANGUAGE
Preferred
language of the
customer
YES
LANGUAGE
STTM_CUSTOME
R
3
CCY_ID
Customer
Currency
YES
PORTFOLI
O_CCY_CO
DE
SETM_PORTFOLI
O_MASTER
3
PREF_COM
M_MODE
Preferable
communication
mode
YES
DEFAULT_
MEDIA
STTM_CUSTOME
R
12
CLIENT_CA
TEGORY
Client category
YES
CUSTOME
R_CATEGO
RY
STTM_CUSTOME
R
10
CLIENT_CL
ASSIFICATI
ON
Client
Classification
YES
CUST_CLA
SSIFICATIO
N
STTM_CUSTOME
R
20
MINOR_FLA
G
Flag indicating
if minor
YES
MINOR
STTM_CUST_PE
RSONAL
1
AUTH_SIGN
_FNAME
First name of
the authorized
signatory
NO
LEGAL_GU
ARDIAN
STTM_CUST_PE
RSONAL
105
AUTH_SIGN
_LNAME
Last name of
the authorized
signatory
NO
NULL
AUTH_SIGN
_DOB
Date of birth of
the authorized
signatory
NO
NULL
AUTH_SIGN
_MOBILE
Mobile number
of the
authorized
signatory
NO
NULL
AUTH_SIGN
Home number
NO
NULL
2-20
FIELD
NAME
DESCRIPTION
MANDAT
ORY
FCUBS
COLUMN
NAME
_HOME
of the
authorized
signatory
AUTH_SIGN
_TAX_ID
Tax identified of
the authorized
signatory
NO
NULL
AUTH_SIGN
_REL
Relationship of
the authorized
signatory
NO
NULL
AUTH_SIGN
_TYPE
Type of the
authorized
signatory
NO
NULL
EXT_PORT
FOLIO_ID
UBS
Investment
portfolio ID
NO
PORTFOLI
O_ID
SETM_PORTFOLI
O_MASTER
16
REG_COUN
TRY_ID
Registered
country for the
corporate
NO
R_COUNTR
Y
STTMS_CUST_C
ORPORATE
3
INCORP_C
OUNTRY_ID
Incorporated
country for the
corporate
NO
INCORP_C
OUNTRY
STTMS_CUST_C
ORPORATE
3
CUSTOMER
_STATUS
Status of the
customer
NO
CIF_STATU
S
STTM_CUSTOME
R
20
UDF_NUM_
1
UDF NUM 1
NO
FIELD_VAL
_1
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_NUM_
2
UDF NUM 2
NO
FIELD_VAL
_2
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_NUM_
3
UDF NUM 3
NO
FIELD_VAL
_3
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_NUM_
4
UDF NUM 4
NO
FIELD_VAL
_4
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
2-21
TABLE NAME
LE
NG
TH
FIELD
NAME
DESCRIPTION
MANDAT
ORY
FCUBS
COLUMN
NAME
TABLE NAME
LE
NG
TH
UDF_NUM_
5
UDF NUM 5
NO
FIELD_VAL
_5
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_TXT_1
UDF TXT 1
NO
FIELD_VAL
_6
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_TXT_2
UDF TXT 2
NO
FIELD_VAL
_7
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_TXT_3
UDF TXT 3
NO
FIELD_VAL
_8
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_TXT_4
UDF TXT 4
NO
FIELD_VAL
_9
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_TXT_5
UDF TXT 5
NO
FIELD_VAL
_10
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_DATE
_1
NO
FIELD_VAL
_11
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_DATE
_2
NO
FIELD_VAL
_12
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_DATE
_3
NO
FIELD_VAL
_13
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_DATE
_4
NO
FIELD_VAL
_14
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
UDF_DATE
_5
NO
FIELD_VAL
_15
CSTM_FUNCTIO
N_USERDEF_FIE
LDS
150
2-22
Customer Account File Format
The format of the customer account file is given below:
FIELD
NAME
DESCRI
PTION
LEN
GTH
MAN
DATO
RY
FCC_COL
UMNS
LE
NG
TH
TABLE
NAME
T_EXT_CL
IENT_ID
External
client id
10
YES
CUST_NO
9
STTM_CU
ST_ACCO
UNT
T_BANK_A
CCT_ID
Bank
account
id
16
YES
CUST_AC
_NO
20
STTM_CU
ST_ACCO
UNT
T_ACCT_S
TATUS
Account
status
1
YES
ACC_STA
TUS
4
STTM_CU
ST_ACCO
UNT
T_ACCT_S
UB_TYPE
Account
sub type
5
YES
ACCOUNT
CALSS
6
STTM_CU
ST_ACCO
UNT
T_CURR
Currency
3
YES
CCY
3
STTM_CU
ST_ACCO
UNT
T_ACCT_B
RANCH
Account
branch
50
YES
BRANCH_
CODE
3
STTM_CU
ST_ACCO
UNT
T_MICR
MICR
24
NO
NULL
T_ACCT_T
YP
Account
type
5
YES
ACCOUNT
_TYPE
1
STTM_CU
ST_ACCO
UNT
T_SALES_
REP_ID
Sale
represent
ative id
50
NO
NULL
T_OPPOR
TUNITY_I
D
Sale
oppurtinit
y id
50
NO
NULL
OPENING
_DATE
Opening
date
YES
AC_OPEN
_DATE
8
STTM_CU
ST_ACCO
UNT
CLOSING_
DATE
Closing
date
NO
AC_SET_
CLOSE_D
8
STTM_CU
ST_ACCO
2-23
Fcubs
Remarks
SSavings,
UCurrent
FIELD
NAME
DESCRI
PTION
LEN
GTH
MAN
DATO
RY
FCC_COL
UMNS
LE
NG
TH
ATE
TABLE
NAME
Fcubs
Remarks
UNT
T_ACCT_A
DDRESS
Address
200
YES
ADDRESS
1
105
STTM_CU
ST_ACCO
UNT
T_ACCT_A
DDRESS1
Address
line 1
200
NO
ADDRESS
2
105
STTM_CU
ST_ACCO
UNT
T_ACCT_A
DDRESS2
Address
line 1
200
NO
ADDRESS
3
105
STTM_CU
ST_ACCO
UNT
T_ACCT_
CITY
Account
city
100
NO
LOCATIO
N
15
STTM_CU
ST_ACCO
UNT
T_ACCT_
COUNTRY
_ID
Account
country
id
3
NO
NULL
T_HLD_AC
CT_YN
Held
away
accoutn
YN
1
YES
"N"
T_ACCT_
DESCRIPT
ION
Accound
descripti
on
20
NO
AC_DESC
1
DEFAULT
VALUE
"N"
STTM_CU
ST_ACCO
UNT
Customer Balance – CASA File Format
The format of the customer balance file is given below:
FIELD
NAME
DESCRIPT
ION
TYPE
LE
NG
TH
MAND
ATORY
FCC_CO
LUMN
LE
NG
TH
FCC
Table
name
CLIENT_
ID
Client id
VARC
HAR
10
YES
CUST_N
O
9
STTM_C
UST_AC
COUNT
BANK_A
CCT_ID
Bank
account id
/loan
account id
VARC
HAR
16
YES
CUST_A
C_NO
20
STTM_C
UST_AC
COUNT
2-24
FCC
Remarks
FIELD
NAME
DESCRIPT
ION
TYPE
LE
NG
TH
MAND
ATORY
FCC_CO
LUMN
LE
NG
TH
FCC
Table
name
FCC
Remarks
PROD_I
D
product id
VARC
HAR
5
YES
PROD
4
ICTB_E
NTRIES
Interest
Product
associated
.One
account
can have
multiple
interest
product
BOOKIN
G_DATE
booking
date
DATE
YES
AC_OPE
N_DATE
VALUE_
DATE
value date
DATE
YES
AMOUN
T
amount
NUMB
ER
24,
6
YES
ACY_AVL
_BAL
22
STTM_C
UST_AC
COUNT
CCY_ID
Currency
VARC
HAR
3
YES
CCY
3
STTM_C
UST_AC
COUNT
MATURI
TY_DAT
E
Maturity
date
DATE
NO
NULL
ACCT_S
UB_TYP
E
Account
sub type
VARC
HAR
5
YES
ACCOUN
T_CLASS
6
STTM_C
UST_AC
COUNT
INT_RA
TE
interest
rate
NUMB
ER
24,
6
NO
AMT/RAT
E
22
ICTB_U
DEVALS
TENOR
tenor
NUMB
ER
10
YES
NULL
ACCR_I
NT
Accrued
interest
NUMB
ER
24,
6
NO
AMT
22
ICTB_E
NTRIES
2-25
STTM_C
UST_AC
COUNT
8
Default
Value
Application
date
This will
be sum of
total credit
interest
accrued
for that
product
includes
FIELD
NAME
DESCRIPT
ION
TYPE
LE
NG
TH
MAND
ATORY
FCC_CO
LUMN
LE
NG
TH
FCC
Table
name
FCC
Remarks
all credit
formula
associated
to it
LAST_IN
T_ACCR
_DATE
Last
interest
paid
DATE
INTERE
ST_PAI
D
interest
paid
NUMB
ER
LAST_IN
T_DATE
Last
interest
date
DATE
HOLD_A
MOUNT
Hold
amount
NUMB
ER
24,
6
24,
6
NO
LAST_AC
CR_DT
8
ICTB_A
CC_PR
NO
AMT
22
ICTB_E
NTRIES
NO
LAST_AC
CR_DT
8
ICTB_A
CC_PR
NO
ACY_BL
OCKED_
AMOUNT
22
STTM_C
UST_AC
COUNT
This will
be sum of
total credit
interest
liquidated
for the
product
includes
all credit
formula
associated
to it
Customer Balance – Loan File Format
The format of the customer loan balance file is given below:
FIELD
NAME
DESCRI
PTION
TYP
E
LEN
GTH
MAN
DAT
ORY
FCC_
COLU
MN
LEN
GT
H
FCC Table
name
CLIENT
_ID
Client id
VAR
CHA
R
10
YES
CUST
OMER
_ID
9
CLTB_ACCO
UNT_MASTE
R
BANK_A
CCT_ID
Bank
account
id /loan
account
id
VAR
CHA
R
16
YES
CUST
_AC_
NO
20
STTM_CUST
_ACCOUNT
2-26
FCC
Remarks
FIELD
NAME
DESCRI
PTION
TYP
E
LEN
GTH
MAN
DAT
ORY
FCC_
COLU
MN
LEN
GT
H
FCC Table
name
PROD_I
D
product
id
VAR
CHA
R
5
YES
PROD
UCT_
CODE
4
CLTB_ACCO
UNT_MASTE
R
BOOKIN
G_DATE
booking
date
DAT
E
YES
BOOK
_DAT
E
8
CLTB_ACCO
UNT_MASTE
R
YYYYMMD
D format
VALUE_
DATE
value
date
DAT
E
YES
VALU
E_DA
TE
8
CLTB_ACCO
UNT_MASTE
R
YYYYMMD
D format
AMOUN
T
amount
NUM
BER
24,6
YES
AMOU
NT_FI
NANC
ED
CCY_ID
Currency
VAR
CHA
R
3
YES
CURR
ENCY
3
CLTB_ACCO
UNT_MASTE
R
MATURI
TY_DAT
E
Maturity
date
DAT
E
NO
MATU
RITY_
DATE
8
CLTB_ACCO
UNT_MASTE
R
ACCT_S
UB_TYP
E
Account
sub type
VAR
CHA
R
5
YES
"L"
1
INT_RA
TE
interest
rate
NUM
BER
24,6
NO
UDE_
VALU
E
CLTB_ACCO
UNT_UDE_V
ALUES
TENOR
tenor
NUM
BER
10
YES
NULL
CLTB_ACCO
UNT_MASTE
R
ACCR_I
NT
Accrued
interest
NUM
BER
24,6
NO
ACCR
UED_
AMOU
NT
CLTB_ACCO
UNT_SCHED
ULES
LAST_IN
T_ACCR
_DATE
Last
interest
paid
DAT
E
NO
EVEN
T_DA
TE
2-27
FCC
Remarks
CLTB_ACCO
UNT_MASTE
R
8
YYYYMMD
D format
Default
Value "L" Loan
CLTB_ACCO
UNT_EVENT
ST_DIARY
Last
accrual
event
happened
date
FIELD
NAME
DESCRI
PTION
TYP
E
LEN
GTH
MAN
DAT
ORY
FCC_
COLU
MN
LEN
GT
H
FCC Table
name
INTERE
ST_PAI
D
interest
paid
NUM
BER
24,6
NO
AMOU
NT_S
ETTLE
D
22
CLTB_ACCO
UNT_SCHED
ULES
LAST_IN
T_DATE
Last
interest
date
DAT
E
NO
EVEN
T_DA
TE
8
CLTB_ACCO
UNT_EVENT
ST_DIARY
Last
liquidation
event
happened
date
HOLD_A
MOUNT
Hold
amount
NUM
BER
NO
AMOU
NT_FI
NANC
ED
MINU
S
AMOU
NT_DI
SBUR
SED
22
CLTB_ACCO
UNT_MASTE
R
This will be
derived
from
AMOUNT_
FINANCED
AMOUNT_
DISBURSE
D
24,6
FCC
Remarks
Customer TD Booked File Format
The format of the customer TD booked file is given below:
FIELD
NAME
DESCRIP
TION
TYPE
LEN
GTH
MANDAT
ORY
CLIEN
T_ID
External
customer
ID
Varchar
10
Yes
TRAN
_TYPE
Tran type
Varchar
15
Yes
ACCO
UNT_
NO
Acount no
Varchar
16
Yes
TRAN
_DATE
Transacti
on date
Date
AMOU
NT
Amount
Number
REMARKS
SAMPLE VALUES
Could be NEW for
Booking, PAR for
Partial Uplift or
RNW for Rollover
Yes
24,6
Yes
2-28
Could be BookingAMt or PARAMt (For
PAR TranType) or RolloverAMt (for
RNW tranType)
FIELD
NAME
DESCRIP
TION
TYPE
LEN
GTH
MANDAT
ORY
CURR
ENCY
Currency
Varchar
3
Yes
MAT_
DATE
Maturity
date
Date
TENO
R
Tenor
Number
10
Yes
INT_R
ATE
Interest
rate
Number
23,6
NO
Has been made non-mandatory as
FCUBS request; but Should be
mandatory for Booking IntRate or
Rollover IntRate (for RNW tranType)
EXTE
RNAL_
TRAN
_ID
external
tran id
Varchar
40
No
Since FCUBS does not have any
separate TransactionId for TD and only
uses TD Ref Number, this should be
sent as NULL/BLANK
TRAN
_STAT
US
Tran
Status
Varchar
1
Yes
No need to send CLOSED TDs..only
Active TDs to be sent
SPRE
AD
Spread in
BPS
Number
24,6
Yes
Only for Floating we have Spread;
Fixed Deposit only has Customer Level
Spread -Bala to get back
ACCO
UNT_
CLAS
S
Product
alt id
Varchar
5
Yes
ROLL
OVER
_TYPE
Rollover
Type
Varchar
1
Yes
INTER
EST_A
MOUN
T
Interest
Amt for
Rollover
'P' type
Number
24,6
No
Yes
REMARKS
SAMPLE VALUES
Could be MatDt for Booking OR New
MatDt for Rollovers
Mandatory for
rollover
TransactionType
oNLY
Can be P or 'P+I'
as Rollover Type
This indicates the
Interest to be paid
to customer on the
RolloverDate for a
'P' type of Rollover
Customer TD Interest Liquidation, Penalty File Format
The format of the customer TD interest liquidation, penalty file is given below:
FIELD NAME
DESCRIPTION
MANDA
TORY
2-29
REMARKS
SAMPLE
VALUES
FIELD NAME
DESCRIPTION
MANDA
TORY
TRAN REF NO
Can be stored as
Ext_Tran_Idn or
Ext_Tran_Ref
Yes
CUSTOMER_N
O
Client_id
Yes
CUSTOMER_NA
ME1
ignored
NO
ACC
Sub_portfolio_id
Yes
ACCOUNT_CLA
SS
Based on Account
class(whether it is TD or
call deposit, instrument
id and instrument type
would be populated)details in
FCPB_FS_CASA_Includ
einholdings_Rel2.1section 8)
Yes
TRN_DT
Tran_Date
Yes
Interest
Liquidation
Date,
Penalty
Charging
Date
LCY_AMOUNT
Amount
Yes
Interest,
Penalty
AC_NO
Indicates Dr/Cr
AcctNumber n ignored
NO
AC_CCY
Amt_ccy
YES
RECORD_STAT
ignored
NO
TRANSACTION_
TYPE
Tran_Type
Yes
2-30
REMARKS
SAMPLE
VALUES
Interest,
Penalty
3.
3.1
Oracle FCPB – FCUBS Interface
Introduction
Oracle FCPB – FCUBS interface has been primarily designed to enable the exchange of
information between FCPB and FCUBS in terms of day-to-day transactions and maintenances for
certain entities like Customer Creation, CASA Account Creation, TD Accounts Creation/
Transactions and Balances related to Loans and Liabilities. This chapter deals with the following
interface and the explanation of the same from FCPB setup perspective:
3.2

Customer Creation – Explains handing-off of details related to Customer created in
FCUBS to FCPB.

CASA Account Creation – Explains handing-off of details related to CASA Account
created in FCUBS to FCPB.

TD Account Creation – Explains handing-off of details related to TD Accounts created in
FCUBS to FCPB.

Loans and Liability Information – Explains handing-off of details related to loans
created in FCUBS to FCPB.
Details of Data Received from Oracle FCUBS to Oracle
FCPB
The details of the Interface Modules for Customer, CASA, Liabilities and TD are as given below:
Entity
Action
Frequency
Source
Target
CIF Authorization/Modification/Closure
Add
On-line
FCUBS
FCPB
Broker Data
Add
On-line
FCUBS
FCPB
CASA Account Creation
Add
On-line
FCUBS
FCPB
CASA Account Balances
Add
On-line
FCUBS
FCPB
TD Account Creation
Add
On-line
FCUBS
FCPB
TD Premature Withdrawal
Add
On-line
FCUBS
FCPB
TD Maturity with Interest Liquidation
Add
Batch
FCUBS
FCPB
Daily Accrued Interest on TD
Add
Batch
FCUBS
FCPB
Penalty on TD
Add
Batch
FCUBS
FCPB
Loan and Liability Information
Add
Batch
FCUBS
FCPB
3-1
3.3
Defining Interface Details from FCUBS to FCPB
Any FCUBS-FCPB interface originating from FCPB is driven by the flag
FCUBS_INTERFACE_FLAG=Y in REF_BANK_PARAMS. However, currently since we are only
supporting Customer/CASA/TD interfaces originated from FCUBS are supported, hence the value
is maintained as 'N'.
In FCUBS, we can assign Segments to customers. Based on certain factors, the RM in FCUBS
decides whether a Retail customer is eligible for a Wealth Segment and if eligible, upgrades the
customers to such a segment.
Whenever a customer is upgraded to Wealth set of segments, all his Accounts, Balances, TDs
etc would be sent to FCPB as EOD File Handoffs. For Retail Customers who have not been
assigned a Segment or Upgraded even once, the system will not send any notifications or EOD
File Handoffs to FCPB.
3.4
Transferring Data using XML Files
FCUBS sends XML based online notifications for Customer creation/modification, CASA account
creation/modification and TD creation/transactions to FCPB for the Segmented Customers only. It
does not send any XML notifications for retail customers that are not allotted any Segment in
FCUBS.
3.4.1 Creating Customer Data
Whenever a customer is created in FCUBS with customer type as Individual or Corporate and if
the Segment is also defined, notifications will be sent by FCUBS via an online notification XML to
FCPB.
If Customer Category is defined as 'Broker' with Segment not being mentioned/blank, FCUBS will
send an online Customer Creation Notification to FCPB. FCPB would create the details for a
Broker in Broker Master Table. If the Segment is not mentioned for the ‘Broker’ created in FCUBS
due to any reason, then the system will generate Segmentation Upgrade files at EOD for Broker.
Thus resulting in a failure while uploading such Customer Segmentation Upgrade files in FCPB,
as this ‘Broker’ as a customer is not created in FCPB.
3.4.1.1 SETUP Needed for Enabling Customer Creation Interface from FCUBS
Mapping of Client IT Type, Segment, Status, Client Classification and Client Category in
FCPB:
FCPB has capability to define various types of Client IT Types like Individual, Corporate, NRI etc.
These values are to be maintained in FCPB with the same values that are being maintained at
FCUBS during Implementation. Similarly Client Category, Client Status are also maintained
suitably in REF Tables of both FCPB and FCUBS systems. These tables are then synched-up via
Transaction_Transformation screen, so that FCPB's internal names and values are mapped to
FCUBS's names.
The important tables and screens to be synched-up between FCUBS and FCPB are mentioned
below:
Tables
Screen Name
3-2
Navigation
Tables
Screen Name
Navigation
REF_CLIENT_SEG
Client Segment
Master  CRM
Related  Client
Segment
REF_CLIENT_STATUS
To be updated directly in the database
REF_CLIENT_IT_TYPE
Client IT Type
REF_CLIENT_CLASSIFICATION
To be updated directly in the database
REF_CLIENT_CATEGORY
Client Category
PREF_LANG_CODE
To be updated directly in the database
Master  CRM
Related  Client IT
Type
Master  CRM
Related  Client
Category
Handling of Mandatory fields in FCUBS and FCPB using Field Access Controller
The FAC framework of FCPB also supports you to maintain certain fields as Mandatory or NonMandatory for Demographics screen. Fields which are mandatorily from FCUBS should be setup
as Mandatory in FCPB via FAC screen for Demographics.
Similarly, fields which are non-mandatory or not available in FCUBS need to be setup as NonMandatory in FCPB via FAC screen for Demographics. Such fields need to be updated by the RM
in FCPB via Demographics screen with the actual values.
The following fields in FCPB are not available in FCUBS:

Occupation

Communication Mode

Preferred Language for Statement

Introducer Name

Contact Number

Client Notes

Zip

State

Tax Id

Gender

Client Classification

Location
3-3
Restriction to Modify FCUBS Fields using Field Access Controller
You are not allowed to modify the fields that are mandatorily received from FCUBS (like
Customer Name, Address, Status, Segment etc.) However, you can modify the fields which are
exclusively maintained by FCPB (fields which are not maintained by FCUBS) like Client Entity,
Hobbies, Preferred Communication Mode etc. The Implementer handles this using the Field
Access Controller Framework of FCPB.
3-4
Automatic Login Creation for New Customer
Whenever a customer is created in FCPB via the Create Customer XML from FCUBS, a script is
executed to auto-generate the Login ID of the customer. This script makes an entry in the
SMS_APP_USER table and assigns a Role to the customer which is same as one’s Segment
(after appropriate transaction transformation to FCPB's specific Segment Codes). For supporting
this, Roles are created for every segment. These roles are mapped as Customer Roles and the
names of these roles are identical to the Segments maintained.
Identifying Customer Currency and Creation of Portfolios
Customer's Currency Code is an essential field while creating a customer without which a
portfolio cannot be created in FCPB. The Create Customer Notification from FCUBS also
contains the Customer_CCY for all Wealth Customers. Portfolios in FCPB get auto-created on
creation of a new Customer with this Customer_CCY as the Portfolio Currency as well.
Directory Details for Corporate Clients
Currently, for corporate clients, FCPB supports only a single Director’s details.
Notification XML
For Customer Creation or modification, FCUBS sends the notification with the appropriate
Namespace and Notif code. The namespace is decided by the implementer at the time of
implementation and NOTIF_CODE would be “NOTIF_PB_CUSTOMER”.
There is no difference in Namespace or NOTIF_CODE for Creation and Modification of a
customer.
3.4.1.2 Process Flow
The following steps are involved in the process:
1. On receipt of Customer New_CIF_AUTH_NOTIFICATION XML from FCUBS, the customer
gets created in FCPB and the various tables get populated to store customer data like
CRM_CLIENT_MASTER, CRM_CLIENT_PREFERENCES, CRM_CLIENT_ADDRESS etc.
and CIF status gets updated to Active.
2. Once the client status becomes active, the default portfolio for the client gets created. This is
a customized script since different Banks would have different requirements for creating
default portfolios i.e. specific Portfolio_Types (like RMM, SLF, HLD etc).
3. Any modifications that are initiated at FCPB (like risk profiling and other details for which
FCPB is the owner), are automatically updated in FCPB and are not sent to FCUBS for any
further authorization.
4. The COMPLIANCE_REQUIRED_YN flag in REF_BANK_PARAMS is maintained as ‘N’ so
that the modifications via Demographics screen will not be sent to Compliance etc and status
of Customer can be made Active immediately.
5. When any modifications are made in the CIF demographic data in FCUBS (like address,
email), a full screen response notification is sent back to FCPB with the amended details.
6. The closure of CIF is also communicated from FCUBS to FCPB. On receipt of this closure
intimation from FCUBS, the status of the customer changes to ‘Closed’.
3-5
7. Updates based on Client IT Type:

If Client IT Type is Corporate, Director Sub-node in FCUBS may or may not have values
(it is not mandatory for FCUBS to fill in the director details at the time of corporate
customer creation). If the value is available, FCPB populates it in
CRM_AUTHORISED_SIGNATORY table with Signatory_Type as A (as mentioned in
mapping sheet). If not available, then the system will not fill it. This is not a mandatory
field from FCPB’s perspective.

If Client IT Type is Minor Y, then FCUBS provides the Guardian details In that case, first
name in CRM_AUTHORISED_SIGNATORY with Signatory_Type as G would be filled in.

If Client IT Type is Individual, then there is no concept of authorized signatory. So there
will be no entry in CRM_AUTHORISED_SIGNATORY table.
8. In FCUBS, customers can also be created quickly using the STDCIFAD screen. The
Operational workflow is as follows:

If a customer is created in FCUBS via the STDCIFAD screen, and later if such a
customer needs to be designated as a Wealth customer via the Segmentation screen,
then the Bank OPS user should remember that the STDCIFAD screen does not have an
RM ID Field, which is a mandatory field for FCPB integration.

Hence you have to first navigate to the Modify Customer screen in FCUBS and enter the
RM ID.

Then you have to navigate to the Segment Association screen and fill in the other details
like Segment, Upgrade Status etc.

FCPB will accept the Customer Creation Notification successfully, only if the above
workflow is followed.
3.4.2 Modifying Customer Data
If there are any modifications at FCUBS end, a full screen response notification is sent to FCPB
with the amended details.
3.4.2.1 Process Flow
The following steps are involved in the process:
The closure of CIF is also communicated from FCUBS to FCPB. On receipt of this closure
intimation from FCUBS, the status of the customer changes to ‘Closed’.
1. Any change in Segment (either Segmentation Upgrade or Downgrade) is also expected as a
part of Customer Modification. To support this, an additional element, the Customer
Segmentation Status, is sent to FCPB which would have values; Segment-Upgrade – 'U' or
Segment-Downgrade – 'D' and Segment-Reupgrade – ‘R’.
9. If the Segment is modified in FCUBS, then FCPB updates the Client_Seg column with the
new Segment Code in CRM_CLIENT_MASTER. Hence, the role of that customer changes
based on the new segment, by first identifying the Role_ID with NAME = Segment's name
from SMS_ROLE and then identifying User_id of the Customer from SMS_APP_USER. The
system then updates SMS_USER_ROLE table for that User_Id with the ROLE_Id for the new
Segment.
3-6
3.4.2.2 Updating Crm_Client_Master Table
The customer status in FCPB gets updated (i.e. Client_Status in CRM_CLIENT_MASTER) based
on the following xml attributes.

CUSTSEGSTATUS

TXNSTAT

FROZEN
Rules for updating the Client_Status in FCPB:

Will be marked CLOSED if TXNSTAT is C

Client_status will be updated as Suspended in FCPB, if CUSTSEGSTATUS is ‘D’ or
FROZEN is ‘Y’.

Customer_Status will be Active, if TXNSTAT is ‘O’ or CUSTSEGSTATUS ‘U’ or ‘R’ or
FROZEN is ‘N’,

Any other status results in an updation failure and an the error message will be sent:
Not a valid Customer status
1. A new column called 'Status_Description' is introduced in CRM_CLIENT_MASTER and it
gets updated as mentioned below.

If Segment Status in the Modification XML is Upgrade ('U' in CUSTSEGSTATUS Tag),
FCPB defaults this column with description as 'Activated customer due to Upgrade from
Core Banking System'.

If Segment Status in the Modification XML is Reupgrade ('R' in CUSTSEGSTATUS Tag),
FCPB defaults this column with description as 'Activated customer due to Re-upgrade
from Core Banking System'.

If Segment Status in the Modification XML is Downgrade ('D' in CUSTSEGSTATUS Tag),
FCPB defaults this column with description as 'Suspended customer due to Downgrade
from Core Banking System'.

If Segment Status in the Modification XML is Closed ('C' in TXNSTAT Tag), FCPB
defaults this column with description as 'Closed customer due to Closure from Core
Banking System'.

If Segment Status in the Modification XML is Frozen ('Y' in FROZEN Tag), FCPB defaults
this column with description as 'Suspended customer due to Frozen Status received from
Core Banking System'.
2. Any change in Segment (either Segmentation Upgrade or Downgrade) is also expected as a
part of Customer Modification. To support this, one more additional element, the Customer
Segmentation Status, is sent to FCPB which would have values; Segment-Upgrade – 'U' or
Segment-Downgrade – 'D' and Segment-Reupgrade – ‘R’.
10. If the Segment is modified in FCUBS, then FCPB updates the Client_Seg column with the
new Segment Code in CRM_CLIENT_MASTER. Hence, the role of that customer changes
based on the new segment. by first identifying the Role_ID with NAME = Segment's name
from SMS_ROLE and then identifying User_id of the Customer from SMS_APP_USER and
updating SMS_USER_ROLE table for that User_Id with the ROLE_Id for the new Segment.
The Customer Modification XML includes the fields Segment, Branch ID, Banker ID, Client Status
and Portfolio_ID.
3-7
The details of online notifications for Suspended Status Client are given below:
3.4.2.3 Process Flow
The following steps are involved in the process:
1. The Frequency of this notification would be one time migration and daily incremental, online.
11. For modification and closure, there would be a special notification message. For modification
and closure, the notif code would be notif_co_customer_mod. When the customer details are
modified, the txnstat would be ‘O’ and in case of closure, the txnstat would be ‘C’.
12. On receiving closure notification from FCUBS, the CIF status in FCPB will stand closed.
3.4.3 Client Suspended Status
The details of online notifications for Suspended Status Client are given below:
3.4.3.1 Process Flow
The following steps are involved in the process:
1. The Frequency of this notification would be one time migration and daily incremental online.
13. If the customer is suspended for a temporary time period, the status of such customer is
updated as Frozen in FCUBS and on receipt of notification xml the customer status in FCPB
gets updated as S (Suspended status).
14. This notification comes in the same way as any other modification notification from FCUBS.
The same XML message gets transmitted with the ‘Frozen’ attribute being marked as ‘Y’.
15. Similarly, if the Frozen status is revoked at FCUBS, it is again communicated to FCPB via
customer modification notification XML with the Frozen attribute being marked as ‘N’. In this
case, the client status in FCPB reverted back to ‘A’ (active status) provided the already
available status of client is ‘S’.
16. The notification message for communicating that the customer being Frozen would be
NOTIF_CO_CUSTOMER_MOD and txnstat would be ‘O’ in this case.
FCPB Column Name
Description
FCUBS Element
Name (as per
the XML)
Updation in CRM_CLIENT_MASTER
Client_status
If Frozen is Y, then client_status would be made
as ‘S’ (provided if already available status is A).
Or if Frozen is N, then client_status would be
made as ‘A’(provided the already available status
for the client is S)
3-8
Frozen
3.4.4 Broker Data
The Broker data is handed-off to FCPB using the XML format similar to Customer Creation
The details of online notifications for Broker are given below:
3.4.4.1 Process Flow
The following steps are involved in the process:
1. The Frequency of this notification would be one time migration and daily incremental online.
17. The broker is created in FCUBS and sent to FCPB.
18. The notification message for broker creation would be same as of create customer
notification - NOTIF_CO_CUSTOMER_NEW.
19. If Customer Category is mentioned as BROKER, then FCPB will identify the same as broker
and update the MST_Broker table.
20. The modification notification XML message for broker modification would be same as of
customer modification notification- NOTIF_CO_CUSTOMER_MOD.
FCPB Column Name
Description
FCUBS Element Name (as per
the XML)
Broker_name
(MST_BROKER)
First Name
FULLNAME (if FULLNAME not
available, then FIRSTNAME)
Broker_code
(MST_BROKER)
Broker code
CUSTNO
This tag would help in
identifying if the CIF
Notification is of broker
or not
CCATEGORY (In case of broker,
it would be broker or B)
Address1
(MST_BROKER)
Address Line 1
ADDRLN1
Address2
(MST_BROKER)
Address Line 2
ADDRLN2
Address3
(MST_BROKER)
Address Line 3
ADDRLN3
3.4.5 CASA Account Creation
The details of online notifications for CASA Account Creation are given below:
3-9
3.4.5.1 Process Flow
The following steps are involved in the process:
1. The Frequency of this notification would be one time migration and daily incremental online.
21. The asset type of products like current and savings account (CASA) would be created by
FCUBS and the details would be handed off to FCPB.
22. CA-New Customer Account-Notify-MSG service would be used by FCUBS to hand-off the
account details to FCPB.
23. The CASA Account would be created for customers whose status is Active. It is not opened
for a Contact person.
24. Once the notification message is received from FCUBS on the creation of CASA Account, the
account details would be inserted into CRM_CLIENT_BANK_ACCOUNT. Once the account
is created, no updates would be done to PMS_PORTFOLIO_HOLDING table. The Holdings
would only be updated after receiving the CASA Balance Update Notification.
FCPB Column Name
Description
FCUBS Element Name (as per
the XML)
Updation in CRM_CLIENT_BANK_ACCT
BANK_ACC_ID(CRM_C
LIENT_BANK_ACCT)
ACC
CLIENT_ID(CRM_CLIE
NT_BANK_ACCT):
Client_id is based on
External_Id which is
being sent as CUSTNO
CUSTNO
ACCT_CCY(CRM_CLIE
NT_BANK_ACCT)
CCY
ACCT_TYP(CRM_CLIE
NT_BANK_ACCT)
Use existing logic of
populating PROD_ID and
Instrument_ID to identify
ACC_TYP
ACCT_SUB_TYPE
ACCTYPE (to be parameterized
with values like S, C)
BANK_ID should be
defaulted to value in
BANK_ID of
MST_BANKS (It is
assumed that only one
branch of FCPB client
(like BMO, BDB is going
3-10
to be maintained in the
table)
ACCT_STAT should be
defaulted to A
ACCT_ADDRESS
respective address as in
ADDRESS column of
MST_BANKS table for
the respective BANK_ID
USE_IN_TRADING
should be defaulted to Y
BANK_NAME respective
name as in NAME
column of MST_BANK
table
PREFFERED should be
considered to be 1 if
CASA account currency
is equal to bank base
currency and for other
denominated accounts
and any ongoing receipt
of CASA accounts
denominated in bank
base currency would be
defaulted to 0
PORTFOLIO_ID(CRM_
CLIENT_BANK_ACCT)
For deriving the portfolio_id
the logic should be as follows:
For non-Heldaway/Internal
accounts, from
pms_client_portfolio for a
particular client, select the
portfolio_id as the portfolio
whose Default_Portfolio = ’Y’
having the same portfolio_type
as mentioned in
ref_instrument_type table for
Instrument_Type = ’CASA’.
The crm_client_bank_account
table would also store this
same portfolio_id for Asset
accounts for easy reference
and retrieval
Banker_Client_Indicator
(CRM_CLIENT_BANK_
ACCT)
Should be defaulted/updated
to ‘B’ for all CASA/TD records
which r being inserted/updated
3-11
from FCUBS Core Banking
system
Acct_branch
Branch_code
Acct_country_id
Country_code
Acct_description
ADESC(if the description is more
than 20 char, then FCPB should
truncate it to the extent of 20 char
and populate the same)
Opening_Date
ACCOPENDT
3.4.6 Customer CASA Account Balances Notification
The details of Customer CASA Account Balances Notifications are given below:
3.4.6.1 Process Flow
The following steps are involved in the process:
1. The Frequency of this notification would be one time migration and daily incremental online.
25. Any changes in the CASA Balances of the customer will be notified by FCUBS to FCPB.
3-12
26. The notification code used by FCUBS to communicate the change in the customer balances
would be “NOTIFY_AC_BAL”.
27. On account balance notification, the PMS_PORTFOLIO_HOLDING table is populated with
the Market_Value and Total_Acq_Cost columns based on the balances received in the
notification message.
FCPB Column Name
Description
FCUBS Element Name (as per
the XML)
SUB_PORTFOLIO_ID
(PMS_PORTFOLIO_HO
LDING)
CASA Account no
CUST_AC_NO
Client_id
(PMS_PORTFOLIO_HO
LDING)
CIF ID
CUSTNO
INSTRUMENT_CCY
(PMS_PORTFOLIO_HO
LDING)
Currency of the CASA Account
CCY
VALUE_DATE
(PMS_PORTFOLIO_HO
LDING)
The date of receipt of the
balances
Since it is online notification, the
XML would be received as and
when the balances are updated.
So the date of receipt of the XML
notification would be populated as
value_date
TOTAL_ACQ_COST
(PMS_PORTFOLIO_HO
LDING)
Actual Balance including
unclear balances
ACBALANCE
MARKET_VALUE
(PMS_PORTFOLIO_HO
LDING)
Balance available to be spent
ACAVLBAL
HOLD_AMOUNT
(PMS_PORTFOLIO_HO
LDING)
The current balance minus
available balance would give
the blocked/hold amount
ACBALANCE- ACAVLBAL
3.4.7 CASA Closure/Modification
The details of Customer CASA Closure/Modification Notifications are given below:
3.4.7.1 Process Flow
The following steps are involved in the process:
3-13
1. Once a CASA Account gets closed in FCUBS, the same should get reflected in FCPB.
NOTIF_CA_CUSTACC_MOD XML would be used to handover the CASA closure details to
FCPB. When the txnstat tag reads as C, it indicates that the CASA account is closed.
28. The Notification Code for CASA Modification/Closure will be: NOTIF_CUSTACCMOD_PB
FCPB Column Name
Description
FCUBS Element Name (as per
the XML)
CRM_CLIENT_BANK_ACCT
TXNSTAT = ‘C’
Bank_Acct_id
ACC
Client_id is based on
External_Id which is
being sent as CUSTNO
CUSTNO
Acct_Stat should
change to ‘C’
Closing_Date: Should
be defaulted as Current
Business Date on
receipt of TXNSTAT as
‘C’
29. CASA Accounts modified in FCUBS for the following fields, would also trigger a Modification
XML and the system updates following fields in FCPB:
FCPB Column Name
Description
FCUBS Element Name (as per
the XML)
CRM_CLIENT_BANK_ACCT
TXNSTAT = ‘O’
Bank_Acct_id
ACC
Acct_CCY
CCY
Acct_Sub_Type
ACCTYPE
Update Client_id based
on External_Id which is
being sent as CUSTNO
CUSTNO
Opening_Date
ACCOPENDT
3-14
Acct_Branch
Branch_Code
Acct_Country_id
Country_Code
Acct_Description
ADESC
The CUSTNO can be modified only if no transactions have yet happened on that CASA
account which means that once FCPB receives a CASA Balance Notification, there is no
possibility of modifying the CUSTNO for that CASA account.
However, if a CASA account has been created with ‘0’ balance and a few days later, FCUBS user
realises that an error has occurred in mapping the CUSTNO, then one may change the Customer
Number which will trigger a Modification XML for CASA Account. For this scenario, FCPB also
updates its own CRM_CLIENT_BANK_ACCOUNT table with the new/modified CUSTNO.
3.4.8 TD Account Creation
Following types of transactions related to TD are sent by FCUBS.
TD Transaction Types:

NEW: New FD

PAR: Withdrawal

INT: Interest Payout

MAT: Maturity Transfer

PEN: Penalty

RNW: Rollover
Whenever a TD gets booked in FCUBS, it is sent to FCPB by Online Notification.
The details of TD Account Creation Notification interface are given below:
3.4.8.1 Process Flow
The following steps are involved in the process:
1. The Frequency of this notification would be one time migration and daily incremental online.
30. Time Deposit would be created by FCUBS and the details will be handed off to FCPB.
31. TD-New Account-Notify-MSG notification service would be used by FCUBS to hand-off the
TD account details to FCPB.
32. Once the notification message is received from FCUBS for creation of TD Account, the
account details would be inserted into PMS_TRANSACTION, PMS_PORTFOLIO_HOLDING
and PMS_TD_HOLDING_DETAILS tables.
33. Once the account is created, the PMS_PORTFOLIO_HOLDING table is populated with Client
Id, TD Account No, Market Value and Total Acquisition Cost columns with the deposit
amount.
3-15
34. PMS_TRANSACTION table would also store the details as mentioned above. The Bid-Ask
indicator would be maintained as ‘B’ for the newly created TD account.
35. PMS_TD_HOLDINGS_DETAILS table would also store details like Client ID, Portfolio ID,
Sub Portfolio ID, Instrument ID, Prod ID, Balance, Currency, Maturity Date, Int_Rate, Tenor,
Tenor_Dm, Account Status and Booking Date.
36. Based on the XSD service used by FCUBS in transmitting the data to FCPB, the Tran_Type
would be populated in PMS_TRANSACTION table. The Tran_Type would be inserted as
‘NEW’ in the PMS_TRANSACTION table.
37. On insertion of the record in PMS_TRANSACTION table, advice would be generated for TD
Account creation.
FCPB Column Name
Description
FCUBS Element Name (as per
the XML)
TRAN_DATE
TRAN_TYPE- to be
defaulted to ‘NEW’
ACCOPENDT
Would be populated based on
the xsd notification service
received from FCUBS
AMOUNT
TDAMT
AMT_CCY
CCY
CLIENT_ID
CUSTNO
SUB_PORTFOLIO_ID
ACC
SUB_PORTFOLIO_ID(
PMS_PORTFOLIO_HO
LDING)
ACC
CLIENT_ID(PMS_POR
TFOLIO_HOLDING)
CUSTNO
INSTRUMENT_CCY(P
MS_PORTFOLIO_HOL
DING)
CCY
TOTAL_ACQ_COST
(PMS_PORTFOLIO_H
OLDING)
The TD deposit amount would
be populated
3-16
TDAMT
MARKET_VALUE(PMS
_PORTFOLIO_HOLDI
NG)
The TD deposit amount would
be populated
TDAMT
CLIENT_ID(PMS_TD_
HOLDINGS_DETAILS)
CUSTNO
SUB_PORTFOLIO_ID
ACC
PROD_ID(it will have
values like time deposit,
call deposit etc)
ACCLS(the same values to be in
sync with those values in FCPB)
CURRENCY
CCY
MATURITY_DATE
MATDT
INT_RATE
INTEREST_RATE under
<Tddetails> subnode
TENOR
DFTENOR
TENOR_DM- to be
defaulted to days
Will be defaulted to D(days)
since FCUBS would be sending
the tenor details in days
BOOKING_DATE
ACCOPENDT
Spread_Bps
In Account Class for TD Product ,
define a UDF with FLDNAME as
SPREAD (while creating the TD
Class) and the FIELD_VALUE for
this UDF will contain the Spread
3-17
3.4.9 TD Modification
The details of TD Modification Notifications are given below:
3.4.9.1 Process Flow
The following steps are involved in the process:
1. If an incorrect interest rate is entered by the operations person in FCUBS while booking a TD,
the same can be corrected in FCUBS by invoking the TD Booking screen. This triggers a TD
modification event, which is sent via an XML interface to FCPB. The Notification Code for
such an operational modification event is
<NOTIF_CODE>NOTIF_TDMOD_PB</NOTIF_CODE>.
38. In ‘IC product preference screen (ICDPRMNT), “Main Interest Rate UDE” field should be
maintained mandatorily as “TERM_RATE” UDE for FCUBS and FCPB integration. This UDE
'TERM_RATE' would be referred by FCPB to pick up the Modified Rate in TD Modification
XML and updated in FCPB's INT_RATE column in PMS_TD_HOLDING_DETAILS
FCPB Column Name
Description
FCUBS Element Name (as
per the XML)
PMS_TD_HOLDINGS_DETAILS
MATURITY_DATE
MATDT
3-18
INT_RATE
UDE with value TERM_RATE
TENO
DFTENOR
Therefore, for any modification notification received from FCUBS, it should refer to these
columns and update it with approriate values shown in the XML for that particular CPIS
(CUSTNO, ACC).
3.4.10 TD Pre-Mature Withdrawal
The details of Customer CASA Account Balances Notifications are given below:
3.4.10.1
Process Flow
The following steps are involved in the process:
1. The Frequency of this notification would be one time migration and daily incremental online.
39. Whenever there is a pre-mature withdrawal of the deposit amount, FCUBS would notify
FCPB on the same.
40. The notif code to be used by FCUBS would be “NOTIF_ICREDM”.
41. FCPB will insert the TD or CD transaction details for ‘PAR’ type of transaction into
PMS_TRANSACTION. Based on the notif code, the system identifies the type and updates
Tran_Type in PMS_TRANSACTION as ‘PAR’. The Bid_Ask_Indicator for ‘PAR’ transactions
would be ‘S’ which means Transaction Processor should handle ‘PAR’ like a Sell transaction.
42. Since the amount received in the PAR transaction will be the Withdrawn principal, the
balance Principal will have to be calculated (as balance = previous balance from
PMS_TD_HOLDINGS_DETAILS – withdrawal amount) and updated in
PMS_PORTFOLIO_HOLDING with Buy Cost and Market Value (and all related fields like
ACQ_COST_CL also reduced accordingly). Also PMS_TD_HOLDINGS_DETAILS to update
fields like balance with the current balance principal after the partial withdrawal.
FCPB Column Name
Description
FCUBS Element Name
(as per the XML)
Updation in PMS_TRANSACTION
TRAN_TYPE- to be
defaulted to ‘PAR’
Would be populated based
on the xsd notification
service received from
FCUBS
AMOUNT
REDEMPTION_AMT
3-19
VALUE_DATE/Tran_Date
CHECKERDT
AMT_CCY
ACCOUNT_CCY
CLIENT_ID
CUSTNO
SUB_PORTFOLIO_ID
TERM_ACNO
Updation in PMS_PORTFOLIO_HOLDING
TOTAL_ACQ_COST
(PMS_PORTFOLIO_HOLDI
NG)
Reduce the TD Buy Cost by
the PAR Amt received i.e.
by the REDEMPTION_AMT
MARKET_VALUE(PMS_PO
RTFOLIO_HOLDING)
Reduce the TD
Market_Value by the PAR
Amt received i.e. by the
REDEMPTION_AMT
VALUE_DATE(PMS_PORT
FOLIO_HOLDING)
CHECKERDT
Updation in PMS_TD_HOLDINGS_DETAILS
BALANCE
Reduce the BALANCE by
the PAR Amt received i.e.
by the REDEMPTION_AMT
3.4.11 TD Rollover
The details of TD Rollover interface are given below:
3.4.11.1
Process Flow
The following steps are involved in the process:
1. The Frequency of this notification would be daily incremental EOD.
43. Time Deposit which are of Rollover type, would be auto-rolled over in FCUBS and the details
would be handed off to FCPB as a part of FCUBS BOD in a new file format (Rollover Format)
44. Even manual Rollovers performed by Operations at FCUBS end would be sent to FCPB
using the same XML Rollover Format.
45. Once the Rollover notification message is received from FCUBS, the transaction details
would be inserted into PMS_TRANSACTION and updated in PMS_PORTFOLIO_HOLDING
and PMS_TD_HOLDING_DETAILS tables.
3-20
46. On rollover, PMS_PORTFOLIO_HOLDING table would be updated for Market_Value and
Settled_MktValue columns with the rollover amount. But the TOTAL_ACQ_COST column
(and derived fields in Cust_CCY, Household_CCY, PF_CCY etc) should remain untouched
as it should continue to indicate the original booked TD's Principal Balance.
47. PMS_TRANSACTION table would also store the renewal details with Transaction_Type
'RNW' as mentioned above. The Bid Ask indicator (column in Pms_Transaction table) for a
Rollover TD would be a B (buy).
48. PMS_TD_Holdings_Details table would also be updated for BALANCE (same as Rollover
Amount), MATURITY_DATE (being sent in the Rollover XML), INT_RATE (being sent in the
Rollover XML) and Rollover Type.
49. PMS_TD_Holdings_Details table should not be updated for Booking Date and it should
continue to reflect the same date as the original TD Booking Date.
50. Interest_Amount would also be mentioned in the Rollover XML and if this value is not blank,
Transaction Processor would create an INT transaction in PMS_Transaction and update
Holdings fields related to Interest like Dividend_Interest (and its Fx converted fields)
51. As part of the EOD after the Rollover, none of the MAT/INT records for the Rolled-over TD
are available in the UBS_TDMAT File.
FCPB Column Name
Description
FCUBS Element Name (as
per the XML)
Updation in PMS_TRANSACTION
TRAN_DATE
TRAN_TYPE- to be
defaulted to ‘RNW’
AMOUNT
Indicating
Rollover Date
RENEWAL_DATE
RNW
Indicating
Rollover Amount
VALUE_DATE
Indicating
Rollover Date
AMT_CCY
Rollover CCY
CLIENT_ID
ROLLOVER_AMT
CCY
CUST_NO
INTEREST_AMOUNT
TP to create a
Txn 'INT' based
on this value
ACCR_INT_BAL
SUB_PORTFOLIO_ID
TD Reference
ACC
3-21
Number
Updation in PMS_PORTFOLIO_HOLDING
SUB_PORTFOLIO_ID
(PMS_PORTFOLIO_HOL
DING)
To be referred
just for
identifying the
CPIS record and
NOT for
updation
CLIENT_ID
(PMS_PORTFOLIO_HOL
DING)
To be referred
just for
identifying the
CPIS record and
NOT for
updation
MARKET_VALUE AND
SETTLED_MKTVALUE
(PMS_PORTFOLIO_HOL
DING)
The TD rollover
amount would
be populated
ROLLOVER_AMT
VALUE_DATE
(PMS_PORTFOLIO_HOL
DING)
Updation in PMS_TD_HOLDINGS_DETAILS
CLIENT_ID
(PMS_TD_HOLDINGS_D
ETAILS)
SUB_PORTFOLIO_ID
ACC
PROD_ID (it will have
values like time deposit,
call deposit etc)
BALANCE
ROLLOVER_AMT
CURRENCY
MATURITY_DATE
NEW_MAT_DATE
INT_RATE
INT_RATE
TENOR
TENOR
TENOR_DM- to be
defaulted to days
3-22
ROLLOVER TYPE
3.4.11.2
ROLLOVER_TYPE
Business Rules and Validations for TD interfaces
Only ‘Active’ transactions for TD are handled using the interface and Transaction Delete would
not be handled.
Rules for Handling TD Interfaces are Mentioned Below:
1. After a ‘NEW’ transaction is received on Booking a TD with a particular TD-referencenumber, any other ‘NEW’ transaction with the same reference number and same client
should be rejected with the reason ‘Duplicate Booking transaction with same reference
number already exists’.
52. After a ‘NEW’ transaction is received on Booking a TD with a particular TD-referencenumber, any other MAT or PAR transaction for the same reference number with Transaction
Date earlier than Booking Date should be rejected with reason ‘This is a new transaction;
cannot be a SELL’ . This rejection logic is in-built in the Transaction Processor of FCPB
which rejects SELLs without having a BUY.
53. After a ‘NEW’ transaction is received on Booking a TD with a particular TD-referencenumber, any other INT transaction for the same reference number with Transaction Date
earlier than Booking Date should be rejected with reason ‘Corporate Action cannot happen
with new Client ID, Portfolio ID, Instrument ID or Subfolio ID’. This rejection logic is in-built in
the Transaction Processor of FCPB which rejects Corporate Actions like INT without having
Holdings for that CPIS.
54. Whenever a ‘PAR’ Transaction is received, the system should first check if the ‘PAR’ amount
is more than the remaining balance principal and if ‘PAR Amount’ is greater than the Balance,
The system should reject the record with the reason ‘Withdrawal amount cannot be greater
than remaining balance principal’.
55. Backdated INT, PAR or MAT transactions should be allowed by the system, so long as it
doesn’t fail the other rules as mentioned in rules 2, 3, 4 above.
56. For the specified currency given along with the transaction, if system does not find FX Rate
maintained for Instrument Currency against with either Customer Currency, Portfolio
Currency, Household Currency, then system should reject with the reason ‘No FX Rate
available for specified currencies’.
57. If default Portfolio is not found for the client, then system should reject with the reason ‘No
default portfolio exists for the client’.
58. If no Instrument of type ‘TD’ is setup for the specified currency, then system should reject
using reason ‘No Instrument exists for the specified currency’.
3-23
59. If no relevant setup for Instrument and the specified currency is present, then system should
reject with the reason ‘No Instrument_ALT / MST_BANKING_PROD_ALT setup exists for the
Instrument with specified currency’.
60. There should be no validation related to Transaction_Date falling on a Holiday and no
rejection should be done even if the transaction_date is a System/Currency/Exchange
holiday.
61. All typical reject reasons in Enrichment procedures should be handled like mandatory-field
checks giving reject reasons like: Invalid Amount, Invalid Date, Invalid A/C No, Invalid
Transaction Type etc.
3.5
Data transfer using File Upload Mechanism
In addition to the online interface mechanism, there is certain data which is expected to be
received from FCUBS as part of file upload. The list is as given below:

TD Maturity along with interest liquidation

Daily Accrued Interest on TD

Penalty on TD (applicable in case of pre-mature partial withdrawal and pre-mature
complete withdrawal)

Loan and Liability Information
3.5.1 TD Maturity along with Interest Liquidation
FCUBS system uses the CSV Format to send the TD maturity related details. Maturity and
Interest liquidation are separate records in the same file. The same interest file format is also
used in case of interest payment for pre-mature full withdrawal and also in case of pre-mature
partial withdrawal.
The processing logic is mentioned in the below table:
Fields in
the file
format
Insertion in Respective tables
PMS_TRANSACTIO
N(for MAT txn)
PMS_TRANSACTI
ON(for INT txn or
PEN txn)
TRAN
REF NO
Can be stored as
Ext_Tran_Idn or
Ext_Tran_Ref
Can be stored as Ext_Tran_Idn or Ext_Tran_Ref
CUSTOM
ER_NO
Client_id
Client_id
3-24
PMS_PO
RTFOLIO
_HOLDIN
GS
Client_id
PMS_TD_HOLDI
NG_DETAILS
Client_id
CUSTOM
ER_NAM
E1
ignored
ignored
ignored
ignored
ACC
Sub_portfolio_id
Sub_portfolio_id
Sub_portf
olio_id
Sub_portfolio_id
ACCOUN
T_CLASS
Based on Account
class(whether it is
TD or call deposit,
instrument id and
instrument type
would be populated)details in
FCPB_FS_CASA_In
cludeinholdings_Rel2
.1- section 8)
Based on Account
class(whether it is
TD or call deposit,
instrument id and
instrument type
would be
populated)- details
in
FCPB_FS_CASA_In
cludeinholdings_Rel
2.1- section 8)
Based on
Account
class(whe
ther it is
TD or call
deposit,
instrument
id and
instrument
type
would be
populated
)- details
in
FCPB_FS
_CASA_In
cludeinhol
dings_Rel
2.1section 8)
Prod_id
TRN_DT
Tran_Date
Tran_Date
Value_Dat
e
Maturity_Date
LCY_AM
OUNT
Amount
Amount
Dividend_
Interest
Mat_Principal(new
field to be
introduced)
AC_NO
Indicates Dr/Cr
AcctNumber n
ignored
Indicates Dr/Cr
AcctNumber n
ignored
ignored
ignored
AC_CCY
Amt_ccy
Amt_ccy
Instrumen
t_Ccy
Currency
RECORD
_STAT
ignored
ignored
ignored
Account_status
TRANSA
CTION_T
YPE
Tran_Type=should
be defaulted to MAT
Tran_Type=should
be defaulted to
INT/PEN
ignored
ignored
3-25
Additional
Attributes
BIDASK_IND field would be defaulted as S
TOTAL_A
CQ_COS
T,
MARKET
_VALUE,
ACCRUE
D_INT,
ACQ_CO
ST_CL,
ACQ_CO
ST_PF,
ACQ_CO
ST_SC
would be
made as
zero
BALANCE field
would be made as
zero
FCUBS system sends the TD maturity related details as a part of their BOD process to ensure
that the data of the TDs maturing on that particular date or TDs which have INTEREST
transactions liquidated on that date should be received by FCPB on the BOD of that particular
date for further processing.
3.5.2 Daily Accrued Interest on TD
FCUBS uses CSV Format to send the daily accrued interest details.
The processing logic for the same is mentioned below:
Insertion in Respective Tables
Fields in File Format
PMS_PORTFOLIO_HOLDINGS
PMS_TD_HOLDING_DETAILS
CUST_NO
Client_Id
Client_Id
SHORT_NAME
Ignored
ignored
ACC
Sub_portfolio_id
Sub_Portfolio_Id
ACCOUNT_CLASS
Based on Account class
(whether it is TD or call deposit,
instrument id and instrument
type would be populated) details in
FCPB_FS_CASA_Includeinholdi
ngs_Rel2.1- section 8)
Prod_Id
ACCRUED_AMOUNT
Accrued_Int
Accr_Int
ENT_DATE
Value_Date
LAST_INT_ACC_DATE
3-26
CCY
Instrument_CCY
Currency
RECORD_STAT
Ignored
Account_Status
PROD
Ignored
Ignored
3.5.3 Penalty on TD (applicable in case of pre-mature partial withdrawal and premature complete withdrawal)
FCUBS supplies applicable Penalty details in the TD MATURITY file handoff itself. It would be
sent immediately in case of a pre-mature full withdrawal (not as part of EOD process). But in case
of pre-mature partial withdrawal, it would be sent as part of maturity EOD, when the complete
amount is withdrawn.
The processing logic is mentioned below:
Fields in File Format
Insertion in Tables
PMS_TRANSACTION (for PEN txn)
CUSTOMER_NO
Client_Id
CUSTOMER_NAME1
Ignored
ACC
Sub_portfolio_id
ACCOUNT_CLASS
Based on Account class whether it is TD
or call deposit, instrument id and
instrument type would be populated.
S_TRANSACTION_TYPE
Tran_Type = should be defaulted to PEN
TRN_DT
Tran_Date
LCY_AMOUNT
Amount
ACC_CCY
Amt_CCY
AC_NO
Bank_Acct_id
RECORD_STAT
Ignored
3.5.4 Loan and Liability Information
FCUBS uses CSV Format to hand-off the loan and liability information:
All the relevant fields are inserted into PMS_PROD_BAL table. An entry is also made in
CRM_CLIENT_BANK_ACCT as well. The details are mentioned below:
The processing logic is mentioned below:
3-27
Fields in File Format
Insertion in Respective Tables
CRM_CLIENT_BANK_ACCT
CUSTOMER_ID
Client_id
ACCOUNT_NUMBER
BANK_ACCT_ID
PROD
Acct_Typ
ACCT_ADDRESS
Ignore ACCT_ADDRESS and default
Address from MST_BANK
For a liability product, the portfolio id would not be populated in CRM_CLIENT_BANK_ACCT (as
it is currently being followed in the application).
While updating the Amount column in PMS_PROD_BAL table, if the Amount provided in the Prod
Bal file for LIABILITY type of Prod ID (by referring MST_BANKING_PROD table's
ASSET_LIAB_IND as 'L') is a positive value, it is updated with a negative sign. FCUBS would be
sending Loan/Liability Amounts as positive and hence these are inserted as negative values in
the PROD_BAL table so that in the Networth portlet of Customer Dashboard, it gets deducted
from Investment/Portfolio value to display the Total value.
3-28
3.6
Segment Upgrade/Downgrade Interfaces
Whenever a customer is upgraded to PWM set of segments, all his Accounts, Balances, TDs etc
would be sent to FCPB as EOD File Handoffs. For Retail Customers who have not been assigned
a Segment or Upgraded even once, no notifications or EOD File Handoffs would be sent to
FCPB.
Also, once a customer is downgraded, the CIF Modification online interface would be sent by
FCUBS to FCPB to inform about this downgrade. In this case, FCPB would update the
Client_Status as 'S' (Suspended) in CRM_CLIENT_MASTER table. It also updates the newly
introduced column Status_Description with description as 'Suspended due to Downgrade from
Core Banking System'.
Suspended customers in FCPB are not allowed to place orders or trade though their Portfolio
Details can be viewed via Portfolio Maintenance/Analysis screens etc. as per currently existing
functionality in FCPB.
Even if a customer gets downgraded, subsequent flow of TD-deal information/account
notifications/balances notifications will continue to flow into FCPB from FCUBS.
If the downgraded customer gets re-upgraded in FCUBS, then the CIF Modification online
interface would send the Status as ’Re-upgraded (R). This would prompt FCPB also to update the
status back to 'A' (Active) and activate the customer for all normal activities in FCPB like Order
Placement etc. In case of such re-upgrades, FCUBS does not send the set of files related to
portfolio and other handoffs as part of the EOD Segmentation Upgrade to FCPB.
Additional Validations to Customer Creation screen to support Segmentation Upgrade:
1. FCUBS would validate that when CIF creation is done for first time, the segment status
cannot be ‘Downgrade’.
62. If the RM (or any other user) who is creating the CIF decides to leave the segment related
fields blank, then those customer data would not be handed-off to FCPB.
63. FCUBS would also validate that once a customer is downgraded, later the status can only be
changed to re-upgrade..
It is assumed that no closed CASA account details would be handed off by FCUBS as a part of
segmentation upgrade files.
Only online notifications are planned for CASA creation and modification and any field level
change of CASA would trigger a modification.
As a part of customer upgrade files, FCUBS will not send any modification of accounts. It’s a
one-time hand-off of all the accounts for the upgraded customer.
The set of interfaces/files for Segmentation Upgrade/Downgrade are detailed in the below
sections.
3-29
3.6.1 Customer File Upload – Segmentation Upgrade
Once a customer gets upgraded as per the segmentation rules, FCUBS sends an online
notification based on which customer gets created in FCPB. FCUBS also generates an EOD file
handoff for these customers and sends it to FCPB. Subsequent updates to these customers will
be received via online notifications.
Whenever a customer is created in FCPB, a script is executed which auto-creates the Login ID of
the customer and makes an entry in SMS_APP_USER table. The Password field in
SMS_APP_USER will be updated as blank and will not have any significance, since FCPB
expects SSO for Customers from FCDB. The Role given to the customer would be the same as
his Segment (after appropriate transaction transformation to FCPB's specific Segment Codes).
For supporting this, Roles would have to be created for every segment which can be mapped as
Customer Role and the name of these roles would be identical to the Segment.
EXT_Portfolio_Id - In the current Rel12.0, FCPB assumes that the Bank will create only one
Investment Portfolio for each Customer and hence multiple Portfolio IDs will not be supported, at
FCUBS end.
FCPB must pick CUSTOMER_MASTER_SEGUP.csv file first and then
CASA_ACCOUNT_CREATE_SEGUP.csv before picking up any other feeds from shared
location.
3.6.2 Customer Account File Upload – Segmentation Upgrade
Once the customer gets upgraded as per the segmentation rules, FCUBS will generate an EOD
file handoff for these Customer Accounts to be uploaded into FCPB. Subsequent modifications to
these Customer Accounts then get updated via online notifications.
The Customer's preferred address would be sent to FCPB from FCUBS as a part of the CASA
Account creation/modification XML notification as well as via Segmentation Upgrade file. Since
Acct_Address is a part of the Branch setup/screen and not part of the FCUBS CASA Account
screen, the Acct_Address cannot be sent. Hence FCPB must ignore these address fields and it
should default CASA_Account related tables with Home Bank's Address (as maintained in
MST_BANK table).
3.6.3 Customer Balances File Upload – Segmentation Upgrade
Once a customer gets upgraded as per the segmentation rules, FCUBS will generate an EOD file
handoff for these customer balances to be uploaded into FCPB. Separate files for CASA
Balances and Liabilities Balances would be sent by FCUBS. Subsequent modifications to these
customer balances then get updated via online notifications.
Processes then get triggered to copy Settled_Market_Value from Market_Value column in
PMS_PORTFOLIO_HOLDINGS since CASA Instrument Type does not require any separate
Settlement.
For Liabilities Balances which are being sent in the UBS_SEG_PRODBL file while updating the
Amount column in PMS_Prod_Bal table, if the Amount provided in the Prod Bal file for LIABILITY
type of Prod ID is a positive value, it is updated with a negative sign in the Prod_Bal table so that
in the Networth portlet of Customer Dashboard, it gets deducted from Investment/Portfolio value
to display the Total value.
3-30
3.6.4 Customer TD Deals File Upload – Segmentation Upgrade
Once a customer gets upgraded as per the segmentation rules, FCUBS will generate an EOD file
handoff for all customer TD deals to be uploaded into FCPB.
Following are the different File uploads which would be sent by FCUBS. For TD, three types of
files would be received by FCPB as a result of Segmentation Upgrade:
Transactions/Deals for new Bookings, Partial Uplift and Rollovers called TD-DEAL
Booking
Since it is a common format being proposed for all the 3 transaction types, certain fields would be
mandatory for specific Tran_types.
Example: Spread is mandatory only for Booking Transaction Type and not for PAR or RNW.
Similarly, Rollover Type is mandatory only for RNW transaction types.
Since these are post settled deals which are indicative of the fact that the advice has already
been generated and sent across to the customer, FCPB will not generate advices for the same.
Spread is also one of the expected fields in the Segmentation Upgrade format for TD Booking. To
capture Spread (in BPS) at FCUBS end, the Account Class for TD Product is created with a UDF
with FLDNAME as SPREAD and the Field_Value for this UDF will contain the Spread. This
Field_Valule would also be sent in the Segmentation Upgrade file.
Transactions for Interest, Penalty and Maturity: Called TD-DEALMAT
The same format would be used for EOD batch handoff and customer upgrade handoff for the TD
Maturity/Interest/Penalty file.
FCUBS will only send Active TDs as part of Segmentation Upgrade handoffs. No
Closed/Matured TD Bookings or any other transactions/Holdings regarding Matured TDs
would be sent.
For NEW, PAR, RNW, INT, MAT and PEN records received as part of Segmentation Upgrade,
system updates the Settlement Flag as 'Y' in PMS_TRANSACTION. Processes then get
triggerred to copy Settled Market Value from Market_Value column in
PMS_PORTFOLIO_HOLDINGS since TD Instrument Type does not require any separate
Settlement.
Since this is indicative of the fact that the advice has already been generated and sent across to
the customer, FCPB will not generate advices for the same.
Holdings level file with Accrued Interest as of Date for TD:
Since Accrued Interest is already sent everyday as a part of EOD from FCUBS to FCPB, there
would be no separate file to be sent specially for Segmentation Upgrade. The same process of
sending Accrued Interest file as explained in earlier section on Daily Accrued Interest on TD
would be sent to capture the Accrued Interest by FCPB.
FCUBS will only send Active TDs as part of Segmentation Upgrade handoffs. No Accrued
Interest for Closed/Matured TDs would be sent.
Subsequent lifecycle of these deals will be via online notifications as is present today
3-31
3.6.5 Customer Online Notification – Segmentation Downgrade
Once a customer gets downgraded as per the segmentation rules, FCUBS will generate an online
Customer Modification notification with the status as 'D' or 'Downgraded'. Even if a customer gets
downgraded subsequent flow of deal information/account notifications/balances notifications will
continue to flow into FCPB from FCUBS.
After a downgrade, FCPB would update the Client_Status as 'S' (for Suspended) in
CRM_Client_Master and default a newly introduced column in CRM_Client_Master called '
Status_Description with 'Suspended due to Downgrade from Core Banking System'. Suspended
customers in FCPB are not allowed to place orders or trade (i.e. place Deals), though their
Portfolio Details can be viewed via Portfolio Maintenance/Analysis screens etc.
Once a customer gets downgraded, it may also happen that the same customer gets re-upgraded
later. In such cases, though FCUBS would send the online notification of re-upgrade via the
Customer Modification XML, at EOD it restricts the Segmentation Upgrade set of files and does
not send the same to FCPB. If FCUBS sends these files after re-upgrade, they would get rejected
as duplicates in FCPB.
Once FCPB receives such a Modification XML wherein Status is changed to 'Active'/'Re-upgrade'
for a customer who is currently in 'Suspended' status in FCPB, FCPB would update the status in
CRM_CLIENT_MASTER back to 'Active' and also update the Status_Description column to 'Reupgrade from Core Banking System'. Once the status is 'Active', the customer would be able to do
all activities permitted in FCPB for active customers like placing of orders and transactions etc.
3.7
Assumptions
1. It is assumed that FCUBS EOD process would run and get completed before triggering the
FCPB EOD process. All the Interface-related processing for Segmentation-Upgrade/Recon
that is required to be handled by FCPB would be triggered as a part of FCPB's EOD process.
64. Create Customer with From FCUBS Mode: Create Customer Menu would be removed in
FCPB so that customer creation only happens from FCUBS. Common REF tables in FCPB
and FCUBS have to be synchronized via Transaction_Transformation screen so that FCPB's
internal names/values are mapped to FCUBS's names. These are: REF_CLIENT_SEG,
REF_CLIENT_STATUS, REF_CLIENT_IT_TYPE, REF_CLIENT_CLASSIFICATION,
REF_CLIENT_CATEGORY
65. In FCUBS, customers can be created quickly via the STDCIFAD screen also and following is
the expected Operational workflow to be followed for the same

If a customer is created in FCUBS via the STDCIAD screen and later if such a customer
is designated as a Wealth customer via the Segmentation screen, then the Bank
Operations user should remember that the STDCIFAD screen does not have an RM Id
Field, which is a mandatory/important field for FCPB integration.

Hence the user has to first go to the Modify Customer screen in UBS and enter the RM Id

Then go to the Segment Association screen and fill in the other details like Segment,
Upgrade Status etc

Only if the above workflow is followed, Customer Creation notification would be accepted
by FCPB successfully.
3-32
66. FAC Setup to support Create Customer from FCUBS: All Mandatory Fields coming from
FCUBS should be kept non-modifiable in FAC for Demographics screen. This is to make sure
that user is not allowed to modify any of the fields which are mandatorily being sent by
FCUBS and present in the Create Customer XML (like External Id, Home Address, Status,
Acquisition Date, Segment etc). However, the user should be allowed to modify any field
which is exclusively maintained by FCPB (and not by FCUBS) like Client Entity, Hobbies,
Preferred Communication Mode etc. or even non-mandatory fields like Occupation, Work
Address, First Name etc. These fields need to keep modifiable in FAC and Demographics
screen. These should be handled by the Implementation team using Field Access Controller
screen and framework in FCPB.
67. Create Customer for BROKER: If Customer_Category is 'BROKER', then even though the
Segment is BLANK, FCUBS would send an online Customer Creation Notification to FCPB
and FCPB would enter the details for a Broker in MST_Broker table. We assume that nobody
would enter Segment in FCUBS screen for Broker category and in case if it is done by
mistake, there would be Segmentation Upgrade files generated at EOD even for Broker,
which would result in rejection of these records in FCPB. Hence for BROKER Category,
Segment should not be filled in the FCUBS screen.
68. Banker Id from FCUBS would be the Same as Wealth Department's RM: This is an
assumption we are making that the same RM would service the customer from Core Banking
and FCPB side. Because that's the only way we can map a customer's Primary RM after
receiving Banker_Code from FCUBS (as a part of Customer Creation interface). Similar
assumption is being made on Customer's Unit/Home Branch - Since FCUBS would be
sending the customer's branch, the Branch/Unit Hierarchy in FCUBS and FCPB is assumed
to be synchronized and the same.
69. Synchronization of other REF tables: Few REF tables need to maintain same values in
FCUBS and FCPB and this should be considered as a pre-requisite for every
Implementation. These are viz. REF_CURRENCY, REF_COUNTRY, CRM_UNIT_MASTER,
CRM_BANKER etc. For certain other tables like REF_CLIENT_CATEGORY,
REF_CLIENT_IT_TYPE, REF_SEGMENT, PBS_LANGUAGE_SUPPORT etc,
implementation team has to synch-up with FCUBS and maintain Transaction Transformation
in FCPB for such entities.
70. Role Setup in FCPB based on Segments Supported by the Bank: Roles would have to be
created for every segment which are mapped as Customer Role and the name of these roles
would be identical to the Segment. Whenever a customer is created in FCPB via the Create
Customer XML from FCUBS, a script is executed to auto-create the Login Id of the customer
and makes an entry in SMS_APP_USER table. The Role given to the customer would be the
same as his Segment (after appropriate transaction transformation to FCPB's specific
Segment Codes). For supporting this, Roles would have to be created for every segment
which are mapped as Customer Role and the name of these roles would be identical to the
Segment.
3-33
71. Segmentation Upgrade Files: Since FCUBS has the capability to run multiple-EODs in
different branches and Head Office, in order to avoid multiple Segmentation Upgrade Files
being sent by each branch (for same customer or even for different customers); FCUBS has
configured sending the Segmentation Upgrade files as part of Head Office's EOD Process
only. This process will therefore collate data for all newly-upgraded customers across all
Branches and send Customer Master/ Prod Bal/Accounts/CASA/TD-Deals in single
consolidated files (for each entity-interface) no matter where the TD-Deal/Account originated.
72. TD Booking: Only Fixed Interest Type of TDs and of Simple Interest Type would be
supported in this release. No Floating TDs or Compound Interest Type would be supported.
Dual Currency Deposits would also not be supported in this Release.
73. TD Rollover: Only Rollover Types of Principal or Principal+Interest would be supported in
this release. Special Amount Rollovers would not be supported.
74. Recurring Deposit TDs: In this release, Top-Up event for Recurring Deposits would not be
supported by FCPB. Recurring Deposits expects that an automatic top-up of the Deposit
Booking Amount is performed by FCUBS as per the pre-determined top-up frequency, which
should trigger a new XML/Notification with the top-up-amount mentioned. This
Notification/workflow is not available in the current release between FCUBS and FCPB.
75. Discounted TDs workflow in FCUBS: Discounted TDs are those wherein Interest is paid
upfront to the Customer, FCUBS would be sending this INT transaction as a part of BOD of
the Business Date after the Booking Date. Also Accrued Interest sent daily for such
Discounted TDs would be ‘0’ everyday till 1 day prior to Maturity Date.
76. TD with Interest Liquidation to TD A/C: In this release, there is a limitation to support TDs
where Interest Liquidation is to TD Account instead of CASA Account. Such TDs are either
capitalized /non-capitalized TD or Autorollover / Manual Rollover P+I TDs or Recurring
Deposit TDs where again the Interest is credited to TD A/C. The limitation here is that in UBS
full uplift is allowed to the extent of Principal + Interest Liquidated + Interest Accrued since
last liquidation. However in FCPB, since Partial/Full uplift is allowed only to the extent of
Balance Outstanding Principal, such withdrawals would get rejected in FCPB
77. TD Modification: FCPB would be referring to the UDE named 'TERM_RATE' to pick up
modified Interest Rate in TD Modification. Hence in IC product preference screen
(ICDPRMNT), “Main Interest Rate UDE” field should be maintained mandatorily as
“TERM_RATE” UDE for FCUBS and FCPB integration.
78. Autorollover with Segmentation limitation: There is a limitation in case an operator
segments a customer on a particular date and on the next date any of this customer's TDs
get Auto-Rolled over. Such Rollover XMLs currently fail to be accepted by FCPB because the
Segmentation details of the TDs booked have not yet been sent to PB at the time the
Autorollover XML has reached FCPB. What this means is that RMs/Bank Operators need to
be made aware that if they are integrating with FCPB, then if they are expecting an
Autorollover anytime between next Calendar Date and Next Business Date (this will take care
of Holidays in between today's date and Next Business Date also); then they should not be
segmenting the Customer today. They should operationally ensure that such customers are
segmented on the Next Business Date.
3-34
79. Future Dated TD Booking limitation: In this release there is a limitation on opening TDs
with account opening date in future. FCPB rejects any booking with future booking date.
Hence in FCUBS if a TD is booked with pay in through Cheque and after considering
Floating/Check Clearing days as say 2 days; the account opening date will consider the next
business day which would be in the future. An enhancement may be taken up by FCPB in
the future to allow such future dated TDs also.
80. Zero Balance TD limitation: In FCUBS, TDs can be created with ‘0’ balance (i.e. Recurring
Deposit TDs etc) wherein the Booking Amount is credited later. When such TD Booking
XMLs are sent to FCPB, FCPB is accepting the TD and creating a Zero Booking Amount for
the TD. This will however create a problem when customer tries to withdraw the TD in UBS
later, and this PAR XML will be rejected by FCPB saying 'PAR amount cannot be greater
than Balance Principal'.
81. Customer Creation/Modification: For corporate clients in this release, FCPB can support
only 1 Director and his details. If more than 1 director is input in FCUBS, FCPB is having
capability to show only first one.
3-35
4.
4.1
Oracle FCPB – FCDB Interface
Introduction
Oracle FLEXCUBE Private Banking (FCPB) is integrated with Oracle FLEXCUBE DIRECT
BANKING (FCDB) as a part of 12.0 release. This integrated system will provide a single-sign-on
to users for accessing Oracle FLEXCUBE Private Wealth Management screens. ’Wealth
Management‘ tab would be provided on the FCDB Customer dashboard which will allow a wealth
management customer to access the FCPB application.
The integrated system will also provide the aggregated holdings of the customer from the FCPB
system, under each investment category.
4.1.1 Rules for Single Sign-On from Oracle FCDB to FCPB
1. Session Management will remain independent between FCPB and FCDB i.e. Once the user
navigates to FCPB system from FCDB system, FCPB session will be created and managed
by FCPB. There would be no inter-dependency of sessions on either of systems.
82. The customers will not be able to access FCDB transactions when logged into FCPB.
83. While enabling a customer for private wealth management in host (UBS), the relevant CIF
details will be sent to the FCPB system as EOD file handoff as explained in FCPB_FCUBS
interface details.
84. If due to any reason, synchronization of customers (enabled for Wealth Management access)
between FCPB & host system (FCUBS) is not available and business user tries to access the
PWM menu via FCDB, the session will be forwarded to FCPB and FCPB will display the error
messages.
85. “You are not authorized to view the Wealth Management Portfolio. Please contact the Bank's
Administrator for more details”.
86. FCPB will have a one to one mapping between UBS customer-id and user id in FCPB
application. FCPB System will authenticate and display relevant information for the CIF
(Customer Id) that is passed from FCDB.
4.1.2 Investment Portfolio Details from FCPB to FCDB
The integrated system enables the user to view the Holdings/Investment-data available in FCPB
if the logged in user is a Wealth Customer and has wealth portfolio in FCPB. The data is
presented for all portfolio types i.e. Overall set of portfolios like RM Managed, Self Managed, Held
Away and Discretionary.
4-1
The FCPB system displays the holding for a customer grouped by Instrument Type as shown in
the below screenshot. This data will be passed on to FCDB via the interface. The integrated
system excludes fetching the details for instrument Types like CASA and/or TD which are already
present in the FCDB core banking system.
The investment portfolio of the customer is then displayed in the accounts summary section in the
Integrated dashboard.
4-2
5.
5.1
Oracle FCDB – FCPB Interface
Introduction
Oracle FLEXCUBE Direct Banking – Oracle FLEXCUBE Private Banking integration allows
Oracle FLEXCUBE Direct banking business user to view and manage their investment portfolio
available with Oracle FLEXCUBE Private Banking application using Single Sign On (SSO) with
Oracle FLEXCUBE Direct Banking application. Hence, the business users shall be able to access
FCPB application through FCDB login. This functionality is only available to the Retail Customers
of the bank.
This document mentions all the prerequisites required for this integration. This SSO login enables
the business user to access his wealth portfolio through Oracle FLEXCUBE Direct Banking within
the same session. Once Oracle FLEXCUBE Private Banking is launched from Direct Banking, the
sessions behave independent i.e. even if the business user logs out of Oracle FLEXCUBE Direct
Banking, Oracle FLEXCUBE Private Banking session stays alive as per the session management
policy set for Oracle FLEXCUBE Private Banking. The same also holds true if Oracle FLEXCUBE
Direct Banking session has been terminated.
The Investment portfolio of the customer is also displayed in the Account Summary Widget and
Account Summary Transaction if the customer is wealth enabled in FCDB and has a wealth
portfolio in Oracle FLEXCUBE Private Banking system.
5.2
Session Management
For Single Sign On between Oracle FLEXCUBE Direct Banking and Oracle FLEXCUBE Private
Banking, it is required that a new session be created in Oracle FLEXCUBE Private Banking
whenever the user clicks on the “Wealth Management” link in Oracle FLEXCUBE Direct Banking.
Oracle FLEXCUBE Direct Banking invokes the Oracle FLEXCUBE Private Banking URL once the
user clicks on the “Wealth Management” link. Following parameters are passed from FCDB to
FCPB for the link invocation:
"CUSTOMER_ID"
"IPADDRESS"
"PORT"
"DEVICE_TYPE"
"SESSIONID"
"JSESSIONID"
"USER_AGENT"
"USERID"
"ENTITYID"
5-1
Upon invocation of the Oracle FLEXCUBE Private Banking URL, Oracle FLEXCUBE Private
Banking verifies the validity of the request by invoking a session validation business service
exposed by Oracle FLEXCUBE Direct Banking. The service invoked for such session validation is
SessionServiceInterface.SessionService.getSession. This service is invoked over through
Webservice over SOAP. The following Webservice URL is exposed by FCDB for session
validation:
https://<ipaddress>:<port>/service/services/ServiceEndPoint
This service validates the combination of Session ID, J Session ID, Customer Id and User’s Login
entity ID as per the session maintained in Oracle FLEXCUBE Direct Banking.
For sample request and response messages and corresponding schema definitions for the XML,
kindly refer section 5.
5.3
Customer folio
Account Summary Transaction and Widget in Oracle FLEXCUBE Direct Banking displays the
customer folio maintained at Oracle FLEXCUBE Private Banking. For viewing customer folio in
Oracle FLEXCUBE Direct Banking, Oracle FLEXCUBE Private Banking exposes Restful Web
Services.
The URL for the customer folio URL is:
https://<ipaddress>:<port>/rest/rest/customerHoldingService/customerHoldings?&clientId={0}
Oracle FLEXCUBE Direct Banking invokes the above URL to get the response from Oracle
FLEXCUBE Private Banking in an XML format. This response is unmarshalled into java object
using context and supported jar of FCPB. Context is configured as Day Zero parameter in FCDB.
The instrument types to be displayed on FCDB dashboard and transaction are also maintained as
a day zero parameter in FCDB.
FCPB shared XSDS for customer folio which is used by FCDB to create FCPB.jar .This jar is
added to FCDB server class path along with other external jars.
5.4
Message Process
All the messages shared between FCPB and FCDB follow a specific XML format.
The following steps are involved:
1. The incoming message sent from FCPB also has a specific XML format. All the tags available
in the request are mandatory. The value for tag “udfValue” when tag “udfName” is
fldextsystems must be ‘PB’
87. .The response message is then sent from FCDB after session validations.
88. After the response message is sent, the customer folio response is received from FCPB.
5.5
Day 0 Parameters
There are few DAY 0 parameters maintained for this SSO integration.
5-2
PARAMETER NAME
PARAMETER VALUES
<identity>.<usertype>. PWM.EXTERNAL_URL
FCPB Dashboard URL exposed by FCPB.
<identity>.<usertype>.PWM.REMOTE_PORT
FCDB server port. This is sent for
authentication.
<identity>.<usertype>.PWM.REMOTE_ADDRESS
FCDB server IP address. This is sent for
authentication.
<identity>.<usertype>.WEALTH_DIMENTIONS_ID
List of dimension’s id which configured at
entity and user type level.
<identity>.WEALTH_DIMENTIONS_ID
List of dimension’s id which configured at
entity level. This is only check when there
is no configuration at entity and user type
level.
FCDB_FCPB.SEND.FCAT_REST_CONTEXT
FCPB context used for unmarshelling.
FCDB_FCPB.SEND.FCAT_REST_METHOD
FCPB customer folio URL invoking
method(e.g. GET,POST)
FCDB_FCPB.SEND.FCAT_REST_URL
FCPB customer folio URL
5-3
6.
6.1
Screen Glossary
Function ID List
The following table lists the function id and the function description of the screens covered as part
of this User Manual.
Function ID
Function Description
GIDIFTDF
Interface Definition
6-1
Oracle FLEXCUBE Wealth Management Interface
[April] [2013]
Version 12.0.1.13.0
Oracle Financial Services Software Limited
Oracle Park
Off Western Express Highway
Goregaon (East)
Mumbai, Maharashtra 400 063
India
Worldwide Inquiries:
Phone: +91 22 6718 3000
Fax:+91 22 6718 3001
www.oracle.com/financialservices/
Copyright © [2007], [2013], Oracle and/or its affiliates. All rights reserved.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
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 failsafe, 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.
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.
This software or hardware and documentation may provide access to or information on 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. 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.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement