Search Results irep_class_id

Overview

FND_FORM_FUNCTIONS_VL is a valid, public view owned by the APPS schema in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It belongs to the FND – Application Object Library product, also known as Application Object Library (AOL). The view exposes the definition of every registered function in the EBS instance, combining the language-independent function attributes stored in FND_FORM_FUNCTIONS with the translated, user-facing text stored in FND_FORM_FUNCTIONS_TL.

Functions form the foundation of EBS security and menu architecture. Each function represents a navigable target — a form, an OAF page, a JSP, a web HTML call, a SubFunction, or a non-navigable utility — and is attached to menus, responsibilities, and request groups. Because FND_FORM_FUNCTIONS_VL provides the function name, description, type, and the web or form execution attributes in a single translated result set, it is the primary source for reporting on function definitions, validating menu/responsibility configurations, and auditing security. The "_VL" suffix signals that the view returns translated text filtered to the session language, rather than the multi-language, union-style "_TL" table.

Underlying Base Objects

The view is defined over two documented base objects, both referenced in ETRM as synonyms resolvable from the APPS schema:

• FND_FORM_FUNCTIONS — the primary, language-independent table holding one row per function, including identifiers, web attributes, and iRep (integration repository) metadata.
• FND_FORM_FUNCTIONS_TL — the translation table holding USER_FUNCTION_NAME and DESCRIPTION per installed language.

The join key is FUNCTION_ID, and the language is constrained by the SQL predicate T.LANGUAGE = USERENV('LANG'), ensuring each query returns only the rows for the caller's current language. The view selects all columns from the base table (aliased B) plus the two translated columns (aliased T), and derives ROW_ID from the base table ROWID. Because the join is an inner join, a function row appears only when a translation row exists for the active language; standard EBS installations always seed translations for the base language.

Key Columns

• FUNCTION_ID — the unique surrogate key for the function; the join column to FND_MENU_ENTRIES, FND_RESPONSIBILITY, and FND_COMPILED_MENU_FUNCTIONS.
• FUNCTION_NAME — the internal, unique function name used programmatically and in security validation.
• USER_FUNCTION_NAME — the translated display name shown to users in menus and the Navigator.
• APPLICATION_ID — the owning application, joined to FND_APPLICATION.
• TYPE — the function type, such as FORM, JSP, WWW, SUBFUNCTION, or NONFORM, which determines which execution attributes apply.
• FORM_ID / PARAMETERS — identify the target form and any parameters passed to it (relevant for FORM-type functions).
• WEB_HTML_CALL, WEB_HOST_NAME, WEB_AGENT_NAME, WEB_SECURED, WEB_ICON — the web-execution attributes for URL-based and HTML functions.
• DESCRIPTION — the translated description of the function.
• OBJECT_ID, REGION_APPLICATION_ID, REGION_CODE — link OAF-based functions to their underlying object and region definitions.
• IREP_* columns — integration repository attributes (method name, scope, lifecycle, direction, compatibility, XML descriptions) used for web-service style function definitions.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include auditing function definitions, locating the display name for a given internal function, and verifying which functions are of a particular type before menu assignment.

List functions belonging to a specific application:

SELECT f.FUNCTION_ID, f.FUNCTION_NAME, f.USER_FUNCTION_NAME, f.TYPE
FROM   APPS.FND_FORM_FUNCTIONS_VL f
WHERE  f.APPLICATION_ID = 101
ORDER  BY f.FUNCTION_NAME;

Find all web-based functions and their HTML call targets:

SELECT FUNCTION_NAME, USER_FUNCTION_NAME, WEB_HTML_CALL
FROM   APPS.FND_FORM_FUNCTIONS_VL
WHERE  TYPE = 'WWW';

Resolve the display name for a known internal name:

SELECT FUNCTION_NAME, USER_FUNCTION_NAME, DESCRIPTION
FROM   APPS.FND_FORM_FUNCTIONS_VL
WHERE  FUNCTION_NAME = 'FND_FNDSCMNU';

Identify functions not referenced by any menu entry (orphan candidates):

SELECT f.FUNCTION_ID, f.FUNCTION_NAME
FROM   APPS.FND_FORM_FUNCTIONS_VL f
WHERE  NOT EXISTS (SELECT 1 FROM APPS.FND_MENU_ENTRIES m
                   WHERE m.FUNCTION_ID = f.FUNCTION_ID);

Because the view enforces USERENV('LANG') filtering, reports built directly on it automatically reflect the runtime language of the user session, which is the recommended pattern for user-facing function listings.