The integration between FCIS and FCUBS enables banks to -
The request from online banking system to view and transact mutual funds is also received by FCIS when integrated with FCDB. These transaction requests from online banking system are further processed with the same FCIS and FCUBS integration.
This chapter contains the following sections:
This section describes the activities that take place in each system and its impact on the other.
This section contains the following topics:
The following integration activities take place in Oracle FLEXCUBE Universal Banking.
Core Entities Module
Following activities take place in Core Entities (CE) module:
Current and Savings Account Module
Following activities take place in Current and Savings Account (CASA) module:
Accounting Module
Following activities take place in accounting module:
The following integration activities that take place in Oracle FLEXCUBE Investor Servicing.
The prerequisites for this integration in each system are discussed below.
This section contains the following topics:
The prerequisites for this integration are as follows.
In ‘CSTB_PARAM’ table, set the option ‘FCIS_INSTALLED’ to ‘Y’. If this parameter is set to ‘Y’ and ‘FCIS_DBLINK’ is setthen the customers in FCUBS system can have unit holder relationship with FCIS system. The system displays an error message if you try to close the customer account from FCUBS and the same account is an active unit holder in FCIS.
If the option ‘FCIS_INSTALLED’ is ‘Y’ and the parameter ‘FCIS_DBLINK’ is not set, then the system displays a configurable override message as ‘FCIS DBlink is Not Maintained’.
In ‘CSTB_PARAM’ table FCIS_USER and FCIS_MODULE should be maintained. This has to be maintained in FCIS also. These parameter values will be fetched by the system and used in the FCIS web service ‘FCISCustomerInquiry’ call from FCUBS for displaying the Fund Holdings of the given Customer.
Complete the following maintenances in Oracle FLEXCUBE Universal Banking to enable the integration.
Queue Name |
Purpose |
MDB_QUEUE_REQUEST |
Online transaction request |
MDB_QUEUE_RESPONSE |
Online transaction response |
CIFCREATION_DEST_QUEUE |
Notification from Oracle FCUBS |
For further details on these maintenances, refer to the Core Services user manual of Oracle FLEXCUBE Universal Banking.
Note
The following data in FCUBS must be in sync with those maintained in FCIS system.
The Oracle FCUBS-FCIS integration is enabled only for customers who are marked as investment customers.
For further details on marking a customer as investment customer, refer to the section ‘Investment Customer Creation/Modification’ in this chapter.
You must manually handle the maintenances and parameters that should have common values in FCUBS and FCIS systems.
Refer to the section ‘Prerequisites in Oracle FLEXCUBE Universal Banking’ for details on common data.
In ‘CSTB_PARAM’ table FCIS_USER and FCIS_MODULE should be maintained.
Complete the following maintenances in Oracle FLEXCUBE Investor Servicing to enable the integration.
The following diagram provides a high-level information of the data flow and integration patterns used in FCIS-FCUBS integration.
The following table contains the integration processes, pattern of each process and the communication channels:
Integration Process |
From |
To |
Integration Pattern |
Communication Channel |
Create CIF |
FCUBS |
NA |
Manual input |
Manual input |
Create UH |
FCIS |
NA |
Manual input |
Manual input |
Get CASA details |
FCUBS |
FCIS |
Fetch (request-response) |
Web service |
CIF details |
FCUBS |
FCIS |
Event processing |
Queue - XML data |
CIF details EOD batch reconciliation |
FCUBS |
FCIS |
Transaction (batch process) |
Batch process |
Validate CIF closure |
FCUBS/FCIS |
FCIS/FCUBS |
Transaction (request-response) |
Web service |
Settlement request and response |
FCUBS/FCIS |
FCIS/FCUBS |
Transaction (request-response) |
Web service |
Settlement request and response - Batch |
FCUBS/FCIS |
FCIS/FCUBS |
Transaction (batch process) |
Batch process |
This integration uses -
The integration between FCUBS and FCIS enables you to create unit holder accounts and perform related transactions for customers maintained in FCUBS.
See “Annexure” on page 1. for the complete list of touch points of the integration process.
The activities involved in this integration are discussed under the following headings.
When an investment customer is created in Oracle FCUBS, a notification with the customer details is sent to FCIS system.
You can create a customer record in Oracle FCUBS using ‘Customer Maintenance’ (STDCIF) screen. The checkbox ‘Investment Customer’ under ‘Status’ details can be used for classifying a customer as an investment customer.
For further details on customer maintenance and description of fields on this screen, refer to the Core Entities user manual.
When an investment customer is created/modified, Oracle FCUBS sends a notification to FCIS system with the details of the new customer. Similarly, if an existing customer is classified as an investment customer during amendment, Oracle FCUBS sends a notification to FCIS with the customer details.
During FCUBS EOD operations, Oracle FCUBS generates a list of CIF IDs created/modified during that day and sends it to FCIS system. In case any customer creation/amendment is missed out in the online notification, it will be reconciled as part of the EOD batch process.
Source System |
Target System |
Operation |
Action |
Communication Channel |
Webservice/Notification Name |
Synchronous/Asynchronous |
FCUBS |
FCIS |
Customer |
Creation |
Notification |
NOTIF_IS_CUSTOMER |
Asynchronous |
FCUBS |
FCIS |
Customer |
Modification |
Notification |
NOTIF_IS_CUSTOMER |
Asynchronous |
In the integrated environment, closure of an investment customer is processed in FCUBS. An investment customer record can be closed only after closing all the unit holder accounts maintained in FCIS for that customer. If there is any active unit holder account associated with the customer, you will not be allowed to continue with the closure.
When all unit holder accounts associated with a customer is closed and authorized, FCIS triggers a web service process to update the data store in FCUBS. This process sets the option ‘Closure Allowed’ to ‘Yes’ in the screen ‘Closure Data from Channels (STSCUSCL) in FCUBS.
However, if the unit holder account is re-opened in FCIS, you can mark the option ‘Closure Allowed’ to ‘No’ as long as the customer record is in ‘Open’ status in FCUBS.
If the customer record is marked as ‘Closed’ in FCUBS, further changes will not be allowed.
If there is no linked unit holder accounts for in FCIS, you can close the customer record in FCUBS.
Following conditions should be satisfied to close a customer record:
Note
In case the customer record is already closed in FCUBS through web service requests, then the option ‘Closure Allowed’ cannot be set to ‘No’ in ‘Customer Closure Data’ screen (STSCUSCL).
For further details on ‘Customer Closure Data’ screen, refer to the section ‘Viewing Customer Closure Data from Channels’ in this chapter.
Source System |
Target System |
Operation |
Action |
Communication Channel |
Webservice/Notification Name |
Synochronous/Asynchronous |
FCIS |
FCUBS |
Customer |
Closure and reopen |
Webservice |
FCUBSCustomerService |
Synchronous |
FCIS |
FCUBS |
Customer closure and reopen reconciliation |
Reconciliation |
Flat file |
NA |
Asynchronous |
In Oracle FLEXCUBE Universal Banking, you can view the details customer closure data received from external channels in ‘Customer Closure Data’ (STSCUSCL) screen. You can search for the closure records based on certain parameters.
For a unit holder, when the option ‘US Indicia Available’ is modified (checked or unchecked), FCIS triggers a web service process to update the data in FCUBS. The web service is triggered after authorization of the change.
Source System |
Target System |
Operation |
Action |
Communication Channel |
Webservice/Notification Name |
Synchronous/Asynchronous |
FCIS |
FCUBS |
FATCA US INDICIA flag |
Change |
Webservice |
FCUBSCustomerService |
Synchronous |
FCIS |
FCUBS |
FATCA US INDICIA flag change reconciliation |
reconciliation |
Flat file |
NA |
Asynchronous |
For a CIF, when there is a change in FATCA classification, FCUBS triggers a notification to update the data in FCIS. The notification is triggered after authorization of the classification creation/change.
Source System |
Target System |
Operation |
Action |
Communication Channel |
Webservice/Notification Name |
Synchronous/Asynchronous |
FCUBS |
FCIS |
FATCA Classification |
Create |
Notification |
NOTIF_FATCA_CLASS |
Asynchronous |
FCUBS |
FCIS |
FATCA Classification |
Modify |
Notification |
NOTIF_FATCA_CLASS |
Asynchronous |
In FCIS, a unit holder account can be created for a customer record maintained in Oracle FCUBS.
While creating a unit holder account, you can validate the account details of the customer using ‘Validate’ button provided on the screen. You need to specify the branch code and account number in ‘Account Details’ tab of ‘Unit Holder Maintenance’ screen and then click ‘Validate’ button.
On clicking ‘Validate’ button, FCIS system will trigger a service request to FCUBS for enquiry of the account details. Following validations are applicable.
If the validation is successful, the FCIS system will populate the following details on the screen:
Note
The above validation is applicable only to the account numbers belonging to the bank whose entity ID is maintained in ‘sttm_bank’.
The details of SWIFT and IBAN will not be automatically updated even after successful validation.You need to manually updated them at the unit holder level.
When you save the unit holder details, the system also validates the holding pattern.
Source System |
Target System |
Operation |
Action |
Communication Channel |
Webservice/Notification Name |
Synchronous/Asynchronous |
FCIS |
FCUBS |
Settlement customer account validate |
Query |
Source - Http request from JS Target - Webservice |
FCUBSAccService |
Synchronous |
In the integrated environment, you can amend the customer details in FCUBS system. While creating or amending unit holder details in FCIS system, you can modify the attributes whose entity owner is identified as ‘CIF/UH’ or ‘UH’ in the following table.
You cannot modify the attributes whose entity owner is CIF.
Attributes |
Entity Owner |
CIF Number |
CIF |
Customer Category |
CIF/UH |
Investor Type |
CIF |
First/Company Name |
CIF |
Last Name |
CIF |
Middle Name |
CIF |
Title |
CIF |
Minor |
CIF |
Guardian Name |
CIF/UH |
Relationship |
CIF/UH |
Sex |
CIF |
Father/Spouse Name |
CIF |
DOB |
CIF |
Marital Status |
CIF |
Occupation |
UH |
A/c operation type |
UH |
Country of Incorporation |
CIF |
Address Line 1 |
CIF/UH |
Address line 2 |
CIF/UH |
City |
CIF/UH |
Country |
CIF/UH |
CIF/UH |
|
Contact person |
UH |
Int dialing code |
CIF/UH |
Telephone 1 |
CIF/UH |
Int Dialing Code |
CIF/UH |
Fax Number |
CIF/UH |
Identification Type |
CIF/UH |
Identification Number |
CIF/UH |
Date of Issue |
CIF/UH |
Date of Expiry |
CIF/UH |
Place of Issue |
CIF/UH |
TAX ID |
UH |
US Indicia Available |
UH attribute to be propagated back to CIF level in FCUBS |
FATCA Status |
CIF (This will be updated to 'Recalcitrant' if 'Recalcitrant' flag Is 'Yes' at FCUBS CIF level.) |
FATCA Classification |
CIF |
When all unit holder accounts associated with a customer is closed and authorized, FCIS triggers a web service process to update the data store in FCUBS. Along with that, the option ‘Investment Customer’ will be unchecked in the customer maintenance. However, you can manually check it again during customer amendment.
FCIS places an amount block creation request if the following conditions are satisfied:
FCIS system sends a request to FCUBS to place an amount block on the order amount (transaction amount + markup percentage) if there are sufficient funds in the account. The amount block happens on clear fund basis. The block request is auto authorized in FCIS.
On receiving the request, FCUBS verifies the following:
If the above validations are successful, then the FCUBS system places the block for the amount sent by FCIS and generates a block reference ID. FCUBS then sends a block successful message to FCIS system. FCIS system generates a block reference ID for the amount block.
If the subscription amount is modified before or after authorization, the amount block is also updated as the new amount. If the system cannot place the block on revised amount, the subscription transaction modification will not be allowed.
The amount block is automatically released in the following cases:
During BOD process, the FCIS system generates amount block creation flat file for the SIP transactions whose payment is due on that day. The file is sent to FCUBS system. Based on successful response of amount block creation from FCUBS, SIP subscription transactions are created in FCIS.
Source System |
Target System |
Operation |
Action |
Communication Channel |
Webservice/Notification Name |
Synchronous/Asynchronous |
FCIS |
FCUBS |
New Transaction -Amount block Creation |
Save |
Webservice call from insulation layer |
FCUBSCustomerService |
Synchronous |
FCIS |
FCUBS |
Transaction Amendment and Change in amount -Amount block amendment |
Save |
Webservice call from insulation layer |
FCUBSCustomerService |
Synchronous |
FCIS |
FCUBS |
Online Amount block failure reconciliation |
Reconciliation |
Flat file |
NA |
Asynchronous |
FCIS |
FCUBS |
SIP process during BOD - amount block creation |
BOD batch |
Flat file |
NA |
Asynchronous |
Settlement happens either online or in a batch process configured to run as part of Mini EOD or EOD process.
The settlement happens as described in the following table.
Sl. No. |
System |
Process |
1 |
FCIS |
Triggers a web service call to release the amount block |
2 |
FCIS |
Sends the settlement entries to FCUBS system as a flat file as part of settlement batch |
3 |
FCUBS |
Processes accounting entries flat file, posts the accounting entries in FCUBS to debit the customer account and credit the respective GL account (applicable to settlement of IN transactions only) |
4 |
FCUBS |
Releases the amount block on passing the accounting entries |
5 |
FCUBS |
Sends response to FCIS system as a flat file |
6 |
FCIS |
If settlement process is successful, triggers payment clearing process |
7 |
FCIS |
If settlement process is failed, triggers payment rejection process based on the error codes |
8 |
FCIS |
Marks the status of the transaction as ‘Settled’ |
Note
Not the following:
For settlement related accounting entries the debit/credit leg will be generated in the transaction currency and other leg will be in fund base currency.
Source System |
Target System |
Operation |
Action |
Communication Channel |
Webservice/Notification Name |
Operation Code/Synchronous |
FCIS |
FCUBS |
Transaction authorisation - Online Settlement |
Authorization |
Webservice call from insulation layer |
FCUBSIFService |
CreateExtAccEntries ReverseExtAccEntries Synchronous |
FCIS |
FCUBS |
Online clearing -Online Settlement |
Authorization |
Webservice call from insulation layer |
FCUBSIFService |
CreateExtAccEntries ReverseExtAccEntries Synchronous |
FCIS |
FCUBS |
Post allocation- settlement and GL extract |
Intra day batch |
Flat file |
NA |
Asynchronous |
FCIS |
FCUBS |
Post allocation- settlement and GL extract |
EOD batch |
Flat file |
NA |
Asynchronous |
FCIS |
FCUBS |
Online settlement failure reconciliation |
Reconciliation |
Flat file |
NA |
Asynchronous |
From Oracle FCUBS, you can view the fund details on an investment customer using ‘360 Degree Retail Customer View’ (STDCUSVW) screen.
FCIS system hands off the details of funds to FCUBS system during a query from ‘360 Degree Retail Customer View’ screen.
You can view the following investor fund details:
Source System |
Target System |
Operation |
Action |
Communication Channel |
Webservice/Notification Name |
Synchronous/Asynchronous |
FCUBS |
FCIS |
360 degree customer view screen - unit holding details |
Query |
Webservice |
FCISCustomerInquiry |
Synchronous |
The integration supports only one agency branch and one distributor module in FCIS.
EOD process in FCIS must be completed before triggering the EOD process in FCUBS.