Results for “bis_form_function_extension_vl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIS_FORM_FUNCTION_EXTENSION_VL is a bilingual (VL, "view with language") database view within the Oracle E-Business Suite Applications BIS product family. It exposes metadata describing form function extensions — the customizations and extensions applied to form-based functions in EBS. The view joins a base transaction table to its translation table and filters the translation rows by the session language, so that querying consumers retrieve the extension name and description in the language configured for the current user session rather than in every installed language.

In EBS 12.1.1 and 12.2.2, the view serves reporting and integration purposes rather than runtime form execution. Functional administrators, implementation consultants, and technical analysts use it to inventory the form function extensions registered in an environment, to document customizations during upgrades or audits, and to drive external reports or data extracts that must be presented in the user's own language. Because the view is a VL construct, it automatically applies the standard Oracle multilingual convention: each extension appears once, translated into the current language, keyed by OBJECT_NAME. The ETRM documentation notes the view is "Not implemented in this database" in the reference environment, which is expected where no form function extensions have been registered — the underlying tables exist but contain no qualifying rows.

Underlying Base Objects

The documented definition of BIS_FORM_FUNCTION_EXTENSION_VL is a join between two tables:

• BIS_FORM_FUNCTION_EXTENSION FF_EXT — the primary (untranslated) table holding extension identity and administrative attributes. It supplies OBJECT_NAME, OBJECT_TYPE, APPLICATION_ID, FUNCTIONAL_AREA_ID, and the standard WHO audit columns.
• BIS_FORM_FUNCTION_EXTENSION_TL FF_EXT_TL — the translation table holding the NAME and DESCRIPTION columns in each installed language.

The two tables are joined on OBJECT_NAME, and the view restricts the translation side with the predicate FF_EXT_TL.LANGUAGE = USERENV('LANG'). This is the canonical Oracle VL pattern: the join is on the object's primary key, and language selection is resolved at query time against the session environment. No other base objects are documented in the ETRM metadata for this view.

Key Columns

• OBJECT_NAME — the technical identifier of the form function extension; also the join key between the base and translation tables.
• OBJECT_TYPE — classifies the extended object, distinguishing the category of extension applied.
• NAME — the user-facing, translated name of the extension, drawn from the TL table in the session language.
• DESCRIPTION — the translated descriptive text for the extension.
• APPLICATION_ID — the owning application, useful for grouping extensions by product or module.
• FUNCTIONAL_AREA_ID — the functional area to which the extension belongs, enabling filtering by business function.
• CREATED_BY / CREATION_DATE — audit columns recording who registered the extension and when.
• LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — audit columns capturing the most recent modification and the login under which it occurred.

Common Use Cases and Queries

Typical uses include producing a translated inventory of form function extensions, auditing customizations before an upgrade, and joining extension metadata to application or functional area reference data for reporting.

• List all extensions in the session language: SELECT object_name, name, description FROM bis_form_function_extension_vl;
• Filter by owning application: SELECT object_name, name, application_id FROM bis_form_function_extension_vl WHERE application_id = :app_id;
• Review recently changed extensions: SELECT object_name, name, last_updated_by, last_update_date FROM bis_form_function_extension_vl ORDER BY last_update_date DESC;

Because language filtering is built into the view, no additional language predicate is required in these queries; results reflect the invoking user's session language automatically.