Extensibility Getting Started
Contents
1. 8 5 122 Screen Modi fic tions sisie iieii n E a E E E E E Ra qase te nite Sete feda tees 8 JRI Amend field level attributes snatri ia a E RE E EEA EE EE EE tenues 9 SAA Style Sheet chan ges cc unis er in E es aah E A etsi 9 545 Language conversion Of SCLECNS ee ettet e ee eod BUG ak Bien d iets 9 3 23 ZFuncti0nal setae rei ed Reese 9 32 User Defined fields at Maintenance isss rannin iae raa EE an dieere ee 9 522 NepSDEmundxruleforIC calculation go enero pene eee abeatis 10 5 2 3 Configurable workflow of Branch Screens eene eene 10 23 9 Processing logie 5d it eite eere ete oerte O EE E OPE ivre Peter a Pr esie cue teet eed 10 5 3 1 Additional validation logic for a field or group of fields sse 10 5 2 2 Modify defaulting logic for fields sssi e t ee es ne re en dd 11 53 3 Onhne contract extersibility a esae e eere he epe pend 12 5 34 tBatchtextensiubihtu s taedet d ee Rte eru 12 34 Notifications deep oe ERPDORUP GO CP UHORU OO REI DDR D beo tiem 12 DAD Event DASed Motpica Hons s esee eid eee ero D te eee E 12 3 5 Reports ix ede ne Hetero ed eese eb epe eae 13 LIE Net BIPIRepOFls eate m pa eiie rae e EODD RI DELE td eaa 13 5 5 2 New OBIEE based reports i e teed ete esed de ette etat ted taie 13 5 6 User defined Advice tags cene Du eRg phenomena RFID SEOSTE IEEE ERESSE EGS 13 5 01 New tag in Advice Message caissier beheben a De eere2. Fn Pre Default And Validate extensibility code start p Wrk stdorf p stdcif IF p wrk stdcif v sttms customer CARD HOLDER NAME NOT IN upper p wrk stdcif v sttms customer CARD HOLDER NAME THEN p err code USI COTHR OS T p err params NULL Dbg Out of validation code Sarva RETURN FALSE END IF extensibility code ends Dbg Returning Success From fn pre default and validate RETURN TRUE EXCEPTION WHEN OTHERS THEN Debug Pr Debug In When Others of stpks stdcif Custom Fn Pre Default And Validate 01 Debug Pr Debug SQLERRM p Err Code ST OTHR 001 p Err Params NULL RETURN FALSE END Fn Pre Default And Validate Note Open RAD XML for a given function ID using RAD tool to understand the data block and field name This would give above complete path to access the field name you can prefix p to get function ID data type and v to data block to get data block name Example to know the card holder name element at runtime use following template function id type data block name field name p wrk stdcif u sttms customer CARD HOLDER NAME Refer FCIS FD03 03 01 Extensibility By Example Volume 1 for detailed steps involved in this exercise 5 3 2 Modify defaulting logic for fields FLEXCUBE IS call outs allows to change defaulting logic for elements using PLSOL data types Note Refer e
3. boldface Boldface type indicates graphical user interface elements for example menus and menu items buttons tabs dialog controls including options that you select italic italic type indicates book titles emphasis or placeholder variables for which you supply particular values monospace Monospace type indicates language and syntax elements directory and file names URLs text that appears on the screen or text that you enter 2 Introduction 2 1 How to use this Guide The information in this guide includes Chapter 2 Introduction Chapter3 Extensibility Introduction Chapter 4 FLEXCUBE IS Extensibility Chapter 5 FLEXCUBE Extensible features Chapter6 Extensible Development Life Cycle Chapter 7 Resources FCIS FD03 01 01 Extensibility Getting started 4 3 Extensibility Introduction 3 1 What is extensibility Extensibility is an ability of the software system to allow and accept the significant extension of its capabilities without major rewriting of code or changes in its basic architecture Extensible systems provide technology tools languages that designed so that developers can expand or Following are the industry pattern to address the extensibility in software architecture add to its capabilities 3 2 Industry Pattern e Frameworks e Configuration files 3 3 Extension using scripts User specific extension software packages Object based programming where
4. entente 13 S4 Interfaces sce odd US opo ei E ER EU EE E O RSS 13 5 7 1 Switch Interface 4508583 configuration tee etie tiae neta 13 5 72 Configurable Generic Interface for upload handoff sse 13 5273 Unploadiadapter framework ace o e t t et ne pP hv 14 6 Extensibility development life cycle eterni roro tdt ie n iere dens 14 6 1 Define Extensibility Requirement esee nennen nennen eene enne enne nette tene tere trente en trennen 14 6 2 Identify the Business area of extensibility sese enne trennen nennen enne 15 6 3 Identify the tools framework to be used ssesssssssssesseeeeeee eene enne enne 15 6 4 Identify the file types amp layers applicable ssessssessessesseeeeeeeeeneenenn ener nennen tenens 16 6 2 JODevelopchanges ooo MenOU ERU SIR MEL 16 6 6 Testitin FLEXCUBE environment a ienr ee eroe nennen nennen reete en ne enne enne tenete retener entren trennen 16 7 Resourceaz uso cbe thui nene noni bc UD REGE HR 16 FCIS FD03 01 01 Extensibility Getting started 2 1 Preface This document describes the concepts and helps reader to get started using Extensible framework of FLEXCUBE IS Application to develop additional functionalities 1 1 Audience The Extensibility getting started book is intended for FLEXCUBE Application Developers Users who are authorized to perform the following tasks Modify the layouts of existing FLE
5. inheritance is used for extensibility Industry Approach Industry approaches to extensibility typically includes following Tools to allow to extend the functionality of base product Program hooks to allow developers to insert their program routines Ability define new business events to address change in process Ability to create regional specific software changes Ability to add remove fields at business messages Ability to configure interface protocols without software change 4 FLEXCUBE IS Extensibility 4 1 Business Areas One of the primary goals of the FLEXCUBE IS architecture is that system should be able to be extendable in required business specific areas Following are such areas where extensibility is required Business Area Screen changes Language of Screens Business legal requirements Events amp eco system participation FCIS FD03 01 01 Extensibility Getting started Why extensibility required User may want to keep some screens simple to improve training amp operational efficiency User may wish to provide screens other than the default language of software Certain processing calculation logic may be applied specific to region country judiciary The software has to be part of bigger eco system by providing other integration notification mechanism Software should provide mechanism to extract required information System to be open to provide the same System should provide mechanism to exchan
6. supplemental regulations As such use duplication disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government This software or hardware is developed for general use in a variety of information management applications It is not developed or intended for use in any inherently dangerous applications including applications that may create a risk of personal injury If you use this software or hardware in dangerous applications then you shall be responsible to take all appropriate failsafe backup redundancy and other measures to ensure its safe use Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for intero
7. FCIS FD03 01 01 Extensibility Getting started 12 Refer FCIS FD02 05 01 RAD Notification Development 5 5 Reports FLEXCUBE provides factory shipped BIP canned reports and OBIEE repositories User can extend the reports or repositories to suite the local requirements Refer FCIS FD07 01 01 Report Getting started for more information 5 5 1 342 2 New BIP Reports User can develop the new report or modify the existing report to change report query result columns or filter criteria Refer FCIS FD07 02 01 BIP Report Development Guide for more information on BIP report development New OBIEE based reports User can develop the new OBIEE repositories or work with existing OBIEE repositories Refer FCIS FD07 03 01 OBIEE repository Development Guide for more information on OBIEE repositories development 5 6 User defined Advice tags 5 6 1 New tag in Advice message FLEXCUBE provides rich set of advices with pre defined tags for each message type During run time the contents are fetched and filled in advices User can define new TAG and add code to fetch the logic 5 7 Interface 5 7 1 5 1 2 Switch Interface ISO8583 configuration FLEXCUBE user can configure the version and protocol fields of ISO8583 based SWITCH interface gateway User can define the mapping of ISO processing code and FLEXCUBE internal transaction code Configurable Generic Interface for upload handoff User can define following interfaces n
8. Oracle FLEXCUBE Investor Servicing Extensibility Getting started Release 12 0 3 0 0 Part No E53392 01 April 2014 ORACLE FINANCIAL SERVICES Contents 1 Pre aoeeoe 3 LI Audien esr e e e a o E E RR PPP EIER ere tH PIER 3 1 2 Related documents eee emer PERGERET rrr Rte ee ERE ee 3 1 37 Conventions cone e OR TOR EE a E E RR ERPU THE RERUM ER FEIER see ENS 4 2 Introduction annon dceo Tae A DER e dere een veri ie e ddr e 4 2L How touse this Guide oon eere Pap este a es dietum D p eei 4 3 Extensibility Introduction iii dee a e ete e ee ar be o AN it rci eris 5 3 1 What 1s extensibility inea E E A de E ee eerte Seed URSI eee ae ip ees 5 3 2 Industry P ttern oe ede SU d ssp d Rel Na ea 5 3 3 Industry Approach a eee ti ee este a die see eet ee EEA SSS 5 4 ELEXCUBE IS Extensibilityzisiientro d reet R E E d E ERN E 5 4 1 B sinessAreaS aiiin eet e NIA e RU Dig I A eei NG e te peste sue 5 4 2 FLEXCUBE IS Extensibility approach sees nen neen nenne etre enne nennen 6 4 3 FLEXCUBE IS Extensibility user roles eeseeseeeeeeeeeeneneenneeeennee nennen trennen nennen innen eene tenen 6 5 FLEXCUBE IS Extensible features csssssssesescessssescesesseccscessecencsssaccscssecssssssesssessesssssecessesserensessersneees 8 o L Screen changes uode qM HER a ea e OR Ene at UE bite tloae lessen et pe IR 8 Dill NCU SCHOCNS E
9. XCUBE Screens Modify the existing functionality by adding new fields tabs data blocks Extend the existing screen to have fields based on customer specific table fields Add customer specific validations at extension hooks Add customer specific processing logics in batch processing Add customer specific notifications Add customer specific calculation elements Add customer specific reports To Use this manual you need conceptual and working knowledge of the below Resources FCIS FD01 01 01 Development Overview Guide Proficiency FLEXCUBE IS Development overview RAD function ID development getting started FCIS FD02 01 01 RAD Getting Started 1 2 Related documents For more information on RAD development and extensibility refer the below documents FCIS FD01 01 01 Development Overview Guide FCIS FD02 02 01 RAD Function ID Development FCIS FD02 03 01 RAD Web Service Development FCIS FD02 04 01 RAD BIP Report Integration FCIS FD02 05 01 RAD Notification Development FCIS FD05 02 01 RAD Reference FCIS FD03 02 01 Extensibility Reference Guide FCIS FD03 03 01 Extensibility By Example Volume 1 FCIS FD03 03 02 Extensibility By Example Volume 2 FCIS FD04 02 01 Generic Interface Configuration Guide FCIS FD04 03 01 Upload Adapter Development Guide FCIS FD03 01 01 Extensibility Getting started 3 1 3 Conventions The following text conventions are used in this document Convention Meaning
10. at requires extensibility development This includes Function ID New modify existing add fields hide fields Processing logic defaulting enriching validating UDF New UDF fields for identified function IDs SDE new SDE for calculation purpose Accounting Batch New batch function during EOD time or intraday Notification New event notification Report new report or modify existing report query Interface New incoming or outgoing Adapter Migration data upload into FLEXCUBE 6 3 Identify the tools framework to be used Area Function ID Processing logic UDF SDE Accounting Batch Notification FCIS FD03 01 01 Extensibility Getting started FLEXCUBE Tools Framework RAD Style sheet editor PLSQL programming on RAD generated packages PLSQL programming on core packages UDDMAINT function ID PLSQL programming on Hand coding of UDF logics SDE maintenance PLSQL programming on Hand coding of SDE data fetch logic PLSQL programming on Accounting extensible packages PLSQL programming on Batch extensible RAD Notification trigger 15 development Reports BIP report development OBIEE based reports development Interface Generic Interface framework 6 4Identify the file types amp layers applicable The below table described the layer and file types developed for each extensibility business areas that involves
11. ce Definiti on on Implementer Yes Yes Yes Yes Implementer could be OFSS staff or customer partner staff who implements FLEXCUBE FCIS FD03 01 01 Extensibility Getting started 7 IS Bank Application Yes User Application users are the bank FLEXCUBE functional users Bank IT User Yes Yes Yes Bank IT user could be system administrators and have technical skill to extend the FLEXCUBE IS 5 FLEXCUBE IS Extensible features This section describes the extensible features available in FLEXCUBE IS 5 1 Screen changes This section describes features that are specific to Function ID screens extensibility RAD tool is used for function ID extensibility 5 1 1 New Screens RAD tool used to develop the new screens depending upon the bank requirement The screens are based on existing or new tables added in database Refer following documents for more information on working with screens FCIS FD02 01 01 RAD Getting Started FCIS FD05 02 01 RAD Reference FCIS FD03 02 01 Extensibility Reference Guide 5 1 2 Screen Modifications Existing screens layouts can be modified using RAD tool to suite as follows Hide fields that are not relevant to a given implementation Modify the placement of the fields example moving from one tab to other tab FCIS FD03 01 01 Extensibility Getting started 8 Add LOV to a given field Changing the data type Adding enumerations to a given field to restrict user inputs To inc
12. coming to get data into FLEXCUBE FCIS FD03 01 01 Extensibility Getting started 13 Outgoing to get data out of FLEXCUBE Refer FCIS FD04 02 01 Generic Interface Configuration Guide on how to define generic interface 5 7 3 Upload adapter framework FLEXCUBE IS provides factory shipped adapters spread sheet based upload for incoming Interface upload purpose User can extend by developing new adapter using upload adapter framework Refer FCIS FD04 03 01 Upload Adapter Development Guide 6 Extensibility development life cycle Extensibility development involves following stages These stages are explained in detail further down the line Testitin FLEXCUBE environment Define Identify Business Identify the Extensibility area of tools framework Identify file types Develop the amp layers changes requirement extensibility to be used 6 1 Define Extensibility Requirement Extensibility Requirements need to be clearly defined and documented This requirement should describe the module function ID if applicable and intended functionality required This requirement should have justification of why extensibility needed compared with base functionality It also should cover other alternatives to achieve the functionality without extensibility FCIS FD03 01 01 Extensibility Getting started 14 6 2 Identify the Business area of extensibility Depending upon the Requirement user needs to identify the FLEXCUBE business area th
13. ge information with ad hoc systems over the period time User configurable messages reports Ad hoc exchange of information between systems 4 2 FLEXCUBE IS Extensibility approach FLEXCUBE IS provides the following approach to address the extensible requirement Pattern Framework Configuration files Extension using Scripts User specific extension of software package User defined events Protocol tweaking User Regional specific processing logic 4 3 FLEXCUBE IS Extensibility user roles Industry Approach Tools and framework to extend the base product XML files Text files to configure Scripts Program hooks to allow extension logic call outs Ability to define new events message types Configuration of protocol without software change Ability to extend the core processing logic FLEXCUBE Approach RAD framework XML configuration files and Text based configuration files Java Script based extensions to enable extension at user interface layer FLEXCUBE call outs based on release type CUSTOM CLUSTER FEXCUBE notification and messaging architecture to define new XML message types FLEXCUBE ISO8583 protocol definition in XML file that can be modifiable FLEXCUBE UDF SDE IC and CL extensions FLEXCUBE IS Extensibility development can be classified into 4 types based on the complexity and user competencies required Application maintenance definition of components User expected to
14. login into FLEXCUBE application and use certain function IDs to define the new components This is typically applicable to Bank business user who requires new functionality FCIS FD03 01 01 Extensibility Getting started 6 Example user need to use function ID UDDMAINT to define new UDF field Configuration files User expected to modify some of the parameters in configuration files This may require restart of application or relevant applications Typically this is required for application administrators in bank Example user may need to modify the 508583 protocol definition Tools based development User expected to understand the given function ID working and required to extend the functionality by adding new data sources and fields This is typically required by IT developer in bank Example User needs to change screen layout to add new data blocks based on new tables added in database Programming User expected to achieve granular control and validations using programming extensions User expected to know the language used thoroughly in this context This is typically required by advanced developers in bank Example bank required to modify the defaulting and validation or modify the processing flow at specific call out points Developer role and extensible approach matrix Given below matrix depicts the developer role and possible extensible approaches to apply Developer role Maintenan Configurati Tools Programming
15. nt FCIS FD03 01 01 Extensibility Getting started Resources FCIS FD02 01 01 RAD Getting Started FCIS FD05 02 01 RAD Reference FCIS FD02 02 01 RAD Function ID Development FCIS FD02 03 01 RAD Web Service Development FCIS FD02 04 01 RAD BIP Report Integration FCIS FD02 05 01 RAD Notification Development FCIS FD03 02 01 Extensibility Reference Guide FCIS FD03 03 01 Extensibility By Example Savings zip WB user manual FS_StyleDesigner_for_FC_IS_10 3 0 0 0 0 0 zip FCIS FD04 02 01 Generic Interface Configuration Guide FCIS FD04 03 01 Upload Adapter Development Guide 17 ORACLE FCIS FD03 01 01 Extensibility Getting started April 2014 Version 12 0 3 0 0 Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon East Mumbai Maharashtra 400 063 India Worldwide Inquiries Phone 91 22 6718 3000 Fax 91 22 6718 3001 www oracle com financialservices Copyright 2007 2014 Oracle and or its affiliates All rights reserved Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific
16. ogic Refer FCIS FD03 03 01 Extensibility By Example Volume 1 for examples 5 2 3 Configurable workflow of Branch Screens Configurable stages available for FLEXCUBE IS Branch function IDs Branch function ID can be identified the module type WB in menu static data User can define the function ID and applicable stages Refer Savings zip user manual section 3 for workflow definition features 5 3 Processing logic 5 3 1 Additional validation logic for a field or group of fields FLEXCUBE IS provides the extension call outs in database layer These extension call outs are extensible package and pre named procedures to be used for extensibility The base product will call this call outs during runtime with required PLSQL data type as parameters Example User wanted extends STDCIF function to add capital letter validation for the field card holder name This can be achieved as follows Edit the STPKS STDCIF CUSTOME Fn Pre Default Validate as below FUNCTION Fn Pre Default And Validate p Source IN VARCHAR2 p Source Operation IN VARCHAR2 p Function Id VARCHAR2 p Action Code VARCHAR2 p Child Function VARCHAR2 stpks stdcif Main ty stdcif OUT stpks stdcif Main ty stdcif OUT stpks stdcif Main ty stdcif OUT VARCHAR2 OUT VARCHAR2 p Prev stdcif p Wrk stdcif p Err Code p Err Params RETURN BOOLEAN IS BEGIN FCIS FD03 01 01 Extensibility Getting started 10 I I I I p stdcif T I I I I Dbg In
17. perability 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 FCIS FD03 01 01 Extensibility Getting started 18
18. rease the set fields example adding the address line 5 Refer FCIS FD03 03 01 Extensibility By Example Volume 1 for examples 5 1 3 Amend field level attributes Existing file level attributes can be modified to add below Defaulting some value to reduce user input errors Restring the maximum and minimum value Precision settings Refer FCIS FD03 03 01 Extensibility By Example Volume 1 for examples 5 1 4 Style Sheet changes FLEXCUBE IS provides style editor to enable CSS changes to have following user specific UI elements design Page template changes Dialog template changes Form elements look and feel Text fonts Tables look and feel Colors changes Refer FS StyleDesigner for FC IS 10 3 0 0 0 0 0 zip for more information 5 1 5 Language conversion of screens FLEXCUB screens can be extended to support languages other than English 5 2 Functional 5 2 1 User Defined fields at Maintenance FCIS FD03 01 01 Extensibility Getting started 9 UDF framework enables the bank user to add the new field without changing any table structure This is used in maintenance function IDs where new field required by bank user Refer FCIS FD03 03 01 Extensibility By Example Volume 1 for examples 5 22 New SDE and rule for IC calculation IC module SDE framework enables user to add the user specific system data element for which user can write the data fetch logic This SDE can be used further in building the interest calculation l
19. software modification Area Client Layer Application Layer Database Layer Function ID Java script files UIXML RAD generated CUSTOM CLUSTER packages Processing RAD generated logic CUSTOM CLUSTER packages Core FLEXCUBE Packages UDF UDF specific procedures and packages SDE IC and CL packages Accounting Accounting packages Batch Batch processing package Notification RAD generated Notification Triggers Reports RTF file RAD generated Report XDO file packages Interface NA NA NA 6 5 Develop changes User can develop the required changes using respective tools documents Refer section 5 for development documentation help on each area of extensibility 6 6 Test it in FLEXCUBE environment User need to copy the developed files to target environment and can test the developed functionality Refer the FLEXCUBE IS installation manuals on how to deploy the changes 7 Resources Refer the below resources to gain further working knowledge with extensibility FCIS FD03 01 01 Extensibility Getting started 16 To Do RAD Getting started RAD complete reference guide RAD screen development step by step procedure RAD web service development BIP report integration with RAD screen Outbound Notification trigger development Extensibility Reference guide Extensibility use case development examples Branch work flow definition Style sheet editor Generic Interface configuration Guide FLEXCUBE Upload adapter developme
20. xample given in section 5 3 1 to know how to identify the element name FCIS FD03 01 01 Extensibility Getting started 11 5 3 3 Online contract extensibility FLEXCUBE IS allows to modify or enrich the oline processing logics at given call out functions Note How to identify package name Refer the RAD generated packages for CUSTOM and CLUSTER types to know the possible call outs available which has PLSQL data type parameters To arrive at the package name using following template Template Module code gt PKS_ lt Function ID Release type Example To get the CUSTOM release of function ID FTDTRONL which belongs to FT module package would be FTPKS FTDTRONL CUSTOM 5 3 4 Batch extensibility Apart from RAD generated function ID based data base packages FLEXCUBE IS allows to modify below core service packages Note that these are core packages which don t have any function ID associated ACPKS package is extensible using following packages ACPKS CUSTOM ACPKS CLUSTER WRP BATCH batch running package is extensible using following packages WRP BATCH CLUSTER WRP BATCH CUSTOM Refer the FCIS FD03 03 02 Extensibility By Example Volume 2 for example 5 4 Notifications 5 4 1 Event based notifications FLEXCUBE IS supports events based notification framework where notification triggers can be developed as per user requirement Once the event occurs the framework pushes the required data to external systems
Download Pdf Manuals
Related Search