Search Results audit_enabled_flag

Overview

FND_FORM_VL is a seeded, VALID view owned by the APPS schema within the FND (Application Object Library) product of Oracle E-Business Suite. It presents the translatable attributes of Oracle Forms-based application forms by joining the base definition table FND_FORM with its translation table FND_FORM_TL. The "_VL" suffix denotes a "view of language," the standard Oracle EBS naming convention for views that resolve translated (TL) columns to the session language, returning only a single, user-facing language row per form.

FND_FORM stores one row per form registered in the EBS instance, keyed by APPLICATION_ID and FORM_ID, and holds the non-translatable, language-independent attributes such as the internal FORM_NAME and audit settings. FND_FORM_TL holds the translatable text — USER_FORM_NAME and DESCRIPTION — for each installed language. FND_FORM_VL exposes the combined result set, so reports, concurrent programs, and integration interfaces can retrieve both the internal form identifier and the user-visible display name without manually joining translation tables or applying the LANGUAGE filter themselves. The view is present in both 12.1.1 and 12.2.2, which share the same object definition.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 identifies two referenced base objects, both exposed to APPS through synonyms: FND_FORM (SYNONYM) and FND_FORM_TL (SYNONYM). The view text is:

• FND_FORM — aliased B; supplies APPLICATION_ID, FORM_ID, FORM_NAME, the audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN), and AUDIT_ENABLED_FLAG.
• FND_FORM_TL — aliased T; supplies USER_FORM_NAME and DESCRIPTION in the current session language.
• Join condition — B.APPLICATION_ID = T.APPLICATION_ID AND B.FORM_ID = T.FORM_ID, combined with the language filter T.LANGUAGE = USERENV('LANG').
• ROW_ID — derived from B.ROWID ($HEADER$ substitution), not stored in any base table.

Because the join is enforced on both key columns and on the session language, the view returns exactly one row per form per language context. In a multi-language instance, FND_FORM still contributes a single row per form, while the translation table supplies the language-appropriate text, including a base-language fallback row.

Key Columns

• ROW_ID — Rowid of the underlying FND_FORM record; useful for row identification in forms and DML operations.
• APPLICATION_ID — Numeric identifier of the owning application (e.g., FND). Part of the composite primary key.
• FORM_ID — Numeric identifier of the form within the application. Part of the composite primary key.
• FORM_NAME — Internal, language-independent form name used by the Forms runtime and function registration.
• USER_FORM_NAME — Translatable, user-facing form name displayed in menus and the navigator; resolved from FND_FORM_TL in the session language.
• DESCRIPTION — Translatable descriptive text for the form, also from FND_FORM_TL.
• AUDIT_ENABLED_FLAG — Indicates whether row-level auditing is enabled for the form.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns describing creation and last modification.

Common Use Cases and Queries

FND_FORM_VL is typically used to build form inventories, resolve the display name for a given FORM_NAME or FORM_ID, and cross-reference forms with functions and menus, since FND_FORM_FUNCTIONS references FORMS by FORM_ID and APPLICATION_ID.

List all registered forms in a readable format:

• SELECT application_id, form_id, form_name, user_form_name, description FROM apps.fnd_form_vl ORDER BY user_form_name;

Resolve the user-facing name for a specific internal form:

• SELECT user_form_name, description FROM apps.fnd_form_vl WHERE form_name = 'FND_FNDSCMNU';

Join forms to their registered functions:

• SELECT v.form_name, v.user_form_name, f.function_name FROM apps.fnd_form_vl v, apps.fnd_form_functions_vl f WHERE v.application_id = f.form_id AND v.form_id = f.form_id;

Because the view filters on USERENV('LANG'), a report executed under one language session returns localized text automatically, making FND_FORM_VL the preferred access path for any reporting or integration logic requiring the user-visible form name alongside its internal identifier.