3 Header Information

This topic provides systematic instructions to update header information.

1. Login to the Oracle FLEXCUBE Universal Banking ODT using the credentials maintained.
   Refer Development Workbench – AdministrationDevelopment Workbench – Administration for creating users.
2. Map the session to the release and environment as required
   Refer Development Workbench – Getting Started for detailed explanation.
3. Click on Function Generation node in the browser tree found in the Landing page of ODT.
   Function Generation screen displays.

   Figure 3-1 Function Generation

   
   

   
   Description of "Figure 3-1 Function Generation"

   
   
4. On Function Generation screen, specify the following.

   Table 3-1 Function Generation - field Description

   Field	Description
   Action	New and Load options are provided for this field. For a new screen development, select the action as New; if an existing screen radxml has to be loaded for customization select Load option. If the action is load then corresponding radxml has to be loaded using browser option in Save Xml Path; all the header information will get populated
   Function Id	If the Action is selected as New, the function Id name needs to be specified. Function Id is the unique name with which a screen is identified. Function Id name should follow the FLEXCUBE standard naming convention. Function Id name to have maximum length of 8 characters For detail screens the third character should be D For report screens the third character should be R For call form function ids the third character should be C First 2 characters should specify the module name for which the particular function id is used.
   Function Type	Function Type can be Parent or Child or Screen Child (based on the screen which has to be designed). For more information on the unresolvable-reference.html#GUID-2366F332-D7AE-4EFD-9D92-7DD820BC1155__TABLE_BLS_JSM_4WBtable.
   Parent Function	This field is applicable only if the function type is child/screen child and this field will be populated when the parent RAD xml is loaded. This is a read only field.
   Save Xml Path	The label description of the field will change depending on the action .If the action is load, ODT attaches a Browse button to it so that user can browse the radxml and load it. If the action is New, save xml path is optional. If provided, then the generated units will be saved in the path mentioned. Note that the value in the Save Xml Path will be used only if the Save Format is Client Path and if the User has given “CURRENT_DIRECTORY” in the User PreferencesWork Directory.
   Parent Xml	This field is also applicable only if the Function type is child/screen child. If the Function Type is child/screen child user has to load the radxml of the Parent Function using browse button provided to this field. It is non editable field if the action is Load.
   Function Category	Provide Function category depending on the type of screen being developed. ODT provides the following options: For more information on the filed, refer to the unresolvable-reference.html#GUID-2366F332-D7AE-4EFD-9D92-7DD820BC1155__TABLE_MYD_3QM_4WB table.
   Header Template	A template can be selected for header. The following options are provided.
   Footer Template	A template can be selected for footer. The following options are provided. For more information on the field, refer to the unresolvable-reference.html#GUID-2366F332-D7AE-4EFD-9D92-7DD820BC1155__TABLE_KHS_XTM_4WB table.

   Table 3-2 Function Type

   Field	Description
   Parent	This is the default option and can be used for normal screen development.
   Child	This option can be selected if the screen has to be the child of another screen .i.e. inherits all the properties of another screen which will be its parent. Properties can be modified in the child level.
   Screen Child	This option can be selected if the screen has to be the screen child of another screen, i.e. it inherits all properties from its parent. Only screen layout changes can be done in the screen child screen.

   Table 3-3 Function Category

   Field	Description
   Maintenance	These screens are typically used to maintain static data used across the system. These screens include product definition function as well. Example: Branch Parameters Maintenance
   Transaction	These screens are typically used to capture contract related data. Any operations related to contracts are performed in these screens Example: Funds Transfer Contract Input screen
   Report	These screens are used to capture data required to generate a BI Publisher canned reports. Example: General Ledger balance report
   Summary	If only query operation is required for the particular function Id, then function category can be selected as summary.
   Others	If developer feels that existing handles provided in maintenance/transaction screens in extensible framework is inadequate (or not necessary) for the screen; screen can be designed as others. Note that all business logic would have to be manually written by the developer for others screen.

   Table 3-4 Header Template

   Field	Description
   None	This is the default header and should be used for all screens except workflow screens.
   Process	This template can be selected for workflow screens. The following Fields will be added to the header section as part of this template. Workflow Reference Priority

   Table 3-5 Footer Template

   Field	Description
   None	This is the default value.
   Maint audit	This template can be used for maintenance screens. Ensure that master data source has the standard audit columns. Audit block field names are reserved filed names and hence cannot be used as the name of any other block field. For more information on the field, refer to the unresolvable-reference.html#GUID-2366F332-D7AE-4EFD-9D92-7DD820BC1155__TABLE_N53_NVM_4WB table. Note: When template is selected, ODT automatically adds the fields to Data Source and Blocks and adding these fields manually to data blocks results in erroneous behavior.
   Maint Process	In this template along with maintenance audit fields System would automatically add a control block and Process related fields. This template can be used for workflow maintenance screens.
   Process	Only process related Fields will be added to the Footer. This can be used for work flow transaction screens. As part of process template; previous remarks, remarks, outcome and audit block will be created in the footer.

   Table 3-6 Audit column and corresponding block fields

   Column Name	Block Field Name
   MAKER_ID	MAKER
   MAKER_DT_STAMP	MAKERSTAMP
   CHECKER_ID	CHECKER
   CHECKER_DT_STAMP	CHECKERSTAMP
   MOD_NO	MODNO
   RECORD_STAT	RECSTAT
   ONCE_AUTH	ONCEAUTH
   ONCE_AUTH	AUTHSTAT

   For example, For Funds Transfer Contract Input Screen name can be given as FTDTRONL Here FT is the module (Funds Transfer), third letter D denotes it is a normal detail screen, and Length of the function Id is 8.

   If the action selected is Load, function Id field will be disabled. It will be picked up from the radxml which is loaded.