Search Results hr_form_windows




Overview
Explore in AI Chat

Overview

The APPS.HR_FORM_WINDOWS view is a reporting and integration object within the PER (Human Resources) product family of Oracle E-Business Suite. It exposes window definitions alongside their translated display properties, providing a single consolidated source for form window metadata used throughout the Oracle HRMS application. Because window titles, dimensions, and informational attributes are stored across separate base and translation entities, this view performs the join work necessary to present a usable result set without requiring consumers to understand the underlying normalized schema. In Oracle EBS 12.1.1 and 12.2.2 the object is shipped with VALID status in the APPS schema, and its design reflects the standard Oracle multilingual ("_TL"/"_VL") architecture introduced for translation support.

Underlying Base Objects

The view is defined over three documented base objects:

The view text joins HR_WINDOW_PROPERTIES_VL to HR_FORM_WINDOWS_VL on FORM_WINDOW_ID, and that result to HR_FORM_WINDOWS_B on the same column. The property join is an outer join (P.FORM_WINDOW_ID (+) = W.FORM_WINDOW_ID), so window definitions persist in the output even when no property row exists. A ROWID from HR_FORM_WINDOWS_B is also projected, though this is a legacy pattern and not recommended as a durable identifier in custom code.

Key Columns

  • FORM_WINDOW_ID — primary identifier that ties the window to its form and drives all three joins.
  • APPLICATION_ID — the application owning the form, useful for filtering by module.
  • FORM_ID — the associated Oracle Forms form definition.
  • WINDOW_NAME / USER_WINDOW_NAME — internal and user-facing window names sourced from the translation view.
  • TITLE, WIDTH, HEIGHT, X_POSITION, Y_POSITION — presentation properties describing window appearance and placement.
  • INFORMATION_CATEGORY and INFORMATION1–INFORMATION30 — generic descriptive attributes (a descriptor-flexfield-style pattern) that carry supplementary window metadata.
  • OBJECT_VERSION_NUMBER — optimistic locking/versioning column.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE.
  • ROW_ID — the ROWID of the base table row, inherited from HR_FORM_WINDOWS_B.

Common Use Cases and Queries

Typical scenarios include enumerating the windows defined for a given form, auditing window-level metadata during an upgrade or localization exercise, and driving custom integrations that need translated window titles. A representative query listing windows for a specific form would be:

  • SELECT FORM_WINDOW_ID, WINDOW_NAME, USER_WINDOW_NAME, TITLE, WIDTH, HEIGHT FROM APPS.HR_FORM_WINDOWS WHERE FORM_ID = :form_id ORDER BY WINDOW_NAME;
  • SELECT FORM_WINDOW_ID, APPLICATION_ID, FORM_ID, USER_WINDOW_NAME FROM APPS.HR_FORM_WINDOWS WHERE LAST_UPDATE_DATE >= :since ORDER BY LAST_UPDATE_DATE;
  • SELECT COUNT(*) FROM APPS.HR_FORM_WINDOWS WHERE INFORMATION_CATEGORY IS NULL;

Because the view is read-only and non-key-preserved over an outer join, it is not designed for DML via the view. Queries should be schema-qualified against APPS, and filters on APPLICATION_ID or FORM_ID should be applied to narrow the result set, as the base tables can be large and are shared across the HRMS suite.