Basic elements(Application,Forms,functions,menu) of Oracle EBS Application

Here in this post,I am trying to explain the Basic elements(Application,Forms,functions,menu) of Oracle EBS Application

-An Application is a collection of Forms,Reports and PL/SQL objects to meet a particular business objectives
-Oracle Applications like 11.0,11i,R12 is a collection of predefined inter linked applications
-A custom application can be designed and integrated with Oracle Applications
-Any custom application has to be registered with Oracle Applications
– Custom application can be defined using the

Responsibility: System Administration
Navigate to Application–>Register

Application = XPROD Custom
Short Name = XPROD
Basepath = XPROD_TOP
Description = XPROD Custom Application

  • The below query can be used to query application information through sqlplus

set linesize 1000
column application_id format a999999 heading “APPL|ID”
column application_short_name format a10 heading “APPL|SHORT NAME”
column application_name format a50 heading “APPLICATION NAME”
column language format a4 heading “LANG”
select a.application_id,
from fnd_application a,
fnd_application_tl at
where at.application_id = a.application_id
and at.language=’US’
group by a.application_id,a.application_short_name,a.basepath,at.application_name,at.language
order by a.application_id

  • The following are the components of an application
    Concurrent program
    Request Group
    Request Set
    Standard Report Submission

-form is a user interface to insert ,update and delete data into and from database
-While developing Oracle Applications form , we follow some development standard
-After development , a form must be registered with Oracle Application Object Library
-FND_FORMS is a table in APPLSYS schema that stores information about forms
-Custom forms needs to be registered in Application
-Custom Form can be defined using the

Responsibility:- System Administrator
Navigation Path ->Application ->Forms

-Form Function:A function that invokes an Oracle Forms form
-Sub Function:A non form function is a securable subset of forms functionality , which means a function executed from within a form
-One can navigate to a form function ( form) using the navigate window
-A sub function can only be run from a form
-FND_FORM_FUNCTIONS is a table in APPLSYS schema that stores information about function grouping in forms. Each row includes a function identifier, the function name,and the application identifier. Each row also includes the form identifier and the parameters for calling the form. You need one row for each function. Oracle Application Object Library uses this information to implementation the subdivision of forms into different functionality groups using the existing menu system. This view is only used for Oracle Applications in GUI mode.
Important Columns in FND_FORM_FUNCTIONS  table
· FUNCTION_ID – Function identifier
· FUNCTION_NAME – Function name
· WEB_AGENT_NAME – Name of Oracle Web Agent. Defaults to the last agent used
· WEB_HTML_CALL – Contains the URL to activate this function. It may be either a static page or a procedure. If the value here is incorrect then users will not be able to launch those form functions from Self Service Web Applications.
-Custom Functions can be defined using the

Responsibility:- System Administrator
Navigation Path ->Application ->Functions


It is a logical or hierarchical listing of functions (forms) so that the user can easily navigate through the forms once he is in a responsibility.

A menu is a hierarchical arrangement of functions and menus of functions that appears in the Navigator. Each responsibility has a menu assigned to it.
Every responsibility will be assigned only one main menu. Under that main menu, you can have either other sub menus or functions.

Note: Define any menus that you intend to call from your menu. Define the lowest-level submenus first. A submenu must be defined before it can be called by another menu.

-Custom Menu can be defined using the

Responsibility:- System Administrator
Navigation Path ->Application ->Menu



The information is stored in FND_MENU table.

This table compiles the information from FND_MENU_ENTRIES to facilitate runtime lookups of which functions are on which menus. It collapses the  hierarchy of FND_MENU_ENTRIES into a flat format. It is populated (compiled) by the FND_FUNCTION package. It also contains marks of which menus are compiled, meaning fnd_compiled_menu_functions has different information from fnd_menu_entries. Any code that manipulates
FND_MENU_ENTRIES should fire the database triggers on it that mark rows as uncompiled. A row with function_id -99999 indicates that a particular menu is uncompiled (cannot be trusted) and code should look directly at fnd_menu_entries. Also note that fnd_compiled_menu_functions does not take exclusions into account, so if there are exclusions on a particular resp then fnd_menu_entries needs to be processed directly.

Step1 Get the Menu name from Menu Define screen (From Application)
Step2 Get the Menu_id from fnd_menus table
SQL> select MENU_ID,MENU_NAME from fnd_menus where MENU_NAME=’&menu_name’;

The whole process of defining custom application in Oracle EBS environment is given in below link

How to define custom application in R12

Related Articles

Introduction to R12

40 question you must know about R12.2

Service Group changes in R12.2

How to change the Web Port in EBS 12.2

Leave a Reply