Search Results fnd_form_functions_n4

Overview

APPLSYS.FND_FORM_FUNCTIONS is a core Oracle Application Object Library (FND) seed table that defines the subdivisions of Oracle EBS forms into separately callable functionality groups. Each row represents a single function — a named entry point that a form can expose — and records the owning application, the parent form, and the runtime parameters used to invoke it. Oracle EBS uses this information to implement form-level segmentation through the existing menu and responsibility framework, so that a responsibility can be granted access to a subset of a form's capability rather than the entire form. The metadata notes that the underlying view construct is applicable to Oracle Applications in GUI mode.

The object carries a Status of VALID with FND Design Data FND.FND_FORM_FUNCTIONS, and is stored in the APPS_TS_SEED tablespace — a placement consistent with seeded, shipped configuration data. Heuristic Data Vault classification mined from the foreign-key structure identifies FND_FORM_FUNCTIONS as a hub. As a modeling suggestion, this reflects its role as a stable catalogue of business keys (function identity) around which dependent relationships and descriptive attributes cluster, rather than a transactional or link entity.

Key Information Stored

The documented schema in 12.2.2 contains 37 columns. The most significant for identification and runtime behavior are:

• FUNCTION_ID — Numeric surrogate primary key (FND_FORM_FUNCTIONS_PK). Also the leading column of unique index FND_FORM_FUNCTIONS_U1, which is documented as (FUNCTION_ID, ZD_EDITION_NAME).
• FUNCTION_NAME — The function name, VARCHAR2(480), and the basis of the second unique business key, FND_FORM_FUNCTIONS_U2 (FUNCTION_NAME, ZD_EDITION_NAME).
• APPLICATION_ID — The owning application; foreign key to FND_FORM.
• FORM_ID — The parent form this function belongs to.
• PARAMETERS — VARCHAR2(2000) call parameters passed when the function invokes its form.
• TYPE — Function type (VARCHAR2(30)); indexed by FND_FORM_FUNCTIONS_N2.
• OBJECT_ID — Foreign key to FND_OBJECTS; indexed by FND_FORM_FUNCTIONS_N4.
• WEB_HOST_NAME / WEB_AGENT_NAME — Web server host or alias and agent used for web-deployed invocations.
• WEB_HTML_CALL, WEB_SECURED, WEB_ICON — Web rendering and security attributes.
• IREP_CLASS_ID — Integration repository class reference; indexed by FND_FORM_FUNCTIONS_N3.
• REGION_APPLICATION_ID, REGION_CODE — Region linkage for the function.
• MAINTENANCE_MODE_SUPPORT, CONTEXT_DEPENDENCE — Behavioral flags governing runtime treatment.
• Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• ZD_EDITION_NAME — Edition discriminator appearing in both unique keys.

Common Use Cases and Queries

Typical scenarios include auditing which functions belong to a form, tracing responsibility grants to form segments, and reconciling menu entries against defined functions.

• Resolve a function by its business key: SELECT FUNCTION_ID, FORM_ID, PARAMETERS FROM APPS.FND_FORM_FUNCTIONS WHERE FUNCTION_NAME = :name;
• List all functions for a given form: SELECT FUNCTION_ID, FUNCTION_NAME FROM APPS.FND_FORM_FUNCTIONS WHERE FORM_ID = :form_id ORDER BY FUNCTION_NAME;
• Cross-check responsibility assignments: join FND_RESP_FUNCTIONS.ACTION_ID to FUNCTION_ID to determine which responsibilities expose a function.
• Report menu-to-function linkage through FND_MENU_ENTRIES.FUNCTION_ID.
• Identify Integration Repository-backed functions using IREP_CLASS_ID and the N3 index.

Related Objects

• FND_FORM — parent form; joined via APPLICATION_ID/FORM_ID.
• FND_OBJECTS — joined via OBJECT_ID.
• FND_FORM_FUNCTIONS_TL — translated function names, joined on FUNCTION_ID.
• FND_MENU_ENTRIES — menu placement of functions, joined on FUNCTION_ID.
• FND_RESP_FUNCTIONS — responsibility-to-function grants, joined via ACTION_ID.
• FND_ATTACHMENT_FUNCTIONS — attachment enablement per function.
• UMX_REG_SERVICES_B — registration services, joined via REG_FUNCTION_ID.
• ICX_SESSIONS — session tracking, joined via FUNCTION_ID.
• OKE_ROLE_FUNCTIONS — role-based function access, joined via FUNCTION_ID.
• PA_OPTIONS / PA_PAGE_LAYOUTS — personalization references by FUNCTION_NAME.