Oracle Applications Forms

To design or develop the form with Applications Standards, Package provided a Standard Form called APPSTAND.fmb

--------------------------------------------------------------------------------

RE: What can we find TEMPLATE.FMB file ?

--------------------------------------------------------------------------------

If you want to develop and new form in Oracle Applications we develop it by using the Template.fmb.

--------------------------------------------------------------------------------

RE: What is the difference between Customization and Personalization?

--------------------------------------------------------------------------------

Customization means making few changes according to client requirement to an already existing product. Personalization means complete development on front end and back end.

--------------------------------------------------------------------------------

What are forms customization steps ?

--------------------------------------------------------------------------------

The steps are as follows :·

Copy the template.fmb and Appstand.fmb from AU_TOP/forms/us.Put it in custom directory. The libraries (FNDSQF, APPCORE, APPDAYPK, GLOBE, CUSTOM, JE, JA, JL, VERT)

NEW FORM DEVELOPMENT

To enable the end user to operate the Forms user friendly we need to standardize the Forms. To design or develop the form with Applications Standards, Package provided a Standard Form called APPSTAND.fmb

APPSTAND.fmb: is a collection of the entire standard object Groups used in the Oracle Applications. Form should inherit the following object Group Properties

1. STAND_PC_AND_VA: This consists of Windows, Canvases, Blocks and Items used for Property Classes and Visual Attributes.

2. STAND_TOOLBAR: This consists of Windows, Canvases, Blocks and Items used for Tool Bars.

3. STANDARD_CALENDER: This consists of Windows, Canvases, Blocks and Items used for Calendars.

4. STANDARD_FOLDER: This consists of Windows, Canvases, Blocks and Items used for Data Restriction and Changing the Layout of the Form at run time. And this is not used for Custom Forms).

5. QUERY_FIND: This consists of Windows, Canvases, Blocks and Items used for implementing find windows or Search methods.

6. LIBRARIES:

APPCORE.PLL: is the collection of Procedures, Functions and Packages used to define Menus and Tool Bars. And Application Standards

FNDSQF.PLL: is the collection of Procedures, Functions and Packages used to define Special Objects like KFF, DFF, Form Functions and Non-Form functions and also Descriptive Flexfields, Currency,Concurrent Request Submission,It Will support for al the Flexfield,profile,WHO Columns functionality.

APPDAYPK.PLL: is the collection of Procedures, Functions and Packages used to define Calendars and Calendar popup, It will Support for All CAlendar and Date time Functions

CUSTOM.PLL: is the collection of Procedures, Functions and Packages used to customize the Forms with out modifying the code of Oracle Applications and Customizations of standard forms

Note: The Built-ins of CUSTOM.PLL are internally called by the Built-ins of APPCORE.PLL and the

Built-ins of APPCORE.PLL are called by few Triggers like
WHEN-NEW-FORM-INSTANCE,
WHEN-NEW-RECORD-INSTANCE,
WHEN-NEW-ITEM-INSTANCE,
PRE-BLOCK,
PRE-RECORD,
PRE-ITEM

APPCORE2.PLL: is a Duplicate/Replica of APPCORE.PLL. It has the same Built-ins as APPCORE.PLL and this is used in CUSTOME.PLL

GLOBE.PLL: is used to change the regional settings of the Package with out modifying the code of Applications. GLOBE.PLL internally calls the Built-ins of JE.PLL, JL.PLL and JA.PLL Libraries and Global or regional features.

JE.PLL: is used to change the regional settings of Middle East Countries like Europe/Middle East/Africa features.

JA.PLL: is used to change the regional settings of Asia Pacific Countries.

JL.PLL: is used to change the regional settings of Latin America.

FORM TEMPLATE.fmb:

It is used to develop the new Form of a Business Application.

1.TEMPLATE.fmb inherits all the Object Groups of APPSTAND.fmb.
2. Attaches all the Libraries.
3. Attaches Standard Menu called FNDMENU.mmb.

4.Creates Form level Triggers. Some of these Triggers are read only and some are read and write. Read only triggers are marked with RED Colour and Read and Write triggers are marked with BLUE Colour.

5. APPS_CUSTOM Package is a collection of OPEN_WINDOW(WND IN VARCHAR2) and OPEN_WINDOW(WND IN VARCHAR2) Procedures. These are created by default when we open the TEMPLATE.fmb Form.

If you want to open the TEMPLATE.fmb form, make sure you have the following forms, libraries, copied over as well from the $AU_TOP/forms/ and $AU_TOP/resource directories:

