Search Results fnd_form_functions_pk

Overview

FND_FORM_FUNCTIONS is the core registration table in the Oracle E-Business Suite Application Object Library (FND) that defines functions — the elementary units of functionality that can be secured, executed, or invoked by a user session. Owned by the APPLSYS schema, this table holds the definition of functionality groupings that range from a form invocation, a web HTML page, a JSP, a subfunction call, or a Java Bean based invocation. In Oracle EBS 12.1.1 and 12.2.2 it functions as the central catalog of executable application entry points referenced throughout menus, responsibilities, permissions, and page-level security models.

From a data modeling perspective, the metadata classifies FND_FORM_FUNCTIONS heuristically as a hub. This is a modeling suggestion: the table acts as the durable business concept registry for functions, keyed by a stable surrogate identifier, with satellites (FND_FORM_FUNCTIONS_TL and the many dependent page/permission tables) holding descriptive and translateable attributes. Designing downstream reporting or integration models on this hub-and-satellite pattern is consistent with its role.

Key Information Stored

The table is physically defined with 37 columns. The most significant columns and their meaning are:

• FUNCTION_ID — Surrogate primary key (FND_FORM_FUNCTIONS_PK) uniquely identifying each function.
• FUNCTION_NAME — The business-key candidate. Indexed by FND_FORM_FUNCTIONS_U2, this is the internal lookup name used across the application.
• APPLICATION_ID — Identifies the owning application; validated against FND_FORM. Together with FORM_ID it locates the function's form.
• FORM_ID — Foreign key to FND_FORM, the form associated with this function.
• TYPE — The function type (e.g., Form, Subfunction, JSP, WWW, HTML).
• OBJECT_ID — Foreign key to FND_OBJECTS, linking the function to a permission/authorization object.
• PARAMETERS — Default parameters passed when the function is invoked.
• WEB_HTML_CALL — The URL or call target used for web-based function types.
• WEB_HOST_NAME / WEB_AGENT_NAME / WEB_SECURED / WEB_ENCRYPT_PARAMETERS — Attributes controlling web invocation security and routing.
• REGION_APPLICATION_ID / REGION_CODE — Identify the OA Framework region rendered for the function.
• MAINTENANCE_MODE_SUPPORT / CONTEXT_DEPENDENCE — Behavioral flags governing availability during patching and context-sensitive display.
• IREP_* columns — Metadata for Integrated SOA Gateway (iRep) exposure, including method name, scope, lifecycle, direction, and XML descriptions.
• ZD_EDITION_NAME — Editioning column supporting Online Patching in 12.2.2 and participation in unique indexes FND_FORM_FUNCTIONS_U1/U2.

Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are standard who-columns. The surrogate key FUNCTION_ID is distinct from the business key FUNCTION_NAME, which is the practical reference used by integration tables such as PA_OBJECT_PAGE_LAYOUTS.

Common Use Cases and Queries

Typical uses include auditing function-to-menu assignments, tracing responsibility access, and validating references stored as function names by sub-modules such as Projects (PA_OBJECT_PAGE_LAYOUTS.PERS_FUNCTION_NAME). A representative query lists functions of a given type:

SELECT function_id, function_name, type, web_html_call
  FROM applsys.fnd_form_functions
 WHERE type = 'WWW'
 ORDER BY function_name;

Because several tables store the function name rather than the ID, a join keyed on FUNCTION_NAME is common:

SELECT p.object_name, f.function_id, f.function_name
  FROM pa_object_page_layouts p
  JOIN applsys.fnd_form_functions f
    ON f.function_name = p.pers_function_name;

Reporting scenarios frequently require reconciling FND_MENU_ENTRIES and FND_RESP_FUNCTIONS back to this central catalog to determine which responsibilities expose which executable functions.

Related Objects

Numerous tables depend on this hub. The most significant relationships include:

• FND_FORM_FUNCTIONS_TL — Joined on FUNCTION_ID; holds translated display names and descriptions.
• FND_MENU_ENTRIES — Menu entries referencing each function via FUNCTION_ID.
• FND_RESP_FUNCTIONS — Responsibility-to-function security mapping via ACTION_ID.
• FND_FORM — Parent form referenced through APPLICATION_ID and FORM_ID.
• FND_OBJECTS — Permission object referenced through OBJECT_ID.
• PA_OBJECT_PAGE_LAYOUTS and PA_PAGE_LAYOUTS — Join on PERS_FUNCTION_NAME to FUNCTION_NAME.
• PA_OPTIONS and PA_PAGE_TYPE_REGIONS — Reference function names for personalization and page security.
• FND_ATTACHMENT_FUNCTIONS and UMX_REG_SERVICES_B — Attachment and user-management registration via FUNCTION_ID.

These relationships confirm FND_FORM_FUNCTIONS as the authoritative registry underpinning security, menus, and page-level control across Oracle EBS.