Open Development Tool Getting Started User Manual
Contents
1. Third character Type D Detail S Summary R Report C Call form N Notification A Authorization 5 1 ORACLE Example STDCIF Detailed screen STSCIF Summary screen ACRJRNAL Report Screen e CONCUSAD Notification of customer address on core module e 1010 Web Branch screen 5 2 Actions and Applicability FLEXCUBE Function ID can send the following action request to database Depending upon the function ID type certain actions applicable and others restricted 5 2 1 Actions Action Purpose New To Create the New record at Data sources Copy To copy the Non Primary key data to another record Delete To Delete the record before authorization Close To mark record closed after authorization Unlock To amend modify the record unlock request sent to FLEXCUBE followed by Save Reopen To re open the closed record Print To Print the data Save To Save the data entered in form Authorize To Authorize the record Reverse To Reverse the transactions contracts Rollover To Rollover the transactions contracts Confirm To confirm certain transactions Liquidate To Liquidate the contracts Hold To Hold the contracts for further actions at later time Template To create as template View To View the certain details messages Generate To generate certain messages Enter Query To Enter Query 5 2 ORACLE Action Purpose Execute To Ex2. Block Type Pick e Control e Normal e Summary Multi Record Pick Yes No Master Block Pick Yes No 7 5 ORACLE Specification Data Data sources to be added Link the data source with this data block 7 8 Block Fields Repeat the below table for every field under every Data block added Block properties edit is optional step User can add delete the feature that impacts the specification in below table Specification Data Field Name Specify the field name XSD Node Change XSD name if required LOV Name if applicable Attach LOV if required Field Size Change Field input size if needed Default Value Specify the Default Value if required Related Block Specify this field incase amount that requires currency formatting Related Field Specify this field incase amount that requires currency formatting For event type fields the below can be specified Specification Data Event name Pick predefined JavaScript events Function Name Pick specify Function name associated in javascript Event Type Event type associated with Button e Normal 7 6 ORACLE Specification Data e Call form e Sub function e Sub Screen Button Screen Specify the Screen name if call form applicable Call form Name Fill this if event type is call form Screen Name Fill screen name if ev
3. Max Length 105 It is optional to change Max length to input at field Specification Data Column Name FC END DATE Specify the column name Max Length 7 It is optional to change Max length to input at field 2 STTM_PERIOD_CODES Specification Data Column Name PERIOD_CODE Specify the column name 11 6 ORACLE Specification Data Max Length 3 It is optional to change Max length to input at field Specification Data Column Name Specify the column name PC_START_DATE Max Length 7 It is optional to change Max length to input at field Specification Data Column Name PC_END_DATE Specify the column name Max Length 7 It is optional to change Max length to input at field 11 6LOV Repeat the below table for every LOV added Specification Data LOV Name None Specify LOV name LOV Query None Specify LOV Query 11 7Data Block Repeat the below table for every Data Block added 1 Specification Data ORACLE 2 Specification Data Block Name Specify block name Follow naming convention BLK_STTM_PERIOD_CODES Block Title Specify Block Title None Parent Specify the Parent Block incase if this is multi record detail block None Relation Type Pick e One to One e One to Many One to One XSD Node Specify the name to be use
4. 7 FUNCTION ID SPECIFICATION SHEE T cccssscsscssssssssscccccccsssssssccccccssssssseccccsescsssssececcessesssscecccssces 7 1 7 1 PREPARATION CHECK LL td 7 1 7 2 A RT ED OPP AN 7 1 7 3 PREFERENCES aria tiro roer ii ud 7 2 7 4 DATA SOURCES e ica 7 3 7 5 DATA SOURCE COFUMNS 2 A A ad 7 4 7 6 EOV a Re e RI NS OE Re SE a ee OER er 7 4 7 7 DATA BLOCK E E a TN E E AE A A E 7 5 7 8 BLOCK PELOS dicto 7 6 7 9 SCREEN A tote su5 ceeds aa A A a a ea ada 7 7 FAQ IBID SETS nea a E E A la 7 8 TAI CALLE FORM ep re ro 7 9 VEZ SUMMARY a is 7 10 8 GENERATED UNITS sisscsccsccsicccssdscsscccccsccessssvscencececsnscsvacnsasevacsacccnssnsosssecteecevasosesduecsosesossosecaveccesesvaeaeeanceasoess 8 1 9 SCREEN RUNTIME DATA FLOW cscsssssicssccscccsscsssesssceccssasssossetscessecesssosssvessesacescobsocessessasessabcecescsesscessceoeones 9 1 10 RESOURCES iessdssscsessescssec scccseseevscecscsoessocssssedeuccosscassssecvevesosasecoodeccesess sssesesscesebasvasoosoescecenaszsssccoessecvoasbacsees 10 1 11 SS cescdsevesoneseescevsevvecsscesscsavdsvoscosseessssisesecseves suse 11 1 11 1 PREPARATION CHECK LIT atacada 11 1 E E TNT 11 1 DES PREFERENCES coa 11 2 11 4 DATA SOURCE Si and 11 3 TS DATA SOURCE COLUMNS aia 11 5 DO TAQ oe as dicas SERIOS 11 7 IZ MATA BELO 11 7 Me UBEOCK BIREDS ns 11 9 DILO SCREENS a 11 14 11 10 FIELD SETS a eR a SO IR PO 11 16 1 1 ORACLE 11 11 EMM ti 11 17 11 12 SUMMARY tata E A EP ia canes 11 17 1 2 O
5. Server Java Script js Run time Application Server Database INC files INC Run time Database Database spec spc sql Run time Database Refer the complete check list and detailed deployment steps in Open Development tools reference guide 8 1 ORACLE 9 Open Development Screen runtime data flow FLEXCUBE at runtime works with two kind of XML between client browser and application server layers e UIXML This is the User interface definition XML file which is generated by Open Development tool Ul XML would have the definition of graphical elements like data block screens fields etc e Data XML This is the runtime FLEXCUBE data structure XML used for HTTP request and response This structure is defined at various code lines like JS files FLEXCUBE frameworks database spec and bodies The below diagram explains the flow of the above XMLs during the FLEXCUBE application user operations Client Selects ORACLE 9 1 10 Resources Refer the below resources to gain further working knowledge with Open Development tool To Do Resources Open Development tool installation Installation and Setup Open Development complete reference guide Reference Open Development screen development step by step procedure Function ID Development Open Development web service development Web Service Development BIP report integration with Open Development screen BIP Report In
6. Specify the field name XSD Node FINCYCLE Change XSD name if required LOV Name if applicable None Attach LOV if required Field Size None Change Field input size if needed Default Value None Specify the Default Value if required Related Block None Specify this field incase amount that requires currency formatting Related Field None Specify this field incase amount that requires currency formatting Specification Data Field Name FCSTARTDATE Specify the field name XSD Node FCSTARTDATE Change XSD name if required LOV Name if applicable None Attach LOV if required Field Size None Change Field input size if needed Default Value None Specify the Default Value if required Related Block None Specify this field incase amount that requires currency formatting Related Field Specify this field incase amount that requires currency formatting None 11 10 ORACLE Specification Data Field Name DESCRIPTION Specify the field name XSD Node DESCRIPTION Change XSD name if required LOV Name if applicable None Attach LOV if required Field Size None Change Field input size if needed Default Value None Specify the Default Value if required Related Block None Specify this field incase amount that requires currency formatting Related Field None Specify this field incase amount that requires currency formatting Specification Data Field Name FCENDDATE Sp
7. incase amount that requires currency formatting Related Field None Specify this field incase amount that requires currency formatting 11 9Screens Repeat the below table for every Screens added Specification Data Screen Name CVS_MAIN 11 14 ORACLE Specification Data Define screen name Screen Title None Specify the screen title Screen Size Medium Pick e Small e Medium e Large Exit Button type Default Cancel Pick e Default Cancel e Default Ok Cancel e Default Ok Reject Cancel Is it Main screen Yes Pick Yes No Repeat the below table for every Tabs added Specification Data Screen name CVS_Main Link screen name with the Tab Name Tab Name TAB_MAIN Specify the Tab name Follow naming convention Repeat the below table for every Sections added Specification Data Section Name SEC_SECTION1 Specify the section Name Partition Names PART 1 Define partition names If applicable ad sub partition number Specification Data 11 15 ORACLE 11 10 Specification Data Section Name Specify the section Name SEC_SECTION2 Partition Names PART 1 Define partition names If applicable ad sub partition number Field Sets Repeat the below table for every Field sets added Specification Data Fieldset Name FST_FIELD1 Specify Field set name Scree
8. name Follow the FLEXCUBE naming conventions for data source entities Is it Master Yes When multiple data sources used in a screen one has to be Mater type Accordingly select Yes No Relation type One to One This defines detail to parent relationships when multiple data sources used Define one of the below accordingly e One to One e One to Many Is it Multi Record data source NO This defines if multiple records to be shown on screen Parent None This defines the parent data source for this multiple record data source ORACLE 2 Specification Data Relation This defines the relation KEYs between the data sources It refers the columns use to join tables None Where clause Specify where clause None Default order by Specify Default Order by clause None Type of Data source Pick e Normal e Query e InOnly e Summary Normal PK Cols This should get defaulted Otherwise specify in tilde separated format FIN_CYCLE PK Types This should get defaulted Otherwise specify in tilde separated format VARCHAR2 Specification Data Data source name STTM_PERIOD_CODES Fill up the Data source name Follow the FLEXCUBE naming conventions for data source entities Is it Master No When multiple data sources used in a screen one has to be Mater type Accordingly select Yes No Relation type One to Many T
9. text conventions are used in this document Convention Meaning 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 forwhich you supply particular values monospace Monospace type indicates language and syntax elements directory and File name URLs text that appears on the screen or text that you enter Indicates important information 1 2 ORACLE 2 Introduction 2 1 How to Use this Guide The information in this guide includes e Chapter 2 Introduction e Chapter 3 Getting started e Chapter 4 Installation e Chapter 5 Function ID e Chapter 6 Development cycle e Chapter 7 Function ID specification Sheet e Chapter 8 generated units e Chapter 9 Screen runtime data flow e Chapter 10 Resources 2 1 ORACLE 3 Open Development Getting started 3 1 What is Open Development Rapid Application Development Open Development is the Web based tool that is intended to develop the FLEXCUBE UBS screens and other components It is the Integration Development Environment for the FLEXCUBE Application Development Open Development is used for the following purpose e Develop the Function ID and Deploy into Target environment e Develop the Web serv
10. Getting Started Oracle FLEXCUBE Universal Banking Release 12 0 May 2012 Oracle Part Number E51527 01 ORACLE FINANCIAL SERVICES Getting Started Table of Contents We SPIRTEH AGRE lt i scccsscccscucscosssvsdcesceedesesecves bones ceessccecssocaetstenecuseeasesscoveussesssenean doescesess seuss Geveusssesensonssessssesasonscsasvesesess 1 1 1 1 AUDIENCE eee rl EE 1 1 1 2 RELATED DOCUMENTS tecipoloce cx tn suo bev A o ek eee 1 1 1 3 CONVENTIONS a chee eee 1 2 2 AN EUA O A 2 1 2 1 HOW TO USE THIS GUIDE sciceiscccivacleccscedsdegscacccecswasuceceececcecscassdedscacedecswaseaedeeacceecssesedegscuceeecseasecespeccesaeseeeea sas 2 1 3 GETTING STAR DED saisiscscscss ccsecssssssescescccesoeectessssscsesecveecessececsesbebecsesasdasesseeesssessssacseasaveccesesdasesceevscsesssbosseeee 3 1 3 1 WHAT IS OPEN DE VELO MEN ici 3 1 3 2 WHAT IS NEEDED TO WORK WITH OPEN DEVELOPMENT oocccccccccccoconoconononononononononononononononononenenonanecenecenenesos 3 1 4 IA O AC sassis AGUDA TOS 4 1 A FUNCTION A OEA AA EA A EA 5 1 5 1 CLASSIFICATIONS iones e EARE aa ae aaae roepana 5 1 5 2 ACTIONS AND APPLICABILITY ococcccccncnnncnnnnnnnnonononoconononononononononononononononononononononnnonnnonnnonononononononanonaceneceneceses 5 2 5 2 1 A A iaieesausconseueies 5 2 5 2 2 ADPUCADUIIN saciar A opiyesdseccshssoeecgtsnoessdatcateneetecsaanediee caeicone Svan 5 3 DINAMARCA A ences ccvoseseseseseceesbesesvabvenceesevessones Sosesvaevesooues 6 1
11. RACLE 1 Preface This document describes the concepts and helps reader to get started using Rapid Application Development Open Development web based development tool to develop FLEXCUBE UBS user interface screens 1 1 Audience The Open Development getting started book is intended for the FLEXCUBE Application Developers who perform the following tasks with Extensible Open Development e Develop the new screen also called as function ID e To modify the existing screen e Bug Fixing the existing screen To Use this manual you need conceptual and working knowledge of the below Proficiency Resources FLEXCUBE Functional Architecture Training programs from Oracle Financial Software Services FLEXCUBE Technical Architecture Training programs from Oracle Financial Software Services FLEXCUBE Object Naming conventions Development Overview Guide Working knowledge of Web based Self Acquired applications Working knowledge of Oracle Database Oracle Documentations Working knowledge of PLSQL developer Respective vendor documents Working knowledge of PLSQL amp SQL Self Acquired Language Working knowledge of XML files Self Acquired 1 2 Related Documents For more information on Open Development development see these resources e Development Overview Guide e Reference e FCUBS FD05 03 01 DDL Reference e FCUBS FD05 04 01 TrAX Reference 1 1 ORACLE 1 3 Conventions The following
12. cation Data e Bulk Authorization e Upload DataBlock fields FINCYCLE Add data block fields and specify if this need to be FCSTARTDATE queriable field DESCRIPTION FCENDDATE 11 18 ORACLE ORACLE Getting Started Mayl 2012 Version 12 0 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores CA 94065 U S A Worldwide Inquiries Phone 1 650 506 7000 Fax 1 650 506 7200 www oracle com financial_services Copyright 2012 Oracle Financial Services Software Limited All rights reserved No part of this work may be reproduced stored in a retrieval system adopted or transmitted in any form or by any means electronic mechanical photographic graphic optic recording or otherwise translated in any language or computer language without the prior written permission of Oracle Financial Services Software Limited Due care has been taken to make this document and accompanying software package as accurate as possible However Oracle Financial Services Software Limited makes no representation or warranties with respect to the contents hereof and shall not be responsible for any loss or damage caused to the user by the direct or indirect use of this document and the accompanying Software System Furthermore Oracle Financial Services Software Limited reserves the right to alter modify or otherwise change in any manner the content hereof without obligation of Oracle Financial Services Software L
13. ck e Header e Body e Footer Tab Name Specify the already defined Tab name Section Name Specify the already defined Section Name Partition Name Specify the already defined Partition name FieldSet Fields Add data block fields that you wish to appear in given lt Screen Tab Section Partition gt Also select Sub partition if applicable 7 11 Call Form Repeat the below table for every Call form added Specification Data Function ID Link the call form name 7 9 ORACLE Specification Data Parent Block Link the parent block defined Parent Data source Link the parent data source defined Relation Define the relation Relation Type Pick e One to One e One to Many 7 12Summary Specification Data Data Block Link the Data block defined Data Source Link the data source defined Summary Type Pick e Summary e Query e Bulk Authorization e Upload DataBlock fields Add data block fields and specify if this need to be queriable field ORACLE 8 Open Development generated units Open Development generates the following type of files File Type File extensions Category Deployment Layer Open Development XML lt functioned gt _Open Development xml Development file Not Applicable and body Ul XML lt functioned gt xml Run time Application
14. d in XSD for Web service types Follow the naming convention Sttm Period Codes Block Type Pick e Control e Normal e Summary Normal Multi Record Pick Yes No Yes Master Block Pick Yes No No Data sources to be added Link the data source with this data block STTM_PERIOD_CODES Specification Data ORACLE Specification Data Block Name Specify block name Follow naming convention BLK_STTM_FIN_CYCLE Block Title Specify Block Title None Parent Specify the Parent Block incase if this is multi record detail block None Relation Type Pick e One to One e One to Many One to One XSD Node Specify the name to be used in XSD for Web service types Follow the naming convention Sttm Fin Cycle Block Type Pick e Control e Normal e Summary Normal Multi Record Pick Yes No No Master Block Pick Yes No Yes Data sources to be added Link the data source with this data block STTM_FIN_CYCLE 11 8Block Fields Repeat the below table for every field under every Data block added Block properties edit is optional step User can add delete the feature that impacts the specification in below table 1 BLK_STTM_FIN_CYCLE Specification Data Field Name FINCYCLE ORACLE Specification Data
15. e Parent e Child Parent ORACLE Specification Data Function Category Maintenance Pick the Category e Maintenance e Report e Transaction e Summary e Others Function ID STDACPER Enter Function ID Save XML Path D Open Provide your local machine path to save Open Developmen Tob Development XML that would be generated Parent Function None Provide Parent Open Development XML name in case you develop Child Function Type Parent Xml None Provide Parent Open Development XML path case you develop Child Function Type Header Template None Pickup the Header Template e None Default e Process Footer Template Main Audit Pickup Footer template e Maint Audit e Maint Process e Process 11 3 Preferences Specification Data Module Static Specify Module code Maintenance ST Head office function No 11 2 ORACLE 1 Specification Data Is it Head office function Auto Authorization No Applicable for maintenance Logging required No Flag to enable disable logging at Gateway layer Tanking Mofications No Should Tanking feature needs to be enabled Field log required No Should you required field level audit logs in FLEXCUBE STTB_FIELD_LOG 11 4Data Source Repeat the below table for every Data source added Specification Data Data source name STTM_FIN_CYCLE Fill up the Data source
16. ecify the field name XSD Node FCENDDATE Change XSD name if required LOV Name if applicable None Attach LOV if required Field Size None Change Field input size if needed Default Value None Specify the Default Value if required Related Block None Specify this field incase amount that requires currency formatting 11 11 ORACLE Specification Data Related Field None Specify this field incase amount that requires currency formatting Specification Data Field Name UDFFIELD Specify the field name XSD Node UDFFIELD Change XSD name if required LOV Name if applicable None Attach LOV if required Field Size None Change Field input size if needed Default Value None Specify the Default Value if required Related Block None Specify this field incase amount that requires currency formatting Related Field None Specify this field incase amount that requires currency formatting Event name onclick Pick predefined javascript events Function Name None Pick specify Function name associated in javascript Event Type callform Event type associated with Button e Normal e Call form e Sub function e Sub Screen Button Screen CVS_MAIN Specify the Screen name if call form applicable 11 12 ORACLE Specification Data Call form Name CSCUFVAL Fill this if event type is call form Screen Name CSCUFVAL Fill screen name if event type is cal
17. ecute Query Query 5 2 2 Applicability Action Maintenance Online New Yes Yes Copy Yes Yes Delete Yes Yes Close Yes Unlock Yes Yes Reopen Yes Print Yes Yes Save Yes Yes Authorize Yes Yes Reverse Yes Rollover Yes Confirm Yes Liquidate Yes Hold Yes Template Yes View Yes Generate Yes Enter Query Yes Execute Query Yes 5 3 ORACLE 6 Open Development development cycle Open Development Function ID development consists of the below broad steps For detailed procedures refer the Resources section Create Specification Design Layouts Develop Identity the function ID name Create the DB objects Design the Main screen and other screens Design the Tabs Buttons Design the field sets and fields linkage Add data source datablock LOV fieldsets screens fields Preview and Check Generate the files Deploy the files into target environment App layer de database layer Testwith FLEXCUBE URL 6 1 ORACLE 7 Open Development Function ID Specification Sheet From Functional specification BRD application developer can write technical specification to develop the screen This section describes the sample specification sheet for reader to get started Refer the appendices A for sample specification sheet Refer the FCUBS FD05 02 01 Open Development Reference guide to understand every specificati
18. ent type is call form or subscreen 7 9 Screens Screens are organized Screen Tab Tab Tab Header So repeats Footer Section Section 1 Section 2 Partition Partition Partition 1 1 2 Sub part Sub part 1 2 Repeat the below table for every Screens added Specification Data Screen Name Define screen name ORACLE Specification Data Screen Title Specify the screen title Screen Size Pick e Small e Medium e Large Exit Button type Pick e Default Cancel e Default Ok Cancel e Default Ok Reject Cancel Is it Main screen Pick Yes No Repeat the below table for every Tabs added Specification Data Screen name Link screen name with the Tab Name Tab Name Specify the Tab name Follow naming convention Repeat the below table for every Sections added Specification Data Section Name Specify the section Name Partition Names Define partition names If applicable ad sub partition number 7 10Field Sets Repeat the below table for every Field sets added Specification Data 7 8 ORACLE Specification Data Fieldset Name Specify Field set name Screen Name Specify the already defined Screen name Data Block Specify the already defined Data block Multi Record Pick Yes No View Type Pick single Multiple Screen Portion e Pi
19. his defines detail to parent relationships when multiple data sources used Define one of the below accordingly e Oneto One ORACLE Specification Data e One to Many Is it Multi Record data source Yes This defines if multiple records to be shown on screen Parent None This defines the parent data source for this multiple record data source Relation None This defines the relation KEYs between the data sources It refers the columns use to join tables Where clause None Specify where clause Default order by None Specify Default Order by clause Type of Data source Normal Pick e Normal e Query e InOnly e Summary PK Cols PERIOD_CODE FIN_CYCLE This should get defaulted Otherwise specify in tilde separated format PK Types VARCHAR2 VARCHAR2 This should get defaulted Otherwise specify in tilde separated format 11 5Data Source Columns Repeat the below table for every column under every Data Block added 1 STTM_FIN_CYCLE 11 5 ORACLE Specification Data Column Name FIN_CYCLE Specify the column name Max Length 9 It is optional to change Max length to input at field Specification Data Column Name FC_START_DATE Specify the column name Max Length 7 It is optional to change Max length to input at field Specification Data Column Name DESCRIPTION Specify the column name
20. ice related files for a Function ID e Develop the Notification Open Development xml and Notification Triggers e Develop the Function ID to integrate the BIP report e To modify the layouts of graphical components e To extend the Function ID for business purpose customers partners 3 2 What is Needed to Work with Open Development e Open Development tool installed and URL to be accessible e Target FLEXCUBE application development environment 3 1 ORACLE 4 Open Development Installation Refer FCUBS FD05 02 02 Open Development Installation and Setup for installation and setup of project release details Typically Open Development environments are shared by multiple Application developers 4 1 ORACLE 5 Function ID Function ID screen forms the basic block of FLEXCUBE UBS software Understanding various function ID types helps developer to choose appropriate parameters during Open Development development 5 1 Classifications FLEXCUBE Host function IDs and Branch function IDs are classified in two ways e Routing Type for Host and Branch screens e This classification can be retrieved from factory shipped information routing type that define the FLEXCUBE Application Menu structure Routing Type Type R Report M Maintenance X Extensible B Batch O Online L ELCM screens null Miscellaneous e Third character of Host screen Function ID depicts the type of function ID
21. imited to notify any person of such revision or changes All company and product names are trademarks of the respective companies with which they are associated
22. l form or subscreen 2 BLK_STTM_PERIOD_CODES Specification Data Field Name PERIODCODE Specify the field name XSD Node PERIODCD Change XSD name if required LOV Name if applicable None Attach LOV if required Field Size None Change Field input size if needed Default Value None Specify the Default Value if required Related Block None Specify this field incase amount that requires currency formatting Related Field None Specify this field incase amount that requires currency formatting Specification Data Field Name PCSTARTDATE Specify the field name XSD Node PCSTARTDATE Change XSD name if required LOV Name if applicable None Attach LOV if required 11 13 ORACLE Specification Data Field Size None Change Field input size if needed Default Value None Specify the Default Value if required Related Block None Specify this field incase amount that requires currency formatting Related Field None Specify this field incase amount that requires currency formatting Specification Data Field Name PCENDDATE Specify the field name XSD Node PCENDDATE Change XSD name if required LOV Name if applicable None Attach LOV if required Field Size None Change Field input size if needed Default Value None Specify the Default Value if required Related Block None Specify this field
23. n Name CVS_MAIN Specify the already defined Screen name Data Block Specify the already defined Data block BLK_STTM_FIN_CYCLE Multi Record Pick Yes No No View Type Pick single Multiple Single Screen Portion Pick e Header e Body e Footer Body Tab Name Specify the already defined Tab name TAB_MAIN Section Name Specify the already defined Section Name SEC_SECTION1 Partition Name Specify the already defined Partition name PART 1 11 16 ORACLE 11 11 Specification Data FieldSet Fields FINCYCLE Add data block fields that you wish to appear in given FCSTARTDATE lt Screen Tab Section Partition gt DESCRIPTION Also select Sub partition if applicable FCENDDATE Call Form Repeat the below table for every Call form added Specification Data Function ID CSCUFVAL Link the call form name Parent Block Link the parent block defined BLK_STTM_FIN_CYCLE Parent Data source Link the parent data source defined STTM_FIN_CYCLE Relation None Define the relation Relation Type One to Many Pick e Oneto One e One to Many 11 12 Summary Specification Data Data Block Link the Data block defined BLK_STTM_FIN_CYCLE Data Source Link the data source defined STTM_FIN_CYCLE Summary Type Pick e Summary e Query Summary 11 17 ORACLE Specifi
24. on attributes that are given here Refer the appendicle A for sample sheet 7 1 Preparation Check List Specification Data Tables Views created in Database Yes No Tables Views should be created in Database Primary Key populated at STTB_PK_COLS Yes No Primark Key details should be defined in STTB_PK_COLS The data can be inserted using Oracle DML commands Column Name population at CSTB_DATA_DICTIONARY done Yes No Column names should be defined in CSTB_DATA_DICTIONAY The data can be inserted using Oracle DML commands Label descriptions populated at CSTB_LABELS Yes No Label descriptions need to be populated at CSTB_LABELS for a given language that screen is developed Default language to be used for screen is English Database Schema name linked with Open Development tool Your Open Development tool needs to be configured with the Oracle FLEXCUBE Application Database schema where the tables views created 7 2 Basic Specification Data Action Pick Action e New e Load 7 1 ORACLE 7 3 Specification Data Function Type Pick Function Type e Parent e Child Function Category Pick the Category e Maintenance e Report e Transaction e Summary e Others Function ID Enter Function ID Save XML Path Provide your local machine path to save Open Development XML that would be generated Parent Function P
25. rovide Parent Open Development XML name in case you develop Child Function Type Parent Xml Provide Parent Open Development XML path case you develop Child Function Type Header Template Pickup the Header Template e None Default e Process Footer Template Pickup Footer template e Maint Audit e Maint Process e Process Preferences ORACLE Specification Data Module Specify Module code Head office function Is it Head office function Auto Authorization Applicable for maintenance Logging required Flag to enable disable logging at Gateway layer Tanking Modifications Should Tanking feature needs to be enabled Field log required Should you required field level audit logs in FLEXCUBE STTB_FIELD_LOG 7 4 Data Source Repeat the below table for every Data source added Specification Data Data source name Fill up the Data source name Follow the FLEXCUBE naming conventions for data source entities Is it Master When multiple data sources used in a screen one has to be Mater type Accordingly select Yes No Relation type This defines detail to parent relationships when multiple data sources used Define one of the below accordingly e Oneto One e Oneto Man Is it Multi Record data source This defines if multiple records to be shown on screen Parent This defines the parent data
26. source for this multiple record data source 7 3 ORACLE Specification Data Relation This defines the relation KEYs between the data sources It refers the columns use to join tables Where clause Specify where clause Default order by Specify Default Order by clause Type of Data source Pick e Normal e Query e InOnly e Summary PK Cols This should get defaulted Otherwise specify in tilde separated format PK Types This should get defaulted Otherwise specify in tilde separated format 7 5 Data Source Columns Repeat the below table for every column under every Data Block added Specification Data Column Name Specify the column name Max Length It is optional to change Max length to input at field 7 6 LOV Repeat the below table for every LOV added Specification Data LOV Name Specify LOV name 7 4 ORACLE Specification Data LOV Query Specify LOV Query 7 7 Data Block Repeat the below table for every Data Block added Specification Data Block Name Specify block name Follow naming convention Block Title Specify Block Title Parent Specify the Parent Block incase if this is multi record detail block Relation Type Pick e One to One e One to Many XSD Node Specify the name to be used in XSD for Web service types Follow the naming convention
27. tegration Outbound Notification trigger development Notification Development Extensibility Getting started Getting started Extensibility Reference guide Extensibility Reference Guide Extensibility use case development examples Extensibility By Example 10 1 ORACLE 11 Appendices This section documents the specification for STDACPER function ID 11 1 Preparation Check List Specification Data Tables Views created in Database Yes No Yes Tables Views should be created in Database Primary Key populated at STTB_PK_COLS Yes No Yes Primark Key details should be defined in STTB_PK_COLS The data can be inserted using Oracle DML commands Column Name population at CSTB_DATA_DICTIONARY done Yes No Yes Column names should be defined in CSTB_DATA_DICTIONAY The data can be inserted using Oracle DML commands Label descriptions populated at CSTB_LABELS Yes No Yes Label descriptions need to be populated at CSTB_LABELS for a given language that screen is developed Default language to be used for screen is English Database Schema name linked with Open Development tool FCPB1121 Your Open Development tool needs to be configured with the Oracle FLEXCUBE Application Database schema where the tables views created 11 2Basic Specification Data Action Pick Action e New e Load New Function Type Pick Function Type
Download Pdf Manuals
Related Search