Search Results amw_constraint_entries

Overview

The FND_FORM_FUNCTIONS table is a core repository within the Oracle E-Business Suite (EBS) Application Object Library (FND). It serves as the master definition table for all executable functionalities, known as "form functions," across the application. A form function is a logical grouping of functionality that can be assigned to menus and secured via responsibilities. It acts as a critical abstraction layer, representing the executable target of a menu entry, which can be an Oracle Forms application, a web page (OA Framework), a concurrent program, or a custom web application. Its primary role is to centralize the definition of all navigable points in EBS, enabling consistent security, auditing, and menu management.

Key Information Stored

The table stores metadata that defines each function's identity, type, and behavior. While the provided metadata does not list all columns, the primary and foreign keys reveal its core structure. The FUNCTION_ID is the unique numeric primary key, and FUNCTION_NAME is the unique textual identifier. The table links to the FND_FORM table via APPLICATION_ID and FORM_ID for Oracle Forms-based functions. Crucially, it integrates with the EBS object security model via the OBJECT_ID foreign key to FND_OBJECTS. Other typical columns (inferred from standard implementation) include TYPE (to distinguish between FORM, SSWA, JSP, etc.), PARAMETERS (for passing arguments), WEB_HOST_NAME, and WEB_AGENT_NAME for web-based functions.

Common Use Cases and Queries

This table is central to security audits, troubleshooting navigation issues, and generating application inventories. Common queries include identifying all functions available to a specific responsibility, finding the definition of a non-working menu item, or listing all functions of a particular type. For example, to find the definition and associated form for a specific function name:

• SELECT fff.function_name, fff.function_id, ff.form_name, ff.user_form_name FROM fnd_form_functions fff, fnd_form ff WHERE fff.form_id = ff.form_id AND fff.application_id = ff.application_id AND fff.function_name = 'MY_FUNCTION_NAME';

Another critical use case is analyzing function security exclusions via the FND_RESP_FUNCTIONS table, which references FND_FORM_FUNCTIONS.ACTION_ID (a synonym for FUNCTION_ID).

Related Objects

As indicated by the extensive foreign key relationships, FND_FORM_FUNCTIONS is a foundational table referenced by numerous EBS modules. Key related objects include:

• FND_MENU_ENTRIES: Links functions to menu structures.
• FND_RESP_FUNCTIONS: Stores responsibility-level function security exclusions.
• FND_FORM_FUNCTIONS_TL: The translated table for user-facing function names.
• FND_OBJECTS: For integration with the EBS object security and auditing framework.
• ICX_SESSIONS: Tracks the current function in a user session for auditing.
• Module-Specific Tables: Such as AMW_CONSTRAINT_ENTRIES (Audit), CSC_PROF_MODULE_GROUPS (Service), and PA_PAGE_LAYOUTS (Projects), demonstrating its use in configuring module-specific features.