, , ,

Develop Custom Forms in Oracle Applications

Overview of the Template Form

The TEMPLATE form is the starting point for all development of new forms. The first step in creating a form for use in Oracle Applications is to copy the template form from $AU_TOP/forms/US, to a local directory and renaming it.

The Template form is unique because it contains some special libraries and triggers that render the application using the template form some standard characteristics. The components of the template form are:

  • References to object groups: The template form contains platform–independent references to predefined standard object groups in the APPSTAND form(STANDARD_PC_AND_VA,STANDARD_TOOLBAR, and STANDARD_CALENDAR).
  • Libraries: The template form contains platform–independent attachments of several libraries (including FNDSQF, APPCORE, and APPDAYPK).
  • Special triggers: The template form contains several form–level triggers with required code. These are responsible for standard the behavior of the form.
  • Predefined Program Units: The template form contains predefined program units that include a spec and a body for the package APP_CUSTOM, which contains default behavior for window opening and closing events.
  • Applications Color Palette: The template form contains the application color palette. This gives the forms developed using the template form the look and feel of Oracle applications.
  • Many referenced objects (from the object groups) that support the Calendar, the toolbar, alternative regions, and the menu. These objects include LOVs, blocks, parameters, and property classes, and so on.
  • The TEMPLATE form contains sample objects that can be seen as examples for the expected layout cosmetics. These samples can be completely removed from theform later as they are only examples and are not required. The following objects are the samples and can be removed:
    • Blocks: BLOCKNAME, DETAILBLOCK
    • Window: BLOCKNAME
    • Canvas–view: BLOCKNAME
Hence, the template form comes along with many attachments, predefined program units, and defined visual attributes as well as examples that not only give the forms that are developed using the template.fmb a standard look and feel, but also make it easier to develop forms with consistent and standard functionality.
/by