1. Development of Maintenance Form
  2. Generated Units

16 Generated Units

This topic provides an overview of generated units for a Maintenance screen.

The following units will be generated for a Maintenance screen. Refer to document Development Workbench- Screen Development II for a detailed explanation on the same.

Front End Units

Table 16-1 Front End Units

Front End Units Description
Language XML This file is an XML markup of presentation details, for the designed Call Form specific to a language.
SYS JavaScript File This JavaScript file mainly contains a list of declared variables required for the functioning of the screen.
Release Type Specific JavaScript File This file won’t be generated by the Tool. It has to be manually written by the developer if he has to write any code specifically in that release.

Data Base Units

Table 16-2 Data Base Units

Data Base Units Description
Static Scripts The following static scripts generated are required for the proper functioning of a Call Form screen. Refer document on generated units for a detailed explanation.
  1. Menu Details

    Scripts for SMTB_MENU and SMTB_FCC_FCJ_MAPPING, SMTB_ROLE_DETAIL, SMTB_FCC_GCJ_MAPPING are required for the functioning of Maintenance screen.

  2. LOV Details
  3. Amendable Details
  4. Label Details
  5. Screen Details
  6. Block Details
  7. Data Source Details
  8. Call form Details
  9. Summary Details
System Packages The Main Package contains the basic validations and backend logic for the Maintenance function ID. The main package contains the mandatory checks required. It will also contain function calls to the other packages generated by Workbench. The main package has the below stages for a maintenance form:
  • Converting Ts to PL/SQL Composite Type
  • Checking for mandatory fields
  • Defaulting and validating the data
  • Writing into Database
  • Querying the Data from the database
  • Converting the Modified Composite Type again to TS
Each of these stages has Pre and Post hooks in the Kernel, Cluster, and Custom Packages. And these Hooks are called from the Main Package itself. Main Package has the system-generated code and should not be modified by the developer. Kernel, Cluster, and Custom Packages are the packages where the respective team can add business logic in appropriate functions using the Pre and Post hooks available.
Hook Packages Release-specific packages will be generated based on the release type (KERNEL, CLUSTER or CUSTOM). The developer can add his code in the release-specific hook package. The Main Package has designated calls to these Hook Packages for executing any functional checks and Business validations added by the user. The structure for all the Hook Packages are the same, like:
  • Fn_Post_Build_Type_Structure
  • Fn_Pre_Check_Mandatory
  • Fn_Post_Check_Mandatory
  • Fn_Pre_Default_and_Validate
  • Fn_Post_Default_and_Validate
  • Fn_Pre_Upload_Db
  • Fn_Post_Upload_Db
  • Fn_Pre_Query
  • Fn_Post_Query
These functions are called from the Main package using the Pre and Post Hooks available in the Main Package. The 3 Hook Packages namely Kernel, Cluster, and Custom Packages have a similar structure and are for the respective teams to work on.

Other Units

XSD: XSD's will be generated if gateway operations are required for the particular function ID. Maintenance for the same has to be done in the Actions node.