Oracle Banking Platform Functional Upgrade Guide Release 2.6.0.0.0 E87094-01 May 2017
Oracle Banking Platform Functional Upgrade Guide, Release 2.6.0.0.0 E87094-01 Copyright 2011, 2017, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. 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.
Contents Preface... v Audience... Documentation Accessibility... Related Documents... Conventions... v v v vi 1 Overview 2 Upgrade Impacts 2.1 Origination... 2-1 2.2 Party... 2-3 2.2.1 Customer Onboarding (Fast Path: PI048)... 2-3 2.2.2 Manage Risk score (Credit Metrics) (Fast Path: PI026)... 2-3 2.2.3 Single Party View - Risk Indicators... 2-3 2.2.4 Single Party View - Legal Reporting... 2-3 2.3... 2-4 2.3.1 Define Credit Policy Fast Path (Fast Path: PM009)... 2-4 2.3.2 Define Loan Product... 2-4 2.3.3 Define TD Offer... 2-5 2.3.4 Define TD Product... 2-6 2.3.5 Define CASA Product... 2-6 2.3.6 Define CASA Offer... 2-6 2.3.7 Define Loan Offer... 2-6 2.3.8 Define Loan Bank Policy... 2-7 2.3.9 Define Statement Policy... 2-8 2.3.10 Define Domain Category Settlement Mode... 2-8 2.3.11 Define Product Settlement Mode... 2-8 2.3.12 Define CASA Bank Policy... 2-9 2.3.13 Define Product Group... 2-9 2.3.14 Define Insurance Product... 2-10 2.3.15 Define Insurance Offer... 2-10 2.3.16 Insurance... 2-14 iii
List of Tables 2 1 Customer Onboarding - Data Elements... 2-3 2 2 Manage Risk scores - Data Elements... 2-3 2 3 Single Party View - Risk indicators - Data Elements... 2-3 2 4 Single Party View - Legal Reporting - Data Elements... 2-4 2 5 Define Credit Policy Fast Path - Data Elements... 2-4 2 6 Define Loan Product- Data Elements... 2-4 2 7 Define TD offer - Data Elements... 2-5 2 8 Define TD Product - Data Elements... 2-6 2 9 Define CASA Product - Data Elements... 2-6 2 10 Define CASA Offer - Data Elements... 2-6 2 11 Define Loan Offer - Data Elements... 2-7 2 12 Define Loan Bank Policy - Data Elements... 2-8 2 13 Define Statement Policy- Data Elements... 2-8 2 14 Define Domain Category Settlement Mode- Data Elements... 2-8 2 15 Define Product Settlement Mode- Data Elements... 2-9 2 16 Define CASA Bank Policy- Data Elements... 2-9 2 17 Define Product Group - Data Elements... 2-9 2 18 Define Insurance Product - Data Elements... 2-10 2 19 Define Insurance Offer - Data Elements... 2-11 2 20 Movement of Insurance screens... 2-14 iv
Preface Oracle Banking is a one-stop solution for a bank for its core banking operations, across retail and business banking operations. It is designed to help banks respond strategically to today's business challenges, while also transforming their business models and processes to reduce operating costs and improve productivity across both front and back offices. Oracle Banking provides a unified yet scalable IT solution for a bank to manage its data and end-to-end business operations with an enriched user experience. It is a composed set of different modules, wherein each module is serviced by a set of services and other subsystems. This guide covers the impacts of upgrading the functionalities of Oracle Banking from Release 2.5.0.2.0 to Release 2.6.0.0.0. This preface contains the following topics: Audience Documentation Accessibility Related Documents Conventions Audience This guide is intended for the users of Oracle Banking. Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc. Access to Oracle Support Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired. Related Documents For more information, see the following documentation: v
For installation and configuration information, see the Oracle Banking Installation Guide - Silent Installation. For a comprehensive overview of security for Oracle Banking, see the Oracle Banking Security Guide. For the complete list of Oracle Banking licensed products and the Third Party licenses included with the license, see the Oracle Banking Licensing Guide. For information related to setting up a bank or a branch, and other operational and administrative functions, see the Oracle Banking Administrator s Guide. For information related to customization and extension of Oracle Banking, see the Oracle Banking Extensibility Guide. For information on the functionality and features of the Oracle Banking product licenses, see the respective Oracle Banking Functional Overview documents. Conventions The following text conventions are used in this document: Convention boldface italic monospace Meaning Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. vi
1 1Overview This guide covers the functional impacts of upgrading Oracle Banking from Release 2.5.0.2.0 to Release 2.6.0.0.0. If a functionality has an impact while upgrading from the previous version, the impact and related maintenances are included in this guide. Overview 1-1
1-2 Oracle Banking Platform Functional Upgrade Guide
2 2Upgrade Impacts This chapter describes the upgrade impacts for different screens of Oracle Banking. 2.1 Origination Following are the functionalities which are added in release Release 2.6.0.0.0 which can have impact during. Earlier for Amend request, system would display all the facilities of the party in the landing page irrespective whether the logged in user has the access to the facility business unit or not. Due to this issue there is a possibility that facility and underlying accounts can be part of different business units. The validation to resolve this problem in the landing page is being fixed as part of Release 2.6.0.0.0. However, for the existing facilities and accounts which has the above discrepancy needs to be corrected. Whenever the existing or new party is being added in the Product details step, the label name for party type Individual, Trust and Organization was shown as First. As part of Release 2.6.0.0.0, the label name for party type Individual, Trust and Organization is shown as First, Trust Legal and Legal respectively. Proposed Repayment Schedule column is being introduced in Internal Refinance panel. In case of Partial Closure, system will generate the proposed repayment schedule for the outstanding amount and display. The existing in-flight applications for which the product details step is crossed, system will not show the proposed repayment schedule. The existing behavior to renew the revolving facilities is supported from current processing date. As part of Release 2.6.0.0.0, the enhancement is made to support the renewal from any date between Current Process Date to Original Expiry Date of the facility. The party step has been enhanced based on the requirements to party module. The party task-flows consumed in origination will be impacted. The changes to party step are as follows: Capability to display the details all pending applications that is, Amend, Review & Renew and IPA Submissions. Enhancement to upload documents from the identification grid. Party Employment is enhanced when Employment type is set to Others and Status is Home Duties, Pensioner, Retired, Student, Superannuation or Unemployed. Enhancements to party address Upgrade Impacts 2-1
Origination The enhancement is to display the collateral description for the supporting collaterals linked or added to the guarantee instead of collateral type and sub type. This will help the banker uniquely identify the supporting collaterals. The existing in-flight submissions opted for edit submission will display the collateral description instead of collateral type and sub type. Earlier Negotiated Amount would change when user moves back to Funds table from subsequent stage in case of additional fees being inclusive. To cater this issue and enhancement is made in funding step to include the negotiation task flow of pricing in Funds table and display the net fee amount in Negotiated Amount. Capability to add verification types manually in the capture application process. The verification types added in capture application process will be available in the verification task for verification. Create work activity will have more options to route the work activity items post upgrade and will not impact the in-progress work activities due to this enhancement. As currently financials are captured for an employment. For a party, multiple financials are available across employments. For all these cases, migration impact of de-linking financial capture from employment to be handled as follows: Salaried, Self-employed and Others: Multiple financial records for a party across asset, liabilities, income and expense are to be added up. Adding up is done at a parameter level. Values of same parameter across multiple employments are to be added up. In case the parameter is shared across multiple employments then the system should not add the parameter multiple times. Self-employed: Multiple financial records for a party across balance sheet and profit and loss statements are to be added up as follows: If for a statement (balance sheet or profit and loss) statement start and end dates match and also statement type and classification match then a union of parameters is to be taken and values of common parameters are to be added up. This is applicable for audited, unaudited and projected statements. Verification stage Post upgrade the look and feel of the Verification stage details appears different due to the redesigning of the screen. All the in-progress verification tasks will not support verification category wise routing functionality. It will be applicable only for the new verification tasks created. Offer letters, Decline letters and IPA Term sheets All the in-progress tasks for these three will be as per existing functionality post upgrade. All the new tasks which are created post upgrade will support this STP functionality (if set up is done). Generation and acceptance of Rate Lock Agreement All the in-progress structure solution tasks will be as per existing functionality post upgrade. All the new structure solution tasks which are created post upgrade will support the functionality (if set up is done). 2-2 Oracle Banking Platform Functional Upgrade Guide
Party Home and Content Insurance and Landlord Insurance are new products introduced in Origination. The suitable product set up needs to be done in the application to enable the bankers to originate the product. The Process Tracker functionality is phased out from this release. Hence the Process Tracker (OR300) screen and Process Tracker link from Application Tracker will not be available post the upgrade. 2.2 Party This section describes the upgrade impacts of functionalities in Party. 2.2.1 Customer Onboarding (Fast Path: PI048) Table 2 1 Other Tax residency Details Economic Cost Computation Date A new section for other tax residency has been introduced. There is no impact on upgrade as all these fields are new and the data capture is non-mandatory. Customer Onboarding - Data Elements No impact Modified No impact Field is non-mandatory, hence no impact during upgrade 2.2.2 Manage Risk score (Credit Metrics) (Fast Path: PI026) The new Agency field introduced is mandatory. Table 2 2 Manage Risk scores - Data Elements Agency The name of the agency has to captured in the next update 2.2.3 Single Party View - Risk Indicators The new field has been introduced in Risk Indicators. This will not have any impact in upgrade as it is a non-mandatory field. Table 2 3 -Risk Indicator Single Party View - Risk indicators - Data Elements No Impact 2.2.4 Single Party View - Legal Reporting The new additional details are introduced for CRS/FATCA. This will not have any impact in upgrade as these are non-mandatory fields. Upgrade Impacts 2-3
Table 2 4 Single Party View - Legal Reporting - Data Elements Other Details No Impact FATCA Other Details CRS No Impact 2.3 This section describes the upgrade impacts of functionalities in Product Manufacturing. 2.3.1 Define Credit Policy Fast Path (Fast Path: PM009) Table 2 5 Define Credit Policy Fast Path - Data Elements Collateral Required This field is defaulted to Not Required. 2.3.2 Define Loan Product Table 2 6 Fee Treatment Preferences - Additional events has been included Fee Treatment for Bill Fee Treatment included for Delinquency Tracking Days Before Maturity Roll Over Maximum Maturity Roll Over Period (in Months) Maximum Number of Maturity Roll Over Is Billing Required Define Loan Product- Data Elements Modified No Impact. In the Fee Treatment for all the new events, the default value is captured as "Bill". If in the field Fee Treatment, if the option is selected as Bill, then in the upgrade impact this field will be defaulted with value as "Payment due Immediately". This should be defaulted to "Yes". By default the value will be 0. By default the value will be 0. This can also be discussed with the bank and can be modified to any other fee treatment. By default the value will be 0. By default this will be unchecked. 2-4 Oracle Banking Platform Functional Upgrade Guide
Table 2 6 Is Pyramiding of late fees Applicable Fee Amortization Method Fee Amortization Frequency Accelerated Payment Allowed For Deferment Allowed For Is Delinquency Tracking Required Modified Modified By default this will be unchecked. No Impact No Impact This value will be defaulted to "Variable". This value will be defaulted to "Variable". By default this will be unchecked. Collected Balance Deleted A new field Interest Computation Balance method is introduced in the Control Parameter panel. This is a drop-down field. It has values as (a) Collected Balance (b) Book balance. For upgrade Impact, if the field Collected Balance is selected, then the value will be defaulted as "Collected Balance", else it will be defaulted as "Book Balance". Interest Computation Balance Method Is Payment Tolerance Applicable (Cont.) Define Loan Product- Data Elements A new field Interest Computation Balance Method is introduced in the Control Parameter panel. This is a drop-down field. It has values as (a) Collected Balance (b) Book balance. For upgrade Impact, if the field Collected Balance is selected, then the value will be defaulted as "Collected Balance", else it will be defaulted as "Book Balance". By default this will be unchecked. 2.3.3 Define TD Offer Table 2 7 Define TD offer - Data Elements Top Up Allowed By default this will be unchecked. Raise Interest Rate on Adhoc Basis By default this will be unchecked Upgrade Impacts 2-5
2.3.4 Define TD Product Table 2 8 Minimum Term for Interest Eligible in days Define TD Product - Data Elements Deleted 2.3.5 Define CASA Product Table 2 9 Align Fees with Statement Cycle Align Interest with Statement Cycle Define CASA Product - Data Elements By default this will be unchecked By default this will be unchecked Billing Functionality By default this will be unchecked 2.3.6 Define CASA Offer Table 2 10 Minimum Sweep-In Amount Sweep-In Amount basis "In Multiples of" Define CASA Offer - Data Elements By default this will have value as 0. By default this will have value as 0. Courtesy Pay By default this will be unchecked Charge Single Fee for Multimode withdrawal Transaction Display Single Transaction for Multimode withdrawal Transaction in Bank Statement By default this will be unchecked By default this will be unchecked 2.3.7 Define Loan Offer 2-6 Oracle Banking Platform Functional Upgrade Guide
Table 2 11 Capture Account Level Purpose Code Maturity Date Intact on Repayment date change Maturity Roll over Allowed Define Loan Offer - Data Elements Deleted By default this will be unchecked A new panel Maturity Treatment Preferences is introduced. This has two columns: (1) Event (2) Required For. The Event name column displays the following events: (a) Loan offer Swap (b) Loan Consolidation (c) Restructure (d) Deferment (e) Change Repayment Date (f) Loan Disbursement The Required For field is of drop-down type. It has values as (1) Intact (2) Extend Change or (3) Both If Maturity Date Intact on Repayment Date change was selected earlier then the value will be stamped as "Intact" against the event Change Repayment Date. By default this will be unchecked 2.3.8 Define Loan Bank Policy Upgrade Impacts 2-7
Table 2 12 Amount Variation that require Credit Assessment Define Loan Bank Policy - Data Elements Deleted In the Control Parameters, a new panel is introduced to allow the user to capture the event-wise account variations that requires Credit Assessments. It has two columns (a) Event and (b) Required For. The following events are displayed: - Loan Offer Swap - Change Overdraft to Term Loan - Loan Split - Loan Consolidation - Restructure - Change Rate Type/Repayment Type For each of the above mentioned events, the user will be allowed to capture the values as either (a) None or (b) Move to IOI/IOA. By default the values will be displayed as None. 2.3.9 Define Statement Policy Table 2 13 Define Statement Policy- Data Elements Billing Statement By default this will be unchecked. 2.3.10 Define Domain Category Settlement Mode Table 2 14 Define Domain Category Settlement Mode- Data Elements Transaction Code By default this will be blank. 2.3.11 Define Product Settlement Mode 2-8 Oracle Banking Platform Functional Upgrade Guide
Table 2 15 Define Product Settlement Mode- Data Elements Transaction Code By default this will be blank. 2.3.12 Define CASA Bank Policy Table 2 16 Sweep-In (a) Online or (b) EOD Define CASA Bank Policy- Data Elements By default it should be Online. 2.3.13 Define Product Group Table 2 17 Define Product Group - Data Elements Product Group Code Based on the type of the Insurance, the PG code will be defaulted as either INPGCCI001 / INPGLMI001 / INPGAS001 / INPGFDPI001. Product Description Based on the type of the Insurance, this field will be defaulted as either CCI / LMI / FDPI / Insurance Others Product Group. Linkage Type Product Group Type Non MOF Product Type Based on the type of the Insurance, the appropriate Product Type will be defaulted as either CCI Insurance / LMI Insurance / FDPI Insurance or Insurance Others. Origination Insurance Unchecked workflow behavior Is External Unchecked Currency Insurance Plan Currency /Branch local Currency Question Set Id Not Applicable for CCI/LMI/FDPI and Insurance Others Description Not Applicable for CCI/LMI/FDPI and Insurance Others There will be a separate Product Group definition for each type of Insurance that is CCI/ LMI / FDPI and Insurance Others. Upgrade Impacts 2-9
2.3.14 Define Insurance Product Table 2 18 Define Insurance Product - Data Elements Product Code Based on the type of the Insurance, the Product code will be defaulted as either INPRCCI001/ INPRLMI001/ INPRAS001/ INPRFDPI001. Product Based on the type of the Insurance, this field will be defaulted as either CCI Product /LMI Product/FDPI Product/ Insurance Others Product. Product Start Date The system has to compare all the Insurance Plan start date for a particular type of Insurance and put the oldest Plan Start date as Product Start Date Expiry Date Product Group Based on the type of Insurance appropriate Product Group needs to be linked. Example: Suppose the product is being created for CCI, then CCI Product Group needs to be linked. Currency Code Insurance Plan Currency needs to be mapped. Owner Browser Image There will be a separate Product Code definition for each type of Insurance that is CCI/ LMI/ FDPI and Insurance Others. Example: If there are 4 CCI Plans with the following start dates: CCI Plan 1 -Jan 1 2017 CCI Plan 2 -Feb 1 2017 CCI Plan 3-Mar 1 2017 CCI Plan 4-Apr 1 2017 In this case, the system needs to capture Jan 1 2017 as start date. Unchecked 2.3.15 Define Insurance Offer 2-10 Oracle Banking Platform Functional Upgrade Guide
Table 2 19 Offer Code Define Insurance Offer - Data Elements Offer This needs to be mapped to Insurance Plan. Offer Description This needs to be mapped to Insurance Plan Description. Start Date Expiry Date Product Code Insurance Provider Code Insurance Provider CCI Insurance Insurance Beneficiary CCI Cover Type Default Cover Type Premium Payment Option Premium Type Cooling Period (in days) For each type of Insurance, all the Insurance Plans under the said Insurance Type needs to be created as Insurance Offer. For example, if there are 4 CCI Plans and 3 LMI Plans and 2 FDPI Plans are defined in the Insurance Module, then in, 4 CCI Offer, 3 LMI Offer and 2 FDPI Offers will be auto created. Unchecked Upgrade Impacts 2-11
Table 2 19 CCI Opt-In Period (in days) Maximum Sum Assured for Death Cover Periodicity of Premium Review period (in months) Premium Repayment Terms (Years) Premium Re-calculation method Policy Review Lead Days (for Recalculation of premium) Review Period revision (on mid-term adjustments) Premium Preference Notice Days Age at Entry (Min and Max) in years Age at maturity (in years) Policy Term (Min & Max) [in years] Product Group Code Product Group Description Back Book Campaign Period - From Date and To Date (Cont.) Define Insurance Offer - Data Elements LMI Insurance 2-12 Oracle Banking Platform Functional Upgrade Guide
Table 2 19 Insurance Beneficiary Premium Payment Option Insurance Others\FDPI Insurance Beneficiary Common Internet Banking Unchecked Phone Banking Unchecked Branch Unchecked ATM\POS Unchecked Mobile Banking Unchecked Offer Eligibility Rule Id Offer Eligibility Rule name For CCI, CCI eligibility rules as defined in the Insurance Plan needs to be linked. For LMI, Asset and FDPI it will be blank. The corresponding offer name will be displayed if the Rule is linked. Alert Events This will be done operationally after discussing with the banker. Lead Days This will be done operationally after discussing with the banker. Lag Days This will be done operationally after discussing with the banker. Entity Entity Reference Id (Cont.) Define Insurance Offer - Data Elements Term & Conditions Icon Id Upgrade Impacts 2-13
Table 2 19 Additional Product Information Offer - Text 1 Offer - Text 2 (Cont.) Define Insurance Offer - Data Elements 2.3.16 Insurance Table 2 20 The following screens have been moved from the Insurance Module: Movement of Insurance screens Screen / Moved From Moved To Insurance Provider Maintenance - LCM Module Insurance Plan Maintenance Party Module Module The expectation is that as part of migration the Insurance Provider will be On-boarded into the Party Module either operationally or through running a migration script. The impact will be done to auto create the Product Group, Product and Offer for Insurance. If the existing Insurance Plan Maintenance has a plan for (a) CCI (b) LMI (c) FDPI and (d) Insurance Others, then the system migrates such plans in the Product Manufacturing Hierarchy Structure as follows: For each type of Insurance, one new Product Group will be automatically created. For each type of Insurance, one new Product will be automatically created and linked to the appropriate Insurance Product Group. For each type of Insurance Plans, the new Insurance offers will be created and linked to the appropriate Insurance Product. 2-14 Oracle Banking Platform Functional Upgrade Guide