Search Results hr_form_windows_vl




Overview
Explore in AI Chat

Overview

HR_FORM_WINDOWS_VL is a translated (VL) view in the APPS schema belonging to the PER (Human Resources) product module. It is a valid database object in Oracle EBS 12.1.1 and 12.2.2 and exposes the user-facing, language-specific representation of Oracle Forms window definitions used by the Oracle Applications Framework and Oracle Forms engine. In Oracle E-Business Suite, a "VL" view is the standard designation for a view that joins a base ("_B") table, which stores language-independent attributes, with a translation ("_TL") table, which stores language-dependent text such as the translatable name and description. HR_FORM_WINDOWS_VL performs exactly this role for the HR_FORM_WINDOWS_B and HR_FORM_WINDOWS_TL tables.

Functionally, this view is primarily an internal metadata object. It supports the delivery of runtime form window labels and descriptions in the session's current language (USERENV('LANG')), and it appears in technical documentation, data dictionary queries, and ETRM (E-Business Suite Technical Reference Manual) references as the canonical access path over the underlying form-window tables. Reporting or integration logic that needs the translated window name for a given form should query this view rather than the base and translation tables individually.

Underlying Base Objects

The view text is defined over two APPS synonyms: HR_FORM_WINDOWS_B and HR_FORM_WINDOWS_TL. HR_FORM_WINDOWS_B holds the non-translatable, language-independent attributes of a form window, notably the primary key FORM_WINDOW_ID, the APPLICATION_ID, the FORM_ID, the internal WINDOW_NAME, and the standard who-columns for auditing. HR_FORM_WINDOWS_TL holds the language-dependent columns (USER_WINDOW_NAME and DESCRIPTION) keyed by FORM_WINDOW_ID and LANGUAGE. The view joins the two on FORM_WINDOW_ID and restricts the translation rows to LANGUAGE = USERENV('LANG'), so each query returns exactly one translated row per form window for the current session language.

Because the view reads from these base tables at query time, it always reflects the current definitions and translations and does not store or cache any data itself. It also exposes the B.ROWID, which allows downstream tools that rely on a row identifier to operate against the view.

Key Columns

  • FORM_WINDOW_ID — Primary key identifying the form window; the join key between the B and TL tables.
  • ROW_ID — Row identifier taken from the base table (B.ROWID).
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/Forms framework for update concurrency.
  • APPLICATION_ID — The Application the form belongs to.
  • FORM_ID — Identifier of the parent Oracle Form that owns the window.
  • WINDOW_NAME — Internal, language-independent window name.
  • USER_WINDOW_NAME — Translatable display name shown to the user in the session language.
  • DESCRIPTION — Translatable description of the window.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard EBS audit (WHO) columns.

Common Use Cases and Queries

The most frequent use is looking up the translated window name and description for a specific form or window, for example when diagnosing a form-window mismatch or documenting a customization. A representative query is:

-- not shown here

Typical SQL statements include retrieving all windows for an application, finding the user-facing name of a given FORM_ID, or joining the view to other HR form metadata objects. Because the view filters by USERENV('LANG'), results are automatically returned in the language of the connected session.

  • Mapping internal window names to translated display names for a specific form.
  • Documenting form-window metadata during a 12.1.1 to 12.2.2 upgrade or audit.
  • Investigating translation gaps by comparing HR_FORM_WINDOWS_B and HR_FORM_WINDOWS_TL coverage against the view.