APPSTAND.fmb
APPCORE.pll
APPCORE2.pll
APPDAYPK.pll
CUSTOM.pll
FNDSQF.pll
GHR.pll
GLOBE.pll
GSM.pll
JA.pll
JE.pll
JL.pll
VERT.pll --specific industry features
OPM.pll
PQH_GEN.pll
PSA.pll
PSAC.pll
PSB.pll
IGILUTIL.pll
IGILUTIL2.pll

Description of Libraries attached with Template.fmb

LIBRARY-Core

1) APPCORE.pll ----Application Standards, toolbar

2)VERT.pll ----Specific industry features

3)GLOBE.pll ----Global or regional features

4) JA.pll ----Asia/Pacific features

5) JE.pll----- Europe/Middle East/Africa features

6) JL.pll ----Latin America Code

7) CUSTOM.pll ---------Customizations of standard forms

8) FNDSQF.pll ------Flexfields, Profiles, Currency, Concurrent Request Submission, Record History, Message Dictionary

9)APPDAYPK.pll -----Calendar

10) APPFLDR.pll -----Packages for Folder Blocks

Libraries – Application Specific to TEMPLATE.fmb

(1) FV.pll --Federal Financials

(2) HRKPI.pll ----Human Resources Knowledge Provider

(3) GHR.pll ---Global Human Resources

(4) GMS.pll ---Encumbrances

(5) IGILUTIL.pll--- International Public Sector

(6) IGILUTIL2.pll ---International Public Sector

(7) PSAC.pll ----Public Sector Applications

(8) PQH_GEN.pll ----Public Sector Human Resources

(9) PSA.pll ---Public Sector Applications

(10) PSB.pll ---Public Sector Budgeting

(11) OPM.pll---- Process Manufacturing

(12) APPCORE2.pll ----Application standards (for CUSTOM.pll)

• Oracle does not support the use of APPFLDR, VERT, GLOBE, PSAC, PQH_GEN, GHR, JA, JE and JL for custom forms

(*) NEVER MODIFY ORACLE APPLICATIONS LIBRARIES OTHER THAN CUSTOM.pll*

APPCORE: APPCORE contains the packages and procedures that are responsible for the standard ‘Oracle Applications’ behavior of the forms. The forms have to support the menu, toolbar, and other required standard behaviors in compliance with oracle applications. The Oracle Applications forms also have to display specific runtime behaviors in accordance with the Oracle Applications Interface Standards, such as the way in which fields are enabled, behaviors of specific types of windows etc. APPCORE contains the procedures to support this standard runtime behavior. APPCORE also contains various other utilities for exceptional handling, message levels, and so on.

GLOBE: The GLOBE library allows Oracle Applications developers to incorporate global or regional features into Oracle Applications forms without modification of the base Oracle Applications form. Oracle Applications sends events to the GLOBE library. Regional code can take effect based on these events. The GLOBE library calls routines in the JA, JE, and JL libraries.

JE: The JE library contains code specific to the EMEA (Europe/ MiddleEast/ Africa) region and is called by the GLOBE library.

FNDSQF: FNDSQF contains packages and procedures for Message Dictionary, flexfields, profiles, and concurrent processing. It also has various other utilities for navigation, multicurrency, WHO, etc.

JL: The JL library contains code specific to the Latin America region and is called by the GLOBE library.

JA: The JA library contains code specific to the Asia/Pacific region and is called by the GLOBE library.

VERT: The VERT library allows Oracle Applications developers to incorporate vertical industry features (for automotive, consumer packaged goods, energy, and other industries) into Oracle Applications forms without modification of the base Oracle Applications form. Oracle Applications sends events to the VERT library. Vertical industry code can take effect based on these events. The VERT library calls routines in various other libraries.

GHR: The GHR library contains code specific to Event Dispatcher for HRMS Localization

APPCORE2: There is no basic difference between appcore.pll and appcore2.pll. Appcore2.pll is a replica of appcore.pll. While using custom.pll we can't reference appcore.pll as it cause cross reference problem so to use appcore.pll in custom.pll we make use of appcore2.pll

HRKPI: This HRKPI library contains packages for humary resource knowledge provider. If the HR_STAND is attached with the form, then this may be must.

PQH_GEN.pll The PQH_GEN library contains code specific to Public Sector Human Resources

PSAC.pll The PSAC library contains code specific to Public Sector Applications

PSB.pll The PSB library contains code specific to Public Sector Budgeting

PSA.pll The PSA library contains code specific to Public Sector Applications

GMS.pll The GMS library contains code specific to Encumbrances

FV.pll The FV library contains code specific to Federal Financials

IGILUTIL.pll The IGILUTIL library contains code specific to International Public Sector

IGILUTIL2.pll The IGILUTIL2 library contains code specific to International Public Sector

OPM.pll The OPM library contains code specific to Process Manufacturing

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.