Search Results hr_window_properties_vl




Overview
Explore in AI Chat

Overview

HR_WINDOW_PROPERTIES_VL is a translated (multi-language) view owned by the APPS schema in Oracle E-Business Suite, belonging to the PER — Human Resources product family. It exposes configuration metadata that governs the runtime behaviour of Oracle Forms windows within the HRMS suite, including window sizing, screen positioning, title text, and an extended set of informational attributes. The view follows the standard Oracle EBS "VL" naming convention, which denotes a view that joins a base table (_B) with its translation table (_TL) and filters the translation by the session language.

In the context of EBS 12.1.1 and 12.2.2, this view is primarily a metadata presentation object rather than a transactional one. It allows reporting tools, diagnostics, and integration layers to read window property definitions with the correct language-specific title (TITLE) without having to manually join the base and translation tables or apply the USERENV('LANG') predicate themselves. Because the view resolves the language at query time, it is safe for multi-lingual deployments where users in different language sessions must see their own translated window captions.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms within the APPS schema:

The view joins the two on WINDOW_PROPERTY_ID and restricts the TL side with T.LANGUAGE = USERENV('LANG'), ensuring exactly one translated row per window property for the current session language. The view additionally projects B.ROWID as the leading column. Note that although the documentation labels the first column ROW_ID, the actual view text exposes the base table ROWID; this pseudo-column is useful for identifying rows but is not stable across table reorganization.

Key Columns

  • WINDOW_PROPERTY_ID — primary identifier for each window property record; the join key between the base and translation tables.
  • FORM_WINDOW_ID and TEMPLATE_WINDOW_ID — identifiers linking the property set to the specific form window and its template window definition.
  • TITLE — the translated window caption sourced from HR_WINDOW_PROPERTIES_TL; this is the primary reason to use the VL view rather than the base table.
  • HEIGHT, WIDTH, X_POSITION, Y_POSITION — numeric geometry attributes controlling the rendered window dimensions and screen placement.
  • INFORMATION_CATEGORY and INFORMATION1 through INFORMATION30 — a flexible set of descriptive attributes that carry contextual metadata supplied by the HRMS framework.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, standard across EBS tables and drawn from the _B base table.

Common Use Cases and Queries

Typical uses include auditing HRMS window configuration, verifying that translated titles exist for a given language, and integrating HR window metadata into custom reporting or diagnostics. A representative query listing property geometry and captions is:

  • SELECT window_property_id, form_window_id, title, height, width, x_position, y_position FROM apps.hr_window_properties_vl WHERE form_window_id = :form_window_id;
  • SELECT window_property_id, title FROM apps.hr_window_properties_vl ORDER BY title; — to enumerate available window titles in the current session language.
  • SELECT window_property_id, information_category, information1 FROM apps.hr_window_properties_vl WHERE information_category IS NOT NULL; — to inspect configured information attributes.

Because the view applies USERENV('LANG') internally, callers should not add their own LANGUAGE predicate on the view; doing so is unnecessary and may yield no rows if the language code does not match the session setting. For DBA troubleshooting, querying HR_WINDOW_PROPERTIES_B and HR_WINDOW_PROPERTIES_TL directly can reveal missing translations that would cause a property to be absent from the VL view.