Oracle FLEXCUBE Universal Banking Integration
Contents
1. This integration uses e Web services for synchronous processes where request is sent and response is received in real time e Notifications when data is sent to the target system based on an event e Batch processes for data reconciliation Web services are used in FCIS for the following processes e Save and authorize amount block and settlement transactions e Update FATCA US INDICIA flag in FCUBS e Communicate to FCUBS that an investor customer record is ready for closure reopen Web services are used in FCUBS for fetching the investment details for a customer in 360 degree customer view Integration Process 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 3 1 for the complete list of touch points of the integration process The activities involved in this integration are discussed under the following headings Investment Customer Creation Modification 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 scre2. e Online settlement of transaction amount e Postallocation settlement and GL extract Integration Scope in Oracle FLEXCUBE Investor Servicing System The following integration activities that take place in Oracle FLEXCUBE Investor Servicing e Update the CIF details based on the customer creation and modification data received from FCUBS e Validate whether a customer record can be closed and update the FCUBS data store accordingly e Fetch customer account details from FCUBS while creating unit holder accounts e Based on US Indicia changes in FCIS FATCA classification is created and updated in FCUBS e Update the unit holder details based on FATCA classification changes received from FCUBS e Handoff the mutual fund details to FCUBS for displaying in 360 degree customer view e Maintain markup percentage to decide the buffer percentage for amount block e Request FCUBS to place modify and release amount blocks e Save reject the transaction based on the response received from FCUBS for amount block e Generate accounting entries as part of Mini EOD and EOD process e Generate batch request to FCUBS for amount blocks for Systematic Investment Plan SIP transactions e Passreversal entries in case of settlement failure Prerequisites The prerequisites for this integration in each system are discussed below Prerequisites in Oracle FLEXCUBE Universal Banking The prerequisites for this integration are as follows P
3. patterns used in FCIS FCUBS integration Validate for CIF Closure CIF Details E EOD Batch Reconciliation CIF Details Create CIF Create UH Get CASA details Settlement Request and Response Settlement Request and Response Integration Communication Pattern Data Flow Fetch Webservice Data Flow Request Response Webservice Data Flow Batch Process Batch Process Manual Input Manual Input Data Flow Event Notification Queue XML data The following table contains the integration processes pattern of each process and the communication channels Integration Communication Integration Process From To Pattern Channel Create CIF FCUBS NA Manual input Manual input Create UH FCIS NA Manual input Manual input Get CASA details FCUBS FCIS Fetch request Web service response CIF details FCUBS FCIS Event processing Queue XML data CIF details EOD batch FCUBS FCIS Transaction Batch process reconciliation batch process 28 ORACLE 2 5 2 5 1 Integration Communication Integration Process From To Pattern Channel Validate CIF closure FCUBS FCIS Transaction Web service FCIS FCUBS request response Settlement request and FCUBS FCIS Transaction Web service response FCIS FCUBS request response Settlement request and FCUBS FCIS Transaction Batch process response Batch FCIS FCUBS batch process
4. Line 1 CIF UH 2 10 ORACLE Attributes Entity Owner Address line 2 CIF UH City CIF UH Country CIF UH Email 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 2 5 7 Unit Holder 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 Along with that the option Investment Customer will be unchecked in the customer maintenance However you can manually check it again during customer amendment 2 5 8 Amount Block Amount Block Creation FCIS places an amount block creation request if the following conditions are satisfied e Account details are validated e Mode of payment is direct debit e Bank is internal bank 2H ORACLE 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 fu
5. 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 e Record is available for the customer ID entity id in Customer Closure Data STSCUSCL screen e The option Closure Allowed is set to Yes in Customer Closure Data STSCUSCL 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 2t ORACLE 2 5 2 1 2 5 3 2 5 4 Data Exchange i Synochro Communi Webservice y Source Target RINT nous Operation Action cation Notification System Syste
6. 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 Maintenances Complete the following maintenances in Oracle FLEXCUBE Investor Servicing to enable the integration e Client country codes NT FCUBS DIRECT DEBIT e Block allowed transaction reference types e Param code for Transaction code Mark up percent ea ORACLE Error code Integration parameter maintenances GL maintenance for events S and U GL maintenance trigger event S Client country bypassciff CIFIDNTFCCHK FATCAAPPLICABLE DEDUPCHKFORCIF UH to be created with Direct Debit Applicable as Yes Scheduler maintenances CIF Creation Import CIF Closure Export FATCA Import FATCA Export Amount Block New Export Amount Block Close Export Amount Block Response Import Accounting Export Account Response Import Interface maintenances CIF Creation Import CIF Closure Export FATCA Import FATCA Export Amount Block New Export Amount Block Close Export Amount Block Response Import Accounting Export Account Response Import ORACLE 2 4 Data Flow and Integration Patterns The following diagram provides a high level information of the data flow and integration
7. 5 2 Investment Customer Closure sse 2 7 2 5 3 Investment Customer US Indicia Modification ssssssuss 2 8 2 5 4 Investment Customer FATCA Classification Change 2 8 2 5 5 Unit Holder Creation sse 2 9 2 5 6 Unit Holder Amendment een aE n E e TEETE 2 10 2 5 7 Unit Holder Closure adde nieder pnta na tena AENEA 2 11 2 5 8 Amount BIOCK us eeu ena ae epo nra uu 2 11 2 5 9 Amount Settlement esses eise ied ead a iea 2 13 2 6 Investor Fund Details in 360 Degree Customer View see 2 15 2f JASSUumbptlODns ee itia tease dieti tlle icc ACER a dude Ue setates Laer cedit 2 16 PAINS KO ie toto ee ode ccpececerencace ca Dee Lec ctetu it latus Dedi c erede ades ec ter ended 3 1 3 1 Data Exchange between FCUBS and FCIS ssssse 3 1 3 2 Gateway Web Service cccccceccsceeeeeeetaneeeedeeaceceeeceecaneeeeeecaneneeeeeedenseeeeeeeneneeees 3 1 1 1 1 2 1 3 1 4 1 Preface Introduction This document is designed to help acquaint you with the integration among Oracle FLEXCUBE products viz Oracle FLEXCUBE Universal Banking Solutions FCUBS and Investor Servicing FCIS Besides this user manual while maintaining the interface related details you can invoke the context sensitive help available for each field This help describes the purpose of each field with
8. FLEXCUBE Universal Banking FCDB Oracle FLEXCUBE Direct Banking FCIS Oracle FLEXCUBE Investor Servicing EOD End of Day SIP Systematic Investment Plan CIF Customer Information File CASA Current and Savings Account FATCA Foreign Account Tax Compliance Act Glossary of Icons This user manual may refer to all or some of the following icons Icons Function Ed Exit Add row Delete row EE Option List 1 7 Related Information Sources Along with this user manual you may also refer to the following related sources e Gateway web service documents Ve ORACLE 2 1 2 2 2 2 1 2 Oracle FCUBS FCIS Integration Introduction The integration between FCIS and FCUBS enables banks to e transact on mutual funds e post transactions from investor services to core banking e seamlessly process corporate actions like dividend liquidation and capital payout e harmonize customer and accounts across core banking investor services and online banking system e provide mutual funds details in customer 360 degree view to core banking users bank 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 Scope This section describes the activities that take place in each system and its impact on the
9. Oracle FLEXCUBE Investor Servicing Integration Oracle FLEXCUBE Investor Services Release 12 0 4 0 0 Part Number E57474 01 September 2014 ORACLE Oracle FLEXCUBE Investor Servicing Integration September 2014 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 2014 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 devel
10. ange Details xlsx This sheet has the following details e Source system and module e Target system and module e Operation e Action e Source communication channel e Target communication channel e Webservice notification name e Operation code e Queue name e View name e Reconciliation e Remarks e Response required e Synchronous Asynchronous e Format XSD available 3 2 Gateway Web Service For details on gateway web services that are part of the integration between FCUBS and FCIS refer to the respective Gateway Webservice documents I ORACLE
11. arameter Setup In CSTB PARAM table set the option FCIS INSTALLED to Y If this parameter is set to Y the customers in FCUBS system can have unit holder relationship with FCIS system Maintenances Complete the following maintenances in Oracle FLEXCUBE Universal Banking to enable the integration e Bank parameters basic information about the bank e Branch parameters details of head office regional offices and branches e ORACLE 2 3 1 3 2 3 2 2 3 2 1 e Messaging queues maintain the following queues 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 Bank code Branch code Currency Exchange rate source Investor category Investor type Title Country Investment Customers 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 Prerequisites in Oracle FLEXCUBE Investor Servicing You must manually handle
12. en refer to the Core Entities user manual Online Notification 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 25 ORACLE 2 5 2 classified as an investment customer during amendment Oracle FCUBS sends a notification to FCIS with the customer details Batch Reconciliation 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 Data Exchange Synchro Communi Webservice y Source Target RS nous Operation Action cation Notification System System Asynchr Channel Name nous FCUBS FCIS Customer Creation Notification NOTIF IS CU Asyn STOMER chronous FCUBS FCIS Customer Modifica Notification NOTIF IS CU Asyn tion STOMER chronous Investment Customer Closure 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
13. in a screen You can obtain this information by placing the cursor on the relevant field and striking the F1 key on the keyboard Audience This manual is intended for the following User User Roles 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 implementa tion services Documentation Accessibility For information about Oracle s commitment to accessibility visit the Oracle Accessibility Program website at http www oracle com pls topic lookup ctx acc amp id docacc Organization This manual is organized into the following chapters Preface gives information on the intended audience It also lists the various Chapter 1 Ns chapters covered in this User Manual Chapter 2 Oracle FCUBS FCIS Integration explains the integration between Oracle P FLEXCUBE Universal Banking and Investor Servicing systems Annexure provides the details of data exchange and further reference Chapters sources t1 ORACLE Acronyms and Abbreviations Abbreviation Description System Unless and otherwise specified it shall always refer to Oracle FLEX CUBE Universal Banking Solutions system FCUBS Oracle
14. m Asynchro Channel Name no s FCIS FCUBS Customer Closure Webser FCUBSCus Synchro and reo vice tomerSer nous pen vice FCIS FCUBS Customer Recon Flat file NA Asynchro closureand ciliation nous reopen rec onciliation Viewing Customer Closure Data from Channels 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 Investment Customer US Indicia Modification 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 Data Exchange Communi Webservice Synchro Source Target DEM nous Svstem Svstem Operation Action cation Notification Asvnchr y y Channel Name Bis iih FCIS FCUBS FATCA US Change Webser FCUBSOCus Synchro INDICIA flag vice tomerSer nous vice FCIS FCUBS FATCA US recon Flat file NA Asyn INDICIA flag ciliation chronous change rec onciliation Investment Customer FATCA Classification Change 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 authorizati
15. nd basis The block request is auto authorized in FCIS On receiving the request FCUBS verifies the following e The CASA account has sufficient balance to process the trade e Account status allows debit transactions 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 Amount Block Modification 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 Amount Block Release The amount block is automatically released in the following cases e Deletion of subscription transaction e Reversal of subscription transaction e Subscription transaction fails in FCIS after amount block is placed e Change in settlement details before allocation in this case depending on the change in settlement details the amount block may be applied on a different account Systematic Investment Plans SIP 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 tra
16. nous ment and GL extract FCIS FCUBS Post alloca EOD Flat file NA Asynchro tion settle batch nous ment and GL extract FCIS FCUBS Online settle Recon Flat file NA Asynchro ment failure ciliation nous reconciliation Investor Fund Details in 360 Degree Customer View 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 e Unit holder ID e Fund ID e Name of fund e Fund base currency e Number of units s ORACLE e Average cost e Current value Data Exchange Communi Webservice Synehron Source Target agni ous Systemi System Operation Action cation Notification Asvnch o ysig yes Channel Name y nous FCUBS FCIS 360 degree Query Webser FCISCus Synchro customer vice tomerlnquiry nous view screen unit hold ing details 2 7 Assumptions 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 2 18 ORACLE 3 Annexure 3 1 Data Exchange between FCUBS and FCIS For details on data exchange between FCUBS and FCIS refer to the excel sheet Data Exch
17. nsactions are created in FCIS ORACLE 2 5 9 Amount Block Data Exchange Webservic Synchron Communic Source Target F e ous Operation Action ation System System Notificatio Asynchro Channel n Name nous FCIS FCUBS New Transac Save Webservice FCUB Synchro tion Amount call from SCustom nous block Crea insulation erService tion layer FCIS FCUBS Transaction Save Webservice FCUB Synchro Amendment call from SCustom nous and Change insulation erService in amount layer Amount block amendment FCIS FCUBS Online Recon Flat file NA Asynchro Amount block ciliation nous failure recon ciliation FCIS FCUBS SIP process BOD Flat file NA Asynchro during BOD batch nous amount block creation Amount Settlement 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 SI 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 pas
18. on of the classification creation change is ORACLE 2 5 5 Data Exchange Communic Webservice Synehreno Source Target oes us System System Operation Action ation Notification Asynchron Channel Name ous FCUBS FCIS FATCA Create Notification NOTIF FAT Asynchro Classifica CA CLASS nous tion FCUBS FCIS FATCA Modify Notification NOTIF FAT Asynchro Classifica CA CLASS nous tion Unit Holder Creation 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 e Specified bank account number is a valid account number for the primary CIF e Holding pattern of the bank account single joint is same as the unit holder holding pattern single joint with relevant CIF If the validation is successful the FCIS system will populate the following details on the screen e Account type e Account name e Account currency Note The above validation is applicable only to the account n
19. oped 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 product
20. other Integration Scope in Oracle FLEXCUBE Universal Banking System The following integration activities take place in Oracle FLEXCUBE Universal Banking Core Entities Module Following activities take place in Core Entities CE module e Notify FCIS about creation of a new investment customer and amendment of an existing investment customer e Handoffthe details of investment customer creation and amendment as a reconciliation batch to FCIS e During investment customer closure validate whether closure confirmation is received from FCIS e Create and modify the customer FATCA classification records based on the details received from FCIS e Notify FCIS about the customer FATCA classification creation and changes made in FCUBS e During 360 degree retail customer view display the mutual fund details received from FCIS Current and Savings Account Module Following activities take place in Current and Savings Account CASA module e While creating unit holder accounts FCIS retrieves customer account details from FCUBS e When there is a transaction request from FCIS the FCUBS system debits the customer account based on availability of funds e Based on the requests received from FCIS place modify and release amount blocks in FCUBS e Post settlement accounting entries received from FCIS 24 ORACLE 2 2 2 2 3 2 3 1 2 3 1 1 2 3 1 2 Accounting Module Following activities take place in accounting module
21. s 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 Contents Preface AIRE 1 1 TT introduction ie Pe GP a ne e e c ede ee M Ho bt mls 1 1 1 2 AUdIence ie eter eet te re EE et e eh et Urb p tede 1 1 1 38 Documentation Accessibility essen 1 1 TA Orcus TE 1 1 1 5 Acronyms and Abbreviations sssssesssenne eene 1 2 1 6 Glossary ot ICOnSzz iioi do on boe PUR initia ants 1 2 1 7 Related Information Sources sssssssssseene nennen enne 1 2 Oracle FCUBS FCIS Integration eene 2 1 2 nttoductlons u eco ge edet ba T HOD eas 2 1 2 2 SGODOT S recetas UL LE mE eu t UD E 2 1 2 2 1 Integration Scope in Oracle FLEXCUBE Universal Banking System 2 1 2 2 2 Integration Scope in Oracle FLEXCUBE Investor Servicing System 2 2 2 3 Prerequisites oie e Lace b e beu io ede vei abe a En ea e de de euin 2 2 2 3 1 Prerequisites in Oracle FLEXCUBE Universal Banking 2 2 2 3 2 Prerequisites in Oracle FLEXCUBE Investor Servicing 2 3 2 4 Data Flow and Integration Patterns ssssseenn emen 2 5 2 5 Integration PrOCeSS 3 5 oboe auc dene oe eei Oe 2 6 2 5 1 Investment Customer Creation Modification sss 2 6 2
22. sing the accounting entries 5 FCUBS Sends response to FCIS system as a flat file 6 FCIS If settlement process is successful triggers payment clearing pro cess 7 FCIS If settlement process is failed triggers payment rejection process based on the error codes 219 ORACLE SI No System Process 8 FCIS Marks the status of the transaction as Settled Note Not the following Payment rejection cases where FCIS has not automatically triggered reversals must be reversed manually Settlement related entries for redemption are triggered on confirmation 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 as ORACLE Data Exchange Webservi Operatio Communic Source Target ce n Code Operation Action ation TES System System Notificatio Synchron Channel n Name ous FCIS FCUBS Transaction Authori Webser FCUB CreateEx authorisa zation vice call SlFService tAccEn tion Online from insula tries Settlement tion layer Reverse ExtAccEn tries Synchro nous FCIS FCUBS Online clear Authori Webser FCUB CreateEx ing Online zation vice call SIFService tAccEn Settlement from insula tries tion layer Reverses ExtAccEn tries Synchro nous FCIS FCUBS Post alloca Intraday Flat file NA Asynchro tion settle batch
23. umbers 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 29 ORACLE 2 5 6 Data Exchange Webservi Synchro Communica Source Target ce nous Operation Action tion vet gh System System Notificati Asynchr Channel on Name onous FCIS FCUBS Settlement Query Source Http FCUB Synchro customer request from SAccSer nous account vali JS vice deus Target Webservice Unit Holder Amendment 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 Alc operation type UH Country of Incorporation CIF Address
Download Pdf Manuals
Related Search