Home

Oracle FLEXCUBE Wealth Management Interface User Manual

1. FIELD DESCRI LEN MAN FCC COL LE TABLE Fcubs NAME PTION GTH DATO UMNS NG NAME Remarks RY TH ATE UNT T ACCT A Address 200 YES ADDRESS 105 STTM CU DDRESS 1 ST ACCO UNT T ACCT A Address 200 NO ADDRESS 105 STTM CU DDRESS1 line 1 2 ST_ACCO UNT T ACCT A Address 200 NO ADDRESS 105 STTM CU DDRESS2 line 1 3 ST ACCO UNT T ACCT Account 100 NO LOCATIO 15 STTM_CU CITY city N ST_ACCO UNT T_ACCT_ Account 3 NO NULL COUNTRY country 1 id T HLD AC Held 1 YES N 1 DEFAULT CT YN away VALUE accoutn N YN T ACCT Accound 20 NO AC_DESC STTM_CU DESCRIPT descripti ST_ACCO ION on UNT Customer Balance CASA File Format The format of the customer balance file is given below FIELD DESCRIPT TYPE LE MAND FCC CO LE FCC FCC NAME ION NG ATORY LUMN NG Table Remarks TH TH name CLIENT _ Client id VARC 10 YES CUST_N 9 STTM_C ID HAR O UST_AC COUNT BANK_A Bank VARC 16 YES CUST_A 20 STTM C CCT_ID account id HAR C_NO UST_AC loan COUNT account id 2 24 FIELD DESCRIPT TYPE LE MAND FCC CO LE FCC FCC NAME ION NG ATORY LUMN NG Table Remarks TH TH name PROD product id VARC 5 YES PROD 4 ICTB E Interest D HAR NTRIES Product associated One account can have multiple interest product BOOKIN booking DATE YES AC OPE STTM C G DATE date N
2. TYP LEN MAN FCC LEN FCC Table FCC NAME PTION E GTH DAT COLU GT name Remarks ORY MN H CLIENT Client id VAR 10 YES CUST 9 CLTB_ACCO _ID CHA OMER UNT_MASTE R 1 R BANK_A Bank VAR 16 YES CUST 20 STTM CUST CCT ID account CHA AC ACCOUNT id loan R NO account id 2 26 FIELD DESCRI TYP LEN MAN FCC LEN FCC Table FCC NAME PTION E GTH DAT COLU GT name Remarks ORY MN H PROD 1 product VAR 5 YES PROD 4 CLTB_ACCO D id CHA UCT_ UNT_MASTE R CODE R BOOKIN booking DAT YES BOOK 8 CLTB_ACCO YYYYMMD G_DATE date E _DAT UNT_MASTE D format E R VALUE_ value DAT YES VALU 8 CLTB_ACCO YYYYMMD DATE date E E DA UNT_MASTE D format TE R AMOUN amount NUM 24 6 YES AMOU CLTB_ACCO T BER NT FI UNT MASTE NANC R ED CCY ID Currency VAR 3 YES CURR 3 CLTB ACCO CHA ENCY UNT MASTE R R MATURI Maturity DAT NO MATU 8 CLTB ACCO YYYYMMD TY_DAT date E RITY_ UNT MASTE D format E DATE R ACCT S Account VAR 5 YES L 1 Default UB TYP subtype CHA Value L E R Loan INT RA interest NUM 24 6 NO UDE CLTB ACCO TE rate BER VALU UNT UDE V E ALUES TENOR tenor NUM 10 YES NULL CLTB ACCO BER UNT MASTE R ACCR Accrued NUM 246 NO ACCR CLTB ACCO NT interest BER UED UNT SCHED AMOU ULES NT LAST IN Last DAT NO EVEN 8 CLTB ACCO Last T ACCR interest E T DA UNT EVENT
3. LDING VALUE DATE The date of receipt of the Since it is online notification the PMS_PORTFOLIO_HO balances XML would be received as and LDING when the balances are updated So the date of receipt of the XML notification would be populated as value_date PMS_PORTFOLIO_HO LDING TOTAL_ACQ_COST Actual Balance including ACBALANCE PMS_PORTFOLIO_HO unclear balances LDING MARKET_VALUE 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 External ld which is being sent as CUSTNO TXNSTAT C Bank_Acct_id ACC Client_id is based on CUSTNO Acct_Stat should change to C Closing_Date Should be defaulted as Current
4. Business Date on receipt of TXNSTAT as 29 CASA Accounts modified 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 0 Bank Acct id ACC Acct CCY CCY Acct Sub Type ACCTYPE Update Client id based CUSTNO on External Id which is being sent as CUSTNO Opening Date ACCOPENDT 3 14 3 4 8 Acct_Branch Branch Code Acct Country id Country Code Acct Description ADESC The CUSTNO can be modified only if 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 TD Account Creation Following types of transactions related to TD are sent by FCUBS TD Transaction Types e NEW New FD e PAR Withdrawal e Interest Payout e Maturity Transfer e PEN Penalty e RNW
5. CUSTSEGSTATUS Tag FCPB defaults this column with description as Activated customer due to Upgrade from Core Banking System e f 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 e f 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 e 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 e f 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 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 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 Segmen
6. Downgrade eene 3 32 Bit ASSUMPTIONS ect dein ro RR rr RE IR aspa asi TEE UR er d EE 3 32 4 ORACLE FCDB INTERFACQCE eres estesa 4 1 41 INTRODUCTIONT ha aaa Nu Cu a addet ted Takk kaos Se le 4 1 4 1 1 Rules for Single Sign On from Oracle FCDB to FCPB sss eene 4 1 4 1 2 Investment Portfolio Details from FCPB to FCDB sees ene eene nenne 4 1 5 ORACLE FCDB FCPB INTERFACE ua 7 ua eerte teens ienis riiin a 5 1 5 1 INTRODUCTION a EE Eee nies 5 1 3 2 SESSION MANAGEMENT W i et E ape tee eee dee dene RE et 5 1 23 9 CUSTOMER FOLIO SSS ES E RE REIR ENS 5 2 25 4 MESSAGE PROCESS eter ee epe maaa a san h up rt ete e e ipe A deus 5 2 9 9 DAYO PARAMETERS eter epe etr e ara eter i etate o D be e REO 5 2 6 SCREEN nrnr P 6 1 6 1 FUNCTION ID LAST sic etri re eh terre itr i rire gre reet eit tron Herd etes 6 1 1 1 1 2 1 3 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 e FC
7. 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 Re upgrade from Core Banking System Once the status is Active the customer would be able to do all activitie
8. PORTFOLIO HOL DING To be referred just for identifying the CPIS record and NOT for updation MARKET VALUE AND SETTLED MKTVALUE The TD rollover amount would ROLLOVER AMT PMS PORTFOLIO HOL be populated DING 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 3 4 11 2 ROLLOVER TYPE 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 52 53 54 55 56 57 58 After a NEW transaction is received on Booking a TD with a particular TD reference number 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 After a NEW transaction is received on Booking a TD with a particular TD reference number any other MAT or PAR transaction for the same reference number with Transaction Date earlier than Booking Date
9. 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 lt ipaddress gt lt port gt rest rest customerHoldingService customerHoldings amp clientld 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 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 Day 0 Parameters T
10. accrual DATE paid TE ST DIARY event happened date 2 27 FIELD DESCRI TYP LEN MAN FCC_ LEN FCC Table FCC NAME PTION E GTH DAT COLU GT name Remarks ORY MN H INTERE interest NUM 246 NO AMOU 22 CLTB ACCO ST PAI paid BER NT S UNT SCHED D ETTLE ULES D LAST IN Last DAT NO EVEN 8 CLTB ACCO Last T DATE interest E T DA UNT EVENT liquidation date TE ST DIARY event happened date HOLD A Hold NUM 246 NO AMOU 22 CLTB ACCO This will be MOUNT amount BER NT FI UNT MASTE derived NANC R from ED AMOUNT MINU FINANCED S E AMOU AMOUNT NT DI DISBURSE SBUR D SED Customer TD Booked File Format The format of the customer TD booked file is given below FIELD DESCRIP TYPE LEN MANDAT REMARKS SAMPLE VALUES NAME TION GTH ORY CLIEN External Varchar 10 Yes T ID customer ID TRAN Trantype Varchar 15 Yes Could be NEW for TYPE Booking PAR for Partial Uplift or RNW for Rollover ACCO Acount no Varchar 16 Yes UNT NO TRAN Transacti Date Yes DATE on date AMOU Amount Number 24 6 Yes Could be BookingAMt or PARAMt For NT PAR TranType or RolloverAMt for RNW tranType 2 28 FIELD DESCRIP TYPE LEN MANDAT REMARKS SAMPLE VALUES NAME GTH ORY CURR Currency Varchar 3 Yes EN
11. created for customers whose status is Active It is not opened for a Contact person 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 CLIEN T BANK ACCT BANK ACC ID CRM C LIENT BANK ACCT ACC CLIENT ID CRM CLIE NT BANK ACCT Client id is based on External ld 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
12. found for the client then system should reject with the reason No default portfolio exists for the client 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 e TD Maturity along with interest liquidation e Daily Accrued Interest on TD e Penalty on TD applicable in case of pre mature partial withdrawal and pre mature complete withdrawal e 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 Maturi
13. 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 int
14. sent via an XML interface to FCPB The Notification Code for such an operational modification event is NOTIF CODE gt NOTIF TDMOD PB lt 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 ACO 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 89 40 41 42 The Freguency of this notification would be one time migration and daily incremental online Whenever there is a pre mature withdrawal of the deposit amount FCUBS would notify FCPB on the same The notif code to be used by FCUBS would be NOTIF ICREDM FCPB will insert the TD or CD transaction details for PAR type of trans
15. the Integrated dashboard 4 2 5 1 5 2 5 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 Session Management For Single Sign On between Oracle
16. 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 sc
17. 41 N USERDEF FIE LDS UDF DATE NO FIELD VAL CSTM FUNCTIO 150 _2 _12 N_USERDEF_FIE LDS UDF_DATE NO FIELD VAL CSTM_FUNCTIO 150 _3 _13 N_USERDEF_FIE LDS UDF_DATE NO FIELD_VAL CSTM_FUNCTIO 150 4 14 N USERDEF FIE LDS UDF DATE NO FIELD VAL CSTM FUNCTIO 150 5 45 N USERDEF FIE LDS 2 22 Customer Account File Format The format of the customer account file is given below FIELD DESCRI LEN FCC COL LE TABLE Fcubs NAME PTION GTH DATO UMNS NG NAME Remarks RY TH T_EXT_CL External 10 YES CUST_NO 9 STTM_CU IENT_ID client id ST_ACCO UNT T BANK A Bank 16 YES CUST AC 20 STTM CU CCT ID account _NO ST ACCO id UNT T ACCT S Account 1 YES ACC STA 4 STTM CU TATUS status TUS ST ACCO UNT T ACCT S Account 5 YES ACCOUNT 6 STTM_CU UB TYPE sub type CALSS ST_ACCO UNT T_CURR Currency 3 YES CCY 3 STTM_CU ST_ACCO UNT T ACCT B Account 50 YES BRANCH 3 STTM_CU RANCH branch CODE ST ACCO UNT T_MICR MICR 24 NO NULL T ACCT T Account 5 YES ACCOUNT 1 STTM_CU S YP type TYPE ST ACCO Savings UNT U Current T SALES Sale 50 NO NULL REP ID represent ative id T OPPOR Sale 50 NO NULL TUNITY 1 oppurtinit D y id OPENING Opening YES AC_OPEN 8 STTM_CU _DATE date _DATE ST_ACCO UNT CLOSING_ Closing NO AC SET 8 STTM_CU DATE date CLOSE_D ST_ACCO 2 23
18. AILS AC CCY TDVW TD AC CCY VARCHAR2 3 203 _DETAILS REC STAT TDVW TD RECORD STAT VARCHAR2 1 206 _DETAILS TXN TYPE TDVW TD TRANSACTION TY VARCHAR2 9 207 _DETAILS PE TRAILER VARCHAR2 1 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 LED 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 s
19. B 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 Navigation 3 2 Tables Screen Name Navigation REF_CLIENT_SEG Master gt CRM Related gt Client Segment Client Segment REF_CLIENT_STATUS To be updated directly in the database REF_CLIENT_IT_TYPE Master gt CRM Related gt Client IT Type Client IT Type REF_CLIENT_CLASSIFICATION To be updated directly in the database REF_CLIENT_CATEGORY Master gt CRM Related gt Client Category Client Category PREF_LANG_CODE To be updated directly in the database 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 Non Mandatory for Demographics screen Fields which are mandatorily from FCUBS should be setup as Mandatory in FCPB via FAC screen for Demographi
20. 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 ORACLE Use NE Current Log FLEXCUBE Private Banking Home Customer Financial Planning Order Mgmt Txn Mgmt Master Reports Tools My Workspace Logout Customer gt Portfolio gt Maintenance Portfolio Summary Parke Davis i G fPortfalio RM Managed ED Name Description Type ccv Ins
21. CH the customer ANCH R ACQ_DATE Acquisition NO NULL Date BANKER Banker Code YES BANK COD STTM_BANK 4 E ADDR_LINE Mailing Address NO MSTM_CUST_AD 105 1 1 ADDRESS1 DRESS ADDR LINE Mailing Address NO MSTM CUST AD 105 2 18 FIELD DESCRIPTION MANDAT FCUBS TABLE NAME LE NAME ORY COLUMN NG NAME TH 2 2 ADDRESS2 DRESS ADDR_LINE Mailing Address NO MSTM_CUST_AD 105 3 3 ADDRESS3 DRESS STATE_MAI State of the NO NULL LING Mailing address COUNTRY_ Country of the NO COUNTRY CUST AD 3 MAILING mailing address DRESS ZIP_MAILIN Zip code of the NO NULL G mailing address ADDR_LINE Home Address YES ADDRESS_ STTM_CUSTOME 105 1 1 LINE1 R ADDR LINE Home Address YES ADDRESS STTM CUSTOME 105 2 2 LINE3 R ADDR LINE Home Address YES ADDRESS STTM CUSTOME 105 3 3 LINE2 R STATE MAI State of the NO NULL LING Home address COUNTRY Country of the YES COUNTRY STTM CUSTOME 3 MAILING Home address R ZIP MAILIN Zip code ofthe NO NULL G Home address ADDR LINE Work Address 1 NO E_ADDRES STTMS_CUST_P 105 1 S1 ROFESSIONAL ADDR LINE Work Address 2 NO E_ADDRES STTMS_CUST_P 105 2 S2 ROFESSIONAL ADDR LINE Work Address 3 NO E ADDRES STTMS CUST P 105 3 S3 ROFESSIONAL STATE MAI State of the NO NULL LING work address COUNTRY Country of the NO NULL MAILING work add
22. CY MAT Maturity Date Yes Could be MatDt for Booking OR New DATE date MatDt for Rollovers TENO Tenor Number 10 Yes R INT R Interest Number 23 6 NO Has been made non mandatory as ATE rate FCUBS reguest but Should be mandatory for Booking IntRate or Rollover IntRate for RNW tranType EXTE external Varchar 40 No Since FCUBS does not have any RNAL tran id separate Transactionld for TD and only TRAN uses TD Ref Number this should be ID sent as NULL BLANK TRAN Tran Varchar 1 Yes No need to send CLOSED TDs only _STAT Status Active TDs to be sent US SPRE Spreadin Number 24 6 Yes Only for Floating we have Spread AD BPS Fixed Deposit only has Customer Level Spread Bala to get back ACCO Product Varchar 5 Yes UNT altid CLAS S ROLL Rollover Varchar 1 Yes Mandatory for Can be P or P l OVER Type rollover as Rollover Type TYPE TransactionType ONLY INTER Interest Number 24 6 No This indicates the EST A Amt for Interest to be paid MOUN Rollover to customer on the T P type RolloverDate for a P type of Rollover Customer TD Interest Liguidation Penalty File Format The format of the customer TD interest liguidation penalty file is given below FIELD NAME DESCRIPTION MANDA REMARKS SAMPLE TORY VALUES 2 29 FIELD NAME DESCRIPTION MANDA REMARKS SAMPLE TORY VALUES TRAN
23. DATE UST AC COUNT VALUE value date DATE YES 8 Default DATE Value Application date AMOUN amount NUMB 24 YES ACY AVL 22 C T ER 6 BAL UST AC COUNT CCY ID Currency VARC 3 YES CCY 3 STTM C HAR UST AC COUNT MATURI Maturity DATE NO NULL TY DAT date E ACCT S Account VARC 5 YES ACCOUN 6 STTM C UB TYP sub type HAR T CLASS UST AC E COUNT INT RA interest NUMB 24 NO AMT RAT 22 ICTB TE rate ER 6 E DEVALS TENOR tenor NUMB 10 YES NULL ER ACCR Accrued NUMB 24 NO AMT 22 ICTB E This will NT interest ER 6 NTRIES be sum of total credit interest accrued for that product includes 2 25 FIELD DESCRIPT TYPE LE MAND FCC LE FCC FCC NAME ION NG ATORY LUMN NG Table Remarks TH TH name all credit formula associated to it LAST IN Last DATE NO LAST AC 8 ICTB A T ACCR interest CR DT CC PR DATE paid INTERE interest NUMB 24 NO AMT 22 ICTB E This will ST PAI paid ER 6 NTRIES be sum of D total credit interest liquidated for the product includes all credit formula associated to it LAST IN Last DATE NO LAST AC 8 ICTB A T DATE interest CR DT CC PR date HOLD A Hold NUMB 24 NO ACY BL 22 STTM C MOUNT amount ER 6 OCKED UST AC AMOUNT COUNT Customer Balance Loan File Format The format of the customer loan balance file is given below FIELD DESCRI
24. 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 5 3 5 4 5 5 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 SessionServicelnterface SessionService getSession This service is invoked over through Webservice over SOAP The following Webservice URL is exposed by FCDB for session validation https lt ipaddress gt lt port gt 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 Customer folio Account Summary Transaction and
25. 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 Table Name Name Column Name Data Type Field Length Position 2 10 Field Table Name Column Name Data Type Field Position Name Length CUSTNO ICVW_ACCRUAL_ CUST_NO VARCHAR2 9 1 DETAILS SHRTNM ICVW_ACCRUAL_ SHORT NAME VARCHAR2 20 10 DETAILS ICVW_ACCRUAL_ ACC 2 20 30 DETAILS ACCL ICVW_ACCRUAL_ ACCOUNT CLA VARCHAR2 6 50 DETAILS SS ACRAMT ICVW_ACCRUAL_ ACCRUED_AMT NUMBER 22 56 DETAILS ENTDT ICVW_ACCRUAL_ ENT_DT VARCHAR2 10 78 DETAILS CCY ICVW_ACCRUAL_ CCY VARCHAR2 88 DETAILS PROD ICVW_ACCRUAL_ PROD VARCHAR2 4 91 DETAILS HEADER VARCHAR2 1 TRAILER VARCHAR2 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 f
26. Home Branch a7 q Client IT Type Communication Mode q Client Category Client Classification q DOB lt q name Contact No 71 7 71 Introducer Relationship Client Currency 71 3777 Salutation s Client Segment CIF Status s Preferred Language Preferred Language for Statement 799 7 Client Entity Hobby Sports 8 7357 Nationality r Travel Pattern Marital Status Number of Children Occupation Client Background Business Background Initial Deposit Inward Funds From Bank Source of Wealth Annual Frequency ruka aaa Currencies Client Type Professional Investor External Reference Id q Address Mailing q Address Mailing Address Mailing q lt q Address Mailing q ress Mailing Address Mailing q lt Address Mailing 11771 7171711717 q Special Category Client maoa 7100110015017 71 q s Location Save Clear 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 Custom
27. MBER 22 215 INT_DETAILS LTPMTDT CLVW_LOAN_ LAST_PMT_DT VARCHAR2 10 237 INT_DETAILS ACTADD CLVW_LOAN_ ACCT_ADDRESS VARCHAR2 10 247 INT_DETAILS 2 15 Field Table Name Column Name Data Type Field Position Name Length HLDAMT CLVW LOAN HOLD AMOUNT NUMBER 22 257 INT DETAILS TRAILER VARCHAR2 1 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 Whena FCUBS customer segmentation status is updated to Upgraded as per the segmentation rules 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
28. OTIFICATIONS aaa e EE E A 2 5 2 5 DEFINING INTERFACE DETAILS FOR DATA HANDOFF nene entere enne 2 7 2 5 1 Term Deposit Maturity with Interest Liquidation eee 2 8 2 5 2 Daily Accrued Interest on Term Deposits esses eene nennen 2 9 2 5 3 Pen lty on Term Deposits ee o e OUR q anu a vara EAUS aaa an S AERES 2 11 2 5 4 Loan and Liability Information 2 13 2 9 9 Term DepOsit Rollover sie e RE CORR ERR P SEE ERE ETUR arus 2 16 2 5 6 Segmentation Status Information 2 16 3 ORACLE FCPB FCUBS INTERFACE 3 1 3 1 INTRODUETION Sp 3 1 3 2 DETAILS OF DATA RECEIVED FROM ORACLE FCUBS TO ORACLE FCPB eee 3 1 3 3 DEFINING INTERFACE DETAILS FROM FCUBS TO FCPB enne nennen 3 2 3 4 TRANSFERRING DATA USING XML FILES eeseeeeeeeeeeeeeee enne nennen a aS a enne 3 2 3 4 1 Creating Customer Dalai sc ee e e EE RE RU REPRISE fes 3 2 3 4 2 Modifying Customer Data 3 nie eg net eet e e d t rt eee cis 3 6 3 4 3 Client Suspended Statusi inerte e haqa e REED qk hats ER ese e E S e eis 3 8 3 4 4 Broker DGG iens nedau mete atquc iet usen nene eet 3 9 3 4 5 CASA Acco nt Creation uet DH Hp Det tut gee agus ce esie
29. Oracle FLEXCUBE Wealth Management Interface Oracle FLEXCUBE Universal Banking Release 12 0 1 13 0 April 2013 Oracle Part Number E51465 01 ORACLE FINANCIAL SERVICES Oracle FCPB Interface Table of Contents 1 ABOUT THIS UTE PUO 1 1 1 1 INTRODUCTION sa m Rr pne D EA S s BUR 1 1 12 AUDIENCE 11454 een nnn pee nn pem e Pp ea epe n Deb Sata te Sas ad nd Sade ERE 1 1 1 3 ORGANIZATION e ne con ner et pre rH PU 1 1 1 4 ACRONYMS AND ABBREVIATIONS uu 1 2 1 5 TERMINOEOGY u I I R A AE ett pt n ong conan eR pte pam ripa E REPRE 1 2 1 6 GLOSSARY OFICONS 5 iere trt ree Pp er bp eta Her pete ien epe rm ep IR EPOR 1 3 1 6 1 Conventions Used in this Manual nasus 1 3 2 ORACLEFCUBS FCPB INTERFACE iore enis io vo in bn opa on Eee pa ores oen e s 2 1 2 1 INTRODUCTIONS Sg n nuan aa eec teres kana daa de oc edes code ll eene deeds 2 1 2 1 1 Details Handed off from FCUBS to Oracle FCPB sese eene eene 2 1 2 2 DEFINING INTERFACE DETAILS FOR ORACLE FC PB 2 2 2 2 1 Defining Component Details tte e te t Sees es SE e t RH e ER sk kaka 2 4 2 3 FATCA INTERFACE BETWEEN ORACLE FCUBS AND FCPB eese enne enne 2 5 2 4 PROCESSING ONLINE N
30. 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 part of customer upgrade files FCUBS will not send any modification of accounts It s 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 3 6 2 3 6 3 Customer File Upload Segmentation Upgrade Once a customer gets upgraded as per the segmentation ru
31. REF NO Can be stored as Yes Ext Tran Idn or Ext Tran Ref CUSTOMER N Client id Yes CUSTOMER_NA ignored NO ME1 ACG Sub_portfolio_id Yes ACCOUNT_CLA Based on Account Yes SS class whether it is TD or call deposit instrument id and instrument type would be populated details in FCPB FS CASA Includ einholdings Rel2 1 section 8 TRN DT Tran Date Yes Interest Liquidation Date Penalty Charging Date LCY AMOUNT Amount Yes Interest Penalty AC NO Indicates Dr Cr NO AcctNumber n ignored AC CCY Amt YES RECORD STAT ignored NO TRANSACTION Tran Type Yes Interest TYPE Penalty 2 30 3 1 3 2 3 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 e Customer Creation Explains handing off of details related to Customer created in FCUBS to FCPB e CASA Account Creation Explains handing off of details related to CASA Account created in FCUBS to FCPB e Account Creation Explains handing off of details related to TD Accounts created in FCUBS to FCPB e Loans a
32. 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 Acguisition Cost columns with the deposit amount 8 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
33. TAILS NAME1 TD ACC TDVWS TD MAT ACC VARCHARZ 20 125 URITY DETAILS ACC CLA TDVWS TD MAT ACCOUNT VARCHAR2 6 145 SS URITY DETAILS CLASS TRN DT TDVWS TD MAT TRN DT DATE 10 151 URITY DETAILS LCY AMO TDVWS TD MAT AMOUNT NUMBER 22 161 UNT URITY DETAILS DR CRA TDVWS TD MAT AC NO VARCHAR2 20 183 CC URITY DETAILS AC CCY TDVWS TD MAT AC CCY VARCHAR2 3 203 URITY_DETAILS REC_STA TDVWS TD MAT RECORD_S VARCHAR2 1 206 T URITY_DETAILS TAT TXN TYP TDVWS TD MAT TRANSACTI VARCHAR2 9 207 E URITY DETAILS ON TYPE TRAILER VARCHAR2 1 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
34. TE 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 47 48 49 50 51 On rollover PMS PORTFOLIO HOLDING table would be updated for Market Value and Settled MktValue columns with the rollover amount But the TOTAL ACG 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 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 Roll
35. 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 ACCOPENDT TRAN TYPE to be Would be populated based on defaulted to NEW the xsd notification service received from FCUBS AMOUNT TDAMT AMT_CCY CLIENT_ID CUSTNO SUB_PORTFOLIO_ID ACC SUB_PORTFOLIO_ID ACC PMS PORTFOLIO HO LDING CLIENT ID PMS POR CUSTNO TFOLIO HOLDING INSTRUMENT CCY P CCY MS PORTFOLIO HOL DING TOTAL ACQ COST The TD deposit amount would TDAMT PMS PORTFOLIO H be populated OLDING 3 16 MARKET_VALUE PMS The TD deposit amount would TDAMT PORTFOLIO HOLDI be populated NG CLIENT ID PMS TD CUSTNO HOLDINGS DETAILS 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 lt Tddetails gt subnode TENOR DFTENOR TENOR DM to be Will be defaulted to D days defaulted to 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 Cla
36. UBS and FCPB e FCPB and FCUBS e FCPB and FCDB e 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 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 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 4 1 5 Chapter 2 Oracle FCUBS FCPB Interface deals with the maintenances required for the interface and its further processing Chapter3 Or
37. _AUTHORISED_SIGNATORY with Signatory_Type as G would be filled in e f Client IT Type is Individual then there is no concept of authorized signatory So there will be no entry in CRM_AUTHORISED_SIGNATORY table In FCUBS customers can also be created quickly using the STDCIFAD screen The Operational workflow is as follows e facustomer 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 e Hence you have to first navigate to the Modify Customer screen in FCUBS and enter the RM ID e Then you have to navigate to the Segment Association screen and fill in the other details like Segment Upgrade Status etc e 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 Custom
38. acle FCPB FCUBS Interface deals with the maintenances required in FCPB to exchange information between FCUBS and FCPB Chapter4 Oracle FCPB FCDB Interface deals with the maintenances required in FCPB to exchange information between FCPB and FCDB Chapter5 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 ac
39. action 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 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 Would be populated based defaulted to PAR 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 DA
40. ation Operation Service XSD Name Code CIF NOTIF CO CU QueryCustomer FCUBSCustome ST authorizatio STOMER_MOD rService ModifyCustomer n Notify MSG xsd modification Closure Broker NOTIF CO CU QueryCustomer FCUBSCustome ST creation STOMER_NEW rService NewCustomer Notify MSG xsd CASA NOTIFY AC B QuerycustAccount FCUBSAccServi TD AccStat account AL Details ce Notif xsd balance change Customer NOTIF PB CU Customer creation creation STOMER under Broker category Segmentati NOTIF_PB_CU CUSTSEGCD on code STOMER Net worth NOTIF PB CU NETWORTH Amount STOMER Net worth NOTIF PB CU NETWORTHCCY Currency STOMER customer NOTIF PB CU CUSTCCY Currency STOMER Segmentati NOTIF PB CU CUSTSEGSTAT on status STOMER US New tags CUSTSEGCD CUSTSEGSTATUS NETWORTH NETWORTHCCY and CUSTCCY will be available in the notification XSD 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 e TD maturity with interest liquidation e Daily accrued interest on TD e Penalty on TD e 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
41. counts 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 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 FCP
42. cs Similarly fields which are non mandatory or not available in FCUBS need to be setup as Non Mandatory 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 e Occupation e Communication Mode e Preferred Language for Statement e Introducer Name e Contact Number e Client Notes Zip e State e Tax ld e Gender e Client Classification e 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 ORACLE User Admin2 Current Login FLEXCUBE Private Banking Home EOD Master User Admin Authorization Reports My Workspace Logout Master Bank Related Field Access Controller ffield Access Controller Functions Names Demographics E Modifiable Mandatory Display First Name Middle Name Last Name Income Tax ID Occupation 1 1 71 71 71 Email Phone Home Phone Office 1 Mobile Fax lt Relationship Manager q
43. cy 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 amp 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 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 v
44. d 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 Processing Online Notifications FCUBS sends an online notification to Oracle FCDB at the following occasions e Creation of term deposit account in FCUBS e Premature withdrawal redemption before maturity date of the term deposit amount e Creation of customer accounts in FCUBS e Change in the balance in the customer accounts e Creation modification or closure of customer information e Creation of Brokers customer under the customer category Broker in FCUBS e Modification of term deposit account in FCUBS 2 5 e Premature withdrawal redemption before maturity date of the term deposit amount Online Notification for redemption through 1317 redemption screen is not supported e Rollover of Term deposit accou
45. elationship of NO NULL _REL the authorized signatory AUTH_SIGN Type of the NO NULL TYPE authorized signatory EXT PORT UBS NO PORTFOLI SETM PORTFOLI 16 FOLIO ID Investment O ID O MASTER portfolio ID REG COUN Registered NO R COUNTR STTMS CUST C 3 TRY ID country for the Y ORPORATE corporate INCORP C Incorporated NO INCORP C STTMS CUST C 3 OUNTRY ID country for the OUNTRY ORPORATE corporate CUSTOMER Status of the NO CIF STATU STTM CUSTOME 20 STATUS customer S R UDF NUM UDF NUM 1 NO FIELD VAL CSTM FUNCTIO 150 1 _1 N_USERDEF_FIE LDS UDF NUM UDF NUM 2 NO FIELD VAL CSTM FUNCTIO 150 2 2 N USERDEF FIE LDS UDF NUM UDF NUM 3 NO FIELD VAL CSTM FUNCTIO 150 3 3 N_USERDEF_FIE LDS UDF_NUM_ UDF NUM 4 NO FIELD_VAL CSTM_FUNCTIO 150 4 _4 N_USERDEF_FIE LDS 2 21 FIELD DESCRIPTION MANDAT FCUBS TABLE NAME LE NAME ORY COLUMN NG NAME TH UDF NUM UDF NUM 5 NO FIELD VAL CSTM FUNCTIO 150 5 5 N USERDEF FIE LDS UDF TXT 1 UDF TXT 1 NO FIELD VAL CSTM FUNCTIO 150 6 N USERDEF FIE LDS UDF TXT 2 UDF TXT 2 NO FIELD VAL CSTM FUNCTIO 150 _7 N_USERDEF_FIE LDS UDF TXT 3 UDF TXT 3 NO FIELD VAL CSTM_FUNCTIO 150 _8 N_USERDEF_FIE LDS UDF TXT 4 UDF TXT 4 NO FIELD_VAL CSTM_FUNCTIO 150 _9 N_USERDEF_FIE LDS UDF_TXT_5 UDF TXT 5 NO FIELD VAL CSTM_FUNCTIO 150 10 N USERDEF FIE LDS UDF DATE NO FIELD VAL CSTM FUNCTIO 150 4
46. entioned 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 lgnore ACCT ADDRESS and default Address from MST BANK ACCT ADDRESS 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 User HOHEAD Current Login 07 0 123 21PM Last Login 07 05 2012 2 27 PM ORACLE janking FLEXCUBE Private B m Home Customer Financial Planning Order Mgmt Txn Mgmt Reports Tools My Workspace Logout Customer Dashboard tate 2 655 775 00 175 000 00 4 2 655 775 00 Loan Portfolio value 2 480 775 00 otal INR 0 00 1 T Sum Insure d Pending Deals amono by instrument Group C EL
47. er 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 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 e CUSTSEGSTATUS e TXNSTAT e FROZEN Rules for updating the Client_Status in FCPB 10 e Will be marked CLOSED if TXNSTAT is C e Client status will be updated as Suspended in FCPB if CUSTSEGSTATUS is D or FROZEN is Y e Customer Status will be Active if TXNSTAT is or CUSTSEGSTATUS U or R or FROZEN is N e other status results in an updation failure and an the error message will be sent Not a valid Customer status A new column called Status Description is introduced in CRM CLIENT MASTER and it gets updated as mentioned below e f Segment Status in the Modification XML is Upgrade U in
48. er 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 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 ha
49. erface 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 Interface Definition New Enter Query Branch Code External System Interface Code Interface Type incoming FormatType Fixed Delimiting Character File Mask File Path Confirmation File CRC Required Data Log Required When Algorithm CommitFetch CRC File Mask d WR Mandatory ate Format Y MMDD 1 lanua CRC File Path Trigger Manual No OfExecutions Day Confirmation File Mask Duplication File Check Confirmation File Path Reguired For Current Date Justification Padding Character Incoming Date Date Function Id Number Number Processed File Mask Text Text Default Action New On Override Reject Frequency T Daily Pre Message a Lt Outgoing Interface Week Day Post Message Suppress Start Month Pre Message AUDF Reference Dates PostMessage AUDF Incoming File Mask Last Run Date Log Output Next Run Date Parallel Process Parallel Process Required Parallel Process No Of Records No Of Parallel Process Component Details Incoming File Names Input By Authorized By Modification H Authorized Date Time Date Time Number open You need to define the interface details External System Specify the code that identifies the external
50. gment 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 ofthese roles would be identical to the Segment 3 33 71 72 73 74 75 76 77 78 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 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 TD Rollover Only Rollover Types of Principal or Principal Interest would be supported in this release Special Amount Rollovers would not be supported Recurring Deposit TDs In this release Top Up event for Recurring Deposits would not be supported by FCPB Recurring Deposits expects that an automatic to
51. gop EQUITY Fined maturity pian E 48 175 00 1 78 2 655 775 00 2 655 775 00 E E rd Total INR 2 703 950 00 Interaction System Alerts Task Details Date Mode 2 NO PENDING TASK FOUND Corpus 3 28 3 6 Segment Upqrade Downqrade 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
52. 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 Table Name Column Data Type Field Position Name Name Length HEADER VARCHAR2 3 1 AC REF TDVWS TD MAT AC ENTRY NUMBER 10 1 NO URITY DETAILS SR NO CUST NO TDVWS TD MAT CUSTOMER VARCHAR2 9 11 URITY DETAILS NO CUST NA TDVWS TD MAT CUSTOMER VARCHAR2 105 20 ME URITY DE
53. here are few DAY 0 parameters maintained for this SSO integration 5 2 PARAMETER NAME PARAMETER VALUES lt identity gt lt usertype gt PWM EXTERNAL URL FCPB Dashboard URL exposed by FCPB lt identity gt lt usertype gt PWM REMOTE PORT FCDB server port This is sent for authentication lt identity gt lt usertype gt PWM REMOTE ADDRESS FCDB server IP address This is sent for authentication lt identity gt lt usertype gt WEALTH DIMENTIONS ID List of dimension s id which configured at entity and user type level lt identity gt W EALTH 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 1 Function ID List 6 Screen Glossary 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 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 Maha
54. ia 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 ORACLE User HOHEAD Current Login 07 C 3 21PM Last Login 07 05 2012 2 27 PM FLEXCUBE Private Banking Home Customer Financial Planning Order Mgmt Txn Mgmt Reports Tools My Workspace Logout Customer gt Portfolio gt Analysis Category Instrument Type Portfolio Type Overall E Balance Sheet gt instrument Type Sandy Kumar fum Instrument Type Buy Cost Market Value of Total Profit Loss Profit Loss Pie Chart 5 Corpus 1 186 710 00 1 186 710 00 94 93 0 00 amp 0 00 MutualFund 63 290 00 63 415 00 5 07 125 00 0 20 Total INR 1 250 000 00 1 250 125 00 100 0096 125 00 A 0 01 SSS Name CCY Buy Price Units Buy Cost Market Price Market Value eofTotal Profit Loss Profit Loss Liquid ME INR 54 125 6 750 ss 6 875 10 84 125 185 Liquid MF INR 55 1 028 56 540 55 56 540 89 16 0 0 00 Total INR 63 290 63 415 100 125 0 2 Note Fund sub constituent information can be seen by clicking on the instrument name hyperlink by clicking on the Market Value hyperlink the source details are provided Industry Market Capitalization analysis is only for Equity and not other asset classes The investment portfolio of the customer is then displayed in the accounts summary section in
55. lay 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 ofthe 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 hand
56. les 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 Subseguent 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 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 Accou
57. ly as TERM RATE UDE for FCUBS and FCPB integration 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 Recurri
58. mponent details for both handoff and upload Click Component Details button on the Interface Definition screen Payment Gateway SEPA Outgoing File Details File Name File Transfer Status File Reference File Path Failure Reason Advanced Search Records esee 15 zi File Reference File Name File Path File Transfer Status File Transfer Status U Pending C Complete F Failure R Resend 2 4 2 3 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 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 relatedto FATCA e Information available in the FATCA related fields e Any fiel
59. nd 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 Liguidation 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 3 4 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 Ac
60. ng 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 1 4 1 1 4 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 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 dependen
61. nholdi ACCOUNT CLASS 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 pre mature 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 NAME 1 Ignored Sub portfolio id Based on Account class whether it is TD or call deposit instrument id and ACCOUNT CLASS 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 m
62. nsion Schema is a term used for the separate database schema as deployed by Schema Oracle FLEXCUBE Direct Banking to allow IMPLEMENTERS to extend the Oracle FLEXCUBE Direct Banking application as per their needs 1 6 Glossary of Icons This user manual may refer to all or some of the following icons Icons Function E Exit Help Add Delete View 1 6 1 Conventions Used in this Manual Important information is preceded with the 9 symbol 2 Oracle FCUBS FCPB Interface 24 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 to day 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
63. nt in FCUBS e Creation of Recurring deposit account in FCUBS e Customer creation under BROKER category e Amendment of the segmentation code net worth amount net worth currency and customer currency of customer Segmentation e Amendment of the segmentation status from Upgraded to Downgraded and Re Upgraded 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 Operation Service XSD Name Code TD account NOTIF TD TDA QuerycustAccount FCUBSAccServi TD NewAccount creation CC_NEW Details ce Notify MSG xsd TD Account NOTIF TDMOD GuerycustAccount FCUBSAccServi TD NewAccount modification PB Details ce Notify MSG xsd TD NOTIF ICRED QueryTDRedempti FCUBSAccServi IC premature M on ce QueryTDRedem withdrawal Res Full MSG xsd IC QueryTDRedem Reg IO MSG xsd TD rollover NOTIF TD RO QueryTDRollover FCUBSTDServi ST LLOVER ce QueryTDRollover Req lO MSG xsd ST QueryTDRollover Res Full MSG xsd CASA NOTIF CA CU QuerycustAccount FCUBSAccServi CA account STACC NEW Details ce NewCustomerAc creation count Notify MSG xsd 2 6 Instance Notific
64. nts 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 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 disp
65. off 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 3 7 Once a customer gets downgraded as per the segmentation rules
66. ollowing table Field Value Interface Code STOIMDTL Interface Type Outgoing From System FCUBS To System FCPB Dateformat YYYYMMDD 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 Column Name Data Type Field Position Name Length HEADER VARCHAR2 1 AC REF N TDVW TD AC ENTRY SR NO NUMBER 10 1 _DETAILS CUST_NO TDVW_TD CUSTOMER NO VARCHAR2 9 11 _DETAILS CUST NAM TDVW TD CUSTOMER NAME VARCHAR2 105 20 E DETAILS 1 TD ACC TDVW TD ACC VARCHAR2 20 125 DETAILS ACC CLAS TDVW TD ACCOUNT CLASS VARCHAR2 6 145 S DETAILS 2 12 Field Name Table Column Name Data Type Field Position Name Length TRN_DT TDVW TD TRN DT DATE 10 151 DETAILS LCY AMOU TDVW TD AMOUNT NUMBER 22 161 NT DETAILS DR CR AC TDVW TD AC NO VARCHAR2 20 183 C DET
67. otification 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 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 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 Frozen 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 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 w
68. ould 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 First Name FULLNAME if FULLNAME not MST BROKER available then FIRSTNAME Broker code Broker code CUSTNO MST BROKER This tag would help in CCATEGORY In case of broker identifying if the CIF it would be broker or B Notification is of broker or not Address1 Address Line 1 ADDRLN1 MST BROKER Address2 Address Line 2 ADDRLN2 MST BROKER Address3 Address Line 3 ADDRLN3 MST BROKER 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 21 22 23 24 The Frequency of this notification would be one time migration and daily incremental online 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 CA New Customer Account Notify MSG service would be used by FCUBS to hand off the account details to FCPB The CASA Account would be
69. over TD would be a B buy 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 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 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 As part of the EOD after the Rollover none of the MAT INT records for the Rolled over TD are available in the UBS File FCPB Column Name Description FCUBS Element Name as per the XML Updation in PMS TRANSACTION Indicating RENEWAL DATE TRAN DATE Rollover Date TRAN_TYPE to be u defaulted to RNW Indicating ROLLOVER_AMT AMOUNT Rollover Amount VALUE_DATE Indicating Rollover Date AMT_CCY Rollover CCY CCY CLIENT_ID CUST_NO INTEREST_AMOUNT TP to create a ACCR_INT_BAL Txn INT based on this value 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
70. p 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 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 TD with Interest Liguidation to TD A C In this release there is a limitation to support TDs where Interest Liguidation is to TD Account instead of CASA Account Such TDs are either capitalized non capitalized TD or Autorollover Manual Rollover P 1 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 Liguidated Interest Accrued since last liguidation However in FCPB since Partial Full uplift is allowed only to the extent of Balance Outstanding Principal such withdrawals would get rejected in FCPB TD Modification FCPB would be referring to the UDE named TERM to pick up modified Interest Rate in TD Modification Hence in IC product preference screen ICDPRMNT Main Interest Rate UDE field should be maintained mandatori
71. rashira 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 Co
72. reen 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 ofthese 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 Se
73. ress ZIP MAILIN Zip code ofthe NO NULL 2 19 FIELD DESCRIPTION MANDAT FCUBS TABLE NAME LE NAME ORY COLUMN NG NAME TH G work address FAX Fax Number NO FAX_NUMB STTM_CUSTOME 105 ER R NATIONALI Nationality YES NATIONALI STTM_CUSTOME 3 TY TY R LANGUAGE Preferred YES LANGUAGE STTM_CUSTOME 3 language of the R customer CCY_ID Customer YES PORTFOLI SETM_PORTFOLI 3 Currency CCY CO MASTER DE PREF COM Preferable YES DEFAULT STTM CUSTOME 12 M MODE communication MEDIA R mode CLIENT CA Client category YES CUSTOME STTM CUSTOME 10 TEGORY R CATEGO R RY CLIENT CL Client YES CUST CLA STTM CUSTOME 20 ASSIFICATI Classification SSIFICATIO R ON N MINOR FLA Flag indicating YES MINOR STTM CUST PE 1 G if minor RSONAL AUTH_SIGN First name of NO LEGAL GU STTM CUST PE 105 _FNAME the authorized ARDIAN RSONAL signatory AUTH_SIGN Last name of NO NULL _LNAME the authorized signatory AUTH_SIGN Date of birthof NO NULL _DOB the authorized signatory AUTH_SIGN Mobile number NO NULL _MOBILE of the authorized signatory AUTH_SIGN Home number NO NULL 2 20 FIELD DESCRIPTION MANDAT FCUBS TABLE NAME LE NAME ORY COLUMN NG NAME TH _HOME of the authorized signatory AUTH_SIGN Tax identified of NO NULL _TAX ID the authorized signatory AUTH_SIGN R
74. rporation 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
75. s permitted in FCPB for active customers like placing of orders and transactions etc Assumptions 1 Itis 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 e f 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 e Hence the user has to first go to the Modify Customer screen in UBS and enter the RM Id e Then go to the Segment Association screen and fill in the other details like Segment Upgrade Status etc e Only if the above
76. 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 After a NEW transaction is received on Booking a TD with a particular TD reference number 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 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 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 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 If default Portfolio is not
77. ss and the FIELD VALUE for this UDF will contain the Spread User HOHEADRMONE Current Login 07 05 2012 2 21 PM Home Customer Financial Planning Order Mgmt Txn Mgmt Master Reports Tools My Workspace Logout Customer gt Portfolio gt Maintenance Portfolio Summary sdasdf Portfolio RM Managed Name Descripti Type ccv Amount f Total Instrument Type Amount C Heldaway eld 0 00 0 E CASA 7 493 Ti C RM Managed RN 0 Timepep Self Managed Self Man 0 0 00 Total 86 896 33 100 00 Total GBP 86 896 33 100 View Portfolio Modify Delete Add Portfolio e kindad ws Qasi Last Transaction Date in the Portfolio 31 12 2012 Time Deposit RM Managed Accrued Interest Account Type BASNE Paid Dats Quick Launch Term Deposit GBP Term Deposit GBP Term Deposit GBP Term Deposit GBP Term Deposit GBP Term Deposit GBP Term Deposit GBP Term Deposit JPY Term Deposit USD Term Deposit USD Term Deposit USD Term Deposit USD Term Deposit USD 10 6 Total GBP 93 894 85 495 05 2 697 4 g i 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
78. 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 unigue code that identifies the interface between the above external system and FCUBS Interface Type Select the interface type from the following options e Incoming Select this for interfaces that upload data into FCUBS e Outgoing Select this for interfaces that facilitate handoff of data from FCUBS 2 3 2 2 1 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 e Fixed Select this format type if the interface data is within fixed width e 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 Defining Component Details As part of interface definition you need to capture specific co
79. t 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 11 12 The Frequency of this notification would be one time migration and daily incremental online 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 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 13 14 15 16 The Freguency of this notification would be one time migration and daily incremental online 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 This n
80. the above files are given below Customer File Format The format of the customer file is given below FIELD DESCRIPTION MANDAT FCUBS TABLE NAME LE NAME ORY COLUMN NG NAME TH EXTERNAL External client YES EXT_REF_ STTM CUSTOME 20 1 id customer NO R SALUTATIO Salutation YES CUSTOME STTM CUST PE 30 N R PREFIX RSONAL FIRST_NAM First Name YES FIRST NA STTM_CUST_PE 105 E ME RSONAL MIDDLE_NA Middle Name NO MIDDLE N STTM_CUST_PE 105 ME AME RSONAL 2 17 FIELD DESCRIPTION MANDAT FCUBS TABLE NAME LE NAME ORY COLUMN NG NAME TH LAST NAM Last Name NO LAST NAM STTM CUST PE 105 E E RSONAL PHONE HO Home Phone NO TELEPHON STTM CUST PE 105 ME E RSONAL PHONE MO Mobile Phone NO MOBILE N STTM CUST PE 22 BILE UMBER RSONAL PHONE W Work Phone NO E TELEPH STTM CUST PR 10 ORK ONE OFESSIONAL EMAIL Email NO E MAIL STTM CUST PE 255 RSONAL GENDER Gender M YES SEX STTM CUST PE 1 Male F RSONAL Female DOB Date OF Birth NO DATE OF STTM CUST PE 10 BIRTH RSONAL TAX ID Income Tax ID YES TAX ID STTM CORP DI 105 RECTORS CLIENT SE Client Segment YES CUST SEG STTM CUSTOME G MENT CO R DE OCCUPATI Occupation YES DESIGNATI STTMS CUST P 105 ON ON ROFESSIONAL CLIENT TY Client IT type YES CUSTOME CUSTOME 1 PE R TYPE R HOME BRA Branch code of YES LOCAL BR STTM CUSTOME N
81. 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 e 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 e Customer TD Booked 8 Rollover File FCUBS will generate outgoing files for the TD accounts which underwent the following changes as of segmentation date gt Booked gt Rollover gt Partial Redemption The following details are sent to the FCPB gt Details of all open TD accounts gt Partial redeemed TD details gt TD renewal details e 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 gt Interest liquidation gt Penalty The following TD details are sent to FCPB gt TD with interest liquidation gt TD with penalty entries for partial redemption 2 5 6 1 Segment Upgrade File Formats The formats of
82. tors etc Term Definition Business A Business Service or a Transaction Service is a coarse grained component that delivers a Service particular service contract The Service Interfaces and that make up the contract are each 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 A Service Implementation is a concrete implementation of a Service Interface Implement ation or Service Endpoint Service A Service Interface is a cohesive set of Service Methods that are grouped together in the Interface 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 Service A Service Method takes the form of a Java method implemented by the Service Method 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 The Exte
83. trument Type of Total C Heldaway Heldaway INR CASA 94 C RM Managed RM Managed INR 2 578 067 30 TimeDep C Self Managed Self Managed INR 0 00 Total INR 2 578 067 31 Total INR 2 578 067 31 100 View Portfolio Modify Delete Add Portfolio Last Transaction Date in the Portfolio 05 12 2012 KEEGUREST RH Managed Account Type Afc No ccv Available Balance Hold Amount Total Balance As on Date ls Total INR 2 426 277 63 0 2 426 277 63 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 Acg 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 Currency of the CASA Account CCY
84. turity Date e LCY AM Amount Amount Dividend Mat Principal new OUNT Interest field to be introduced AC NO Indicates Dr Cr Indicates Dr Cr ignored ignored AcctNumber n AcctNumber n ignored ignored AC CCY Amt ccy Amt ccy Instrumen Currency t Ccy RECORD ignored ignored ignored Account status STAT TRANSA Tran Type should Tran Type should ignored ignored CTION T be defaulted to MAT be defaulted to YPE INT PEN 3 25 3 5 2 Additional Attributes BIDASK_IND field would be defaulted as S TOTAL A BALANCE field CQ COS would be made as T Zero MARKET would be made as Zero FCUBS system sends the TD maturity related details as a part oftheir 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 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 Fields in File Format Insertion in Respective Tables PMS PORTFOLIO HOLDINGS PMS TD HOLDING DETAILS CUST NO Client Id Client Id SHORT NAME Ignored ignored Sub portfolio id Sub Portfolio Id Based on Account class whether it is TD or call deposit instrument id and instrument type would be populated details in FCPB FS CASA Includei
85. ty 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 Insertion in Respective tables the file format PMS TRANSACTIO PMS_TRANSACTI PMS PO PMS TD HOLDI N for MAT txn ON for INT txn or RTFOLIO NG DETAILS PEN txn HOLDIN GS TRAN Can be stored as Can be stored as Ext Tran Idn or Ext Tran Ref REF NO Ext Tran Idn or Ext Tran Ref CUSTOM Client id Client id Client id Client id ER NO 3 24 CUSTOM ignored ignored ignored ignored ER_NAM E1 ACG Sub portfolio id Sub portfolio id Sub portf Sub portfolio id olio id ACCOUN Based on Account Based on Account Basedon Prod id T CLASS class whether it is class whether it is Account TD or call deposit TD or call deposit class whe instrument id and instrument id and ther it is instrument type instrument type TD or call would be populated would be deposit details in populated details instrument FCPB FS CASA In in id and cludeinholdings Rel2 FCPB FS CASA In instrument 1 section 8 cludeinholdings Rel type 2 1 section 8 would be populated details in FCPB FS _ CASA In cludeinhol dings Rel 2 1 section 8 TRN DT Tran Date Tran Date Value Dat Ma
86. ub screen you need to maintain the following details Field Table Name Column Name Data Type Field Position Name Length HEADER VARCHAR2 3 1 CUSTID CLVW_LOAN_ CUSTOMER ID VARCHAR2 35 1 INT_DETAILS ACCNO CLVW LOAN ACCOUNT NUM VARCHAR2 35 2 INT DETAILS BER PRODAC CLVW LOAN DR PROD AC VARCHAR2 20 36 INT DETAILS PROD CLVW LOAN PRODUCT COD VARCHAR2 4 56 2 14 Field Table Name Column Name Data Type Field Position Name Length INT DETAILS E BOOKDT CLVW LOAN BOOK DATE VARCHAR2 10 60 INT DETAILS VALDT CLVW LOAN VALUE DATE VARCHAR2 10 70 INT DETAILS PRNOUT CLVW LOAN PRNOUTSTANDI NUMBER 22 80 AMT INT DETAILS NG CCY CLVW LOAN CURRENCY VARCHAR2 102 INT_DETAILS MATDT CLVW_LOAN_ MATURITY_DAT VARCHAR2 10 105 INT DETAILS E ACCSTAT CLVW LOAN ACCOUNT STAT VARCHAR2 1 115 INT DETAILS US ACSUBTY CLVW LOAN ACCT SUB VARCHAR2 10 116 P INT DETAILS E ACCBRN CLVW LOAN DR ACC BRN VARCHAR2 126 INT_DETAILS MICR CLVW_LOAN_ MICR VARCHAR2 10 129 INT_DETAILS RSLDVAL CLVW_LOAN_ RESOLVED_VAL NUMBER 22 139 INT_DETAILS UE TENOR CLVW_LOAN_ TENOR NUMBER 22 161 INT_DETAILS ACCRAM CLVW_LOAN_ ACCRAMT NUMBER 22 183 T INT_DETAILS LTINACD CLVW LOAN LAST_INT_ACCR VARCHAR2 10 205 T INT DETAILS DATE AMTSTLD CLVW_LOAN_ AMTSTLD NU
87. ueteres 3 9 3 4 6 Customer CASA Account Balances Notification eese 3 12 3 4 7 CASA Closure ModifiCdtiOf ss cise ite e e e E d pH eov 3 13 3 4 8 TD Account Creation dedu itg ducet et nn Det 3 15 3 4 9 TD Modific tion te E a E RHET pets 3 18 3 4 10 TD Pre Mature Withdrawal cesses enne 3 19 3 4 11 TIDROUOVER to rie S renonce 3 20 3 5 DATA TRANSFER USING FILE UPLOAD MECHANISM nennen nennen entente entente innen enne 3 24 3 5 1 TD Maturity along with Interest Liquidation eese rentrer en 3 24 3 32 Daily Accrued Interest n TD iiu anuo een PERI REL aias EP ui 3 26 3 5 3 Penalty on TD applicable in case of pre mature partial withdrawal and pre mature complete withdrawal icit cte tei a heri etc or ORE E HE E desee cor Reds 3 27 3 5 4 Loan and Liability Information eee eee esee eene enne nennen trennen eene ene 3 27 3 6 SEGMENT UPGRADE DOWNGRADE INTERFACES n nnne tentent 3 29 3 6 1 Customer File Upload Segmentation Upgrade eene rennen 3 30 3 6 2 Customer Account File Upload Segmentation Upgrade eene 3 30 3 6 3 Customer Balances File Upload Segmentation Upgrade eene 3 30 3 6 4 Customer TD Deals File Upload Segmentation Upgrade eee 3 31 3 6 5 Customer Online Notification Segmentation
88. ve 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 Updates based on Client IT Type e 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 e If Client IT Type is Minor Y then FCUBS provides the Guardian details In that case first name in CRM

Oracle FLEXCUBE Wealth Management Interface User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents