Search Results hr_form_tab_pages_vl




Overview

HR_FORM_TAB_PAGES_VL is a translated (MLS) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER – Human Resources product family. It presents a language-specific, user-facing representation of the form tab page definitions that control how tabbed regions are rendered within Oracle Forms used by EBS HR self-service and professional forms. The "_VL" suffix is the standard Oracle EBS convention for a "view of translated" data: it joins a language-independent base (_B) table with a language-dependent translation (_TL) table, filtering the translation side by the current session language so that each row is returned in the run-time language of the user.

In the reporting and integration context, HR_FORM_TAB_PAGES_VL exposes a single flattened source that combines structural metadata (canvas association, tab page identifier, display order, visibility override) with translated presentation text (user tab page name and description). It is documented in ETRM for releases 12.1.1 and 12.2.2, where it is registered with status VALID. The view is not a transactional object; it is a configuration/reference reporting view used when extracting or auditing the setup of HR form tab pages, and when building multilanguage-aware lookups where the displayed tab label must match the user's preferred language.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS-owned synonyms:

  • HR_FORM_TAB_PAGES_B — the base (language-independent) table holding the physical definition of each form tab page, including its primary key, object version, parent canvas, internal tab page name, display sequence, and the standard WHO audit columns.
  • HR_FORM_TAB_PAGES_TL — the translation table holding the language-dependent attributes, principally USER_TAB_PAGE_NAME and DESCRIPTION, keyed by FORM_TAB_PAGE_ID and LANGUAGE.

The two are joined on FORM_TAB_PAGE_ID, with the translation side restricted by T.LANGUAGE = USERENV('LANG'). This predicate is what makes the view return a single row per tab page for the session language rather than one row per installed translation. The view text additionally selects B.ROWID as ROW_ID, exposing the base table row identifier.

Key Columns

  • ROW_ID — the ROWID of the underlying HR_FORM_TAB_PAGES_B row.
  • FORM_TAB_PAGE_ID — unique identifier and join key between the _B and _TL tables.
  • OBJECT_VERSION_NUMBER — optimistic locking / version column maintained by the EBS framework.
  • FORM_CANVAS_ID — foreign key to the form canvas to which the tab page belongs.
  • TAB_PAGE_NAME — internal, language-independent tab page name from the base table.
  • USER_TAB_PAGE_NAME — translated, user-visible tab label from the _TL table.
  • DESCRIPTION — translated descriptive text from the _TL table.
  • DISPLAY_ORDER — sequence controlling the order in which tab pages are presented.
  • VISIBLE_OVERRIDE — flag/indicator controlling whether the tab page is displayed.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns describing creation and last modification.

Common Use Cases and Queries

Typical uses include auditing the configured tab pages for HR forms, verifying translated labels exist for every supported language, and feeding downstream reports or interfaces that need language-appropriate tab captions. Because the view filters on USERENV('LANG'), queries return rows in the session language; to inspect a specific language, join to the _TL table directly or set the session language accordingly.

List all tab pages with their translated labels and display order:

  • SELECT form_tab_page_id, tab_page_name, user_tab_page_name, display_order, visible_override FROM apps.hr_form_tab_pages_vl ORDER BY display_order;

Retrieve the visible tab pages for a specific canvas:

  • SELECT form_tab_page_id, user_tab_page_name, display_order FROM apps.hr_form_tab_pages_vl WHERE form_canvas_id = :p_canvas_id AND visible_override = 'Y' ORDER BY display_order;

Identify tab pages lacking a translation in the current language:

  • SELECT b.form_tab_page_id, b.tab_page_name FROM apps.hr_form_tab_pages_b b WHERE NOT EXISTS (SELECT 1 FROM apps.hr_form_tab_pages_tl t WHERE t.form_tab_page_id = b.form_tab_page_id AND t.language = USERENV('LANG'));

These patterns rely solely on the documented columns and join semantics of the view, ensuring the queries remain valid across EBS 12.1.1 and 12.2.2.