Results for “hr_window_properties_tl”

50+ results




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

Overview

HR_WINDOW_PROPERTIES_TL is the translation table for configurable form window definitions within the Oracle E-Business Suite PER — Human Resources product. It stores the language-specific (translated) text attributes for windows that appear in configurable forms used by HRMS self-service and professional forms. In the Oracle EBS multilanguage architecture, a corresponding base table (HR_WINDOW_PROPERTIES_B) holds language-independent and non-translatable data, while this _TL companion table holds the translatable attributes keyed by LANGUAGE. The _TL suffix is the standard Oracle EBS convention for a translation entity, and it appears here exactly as documented with ten columns in the 12.2.2 physical schema.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. This is consistent with the table's dependency upon HR_WINDOW_PROPERTIES_B as its parent: the _TL table is best modeled as a descriptive satellite attached to the base hub/business entity, keyed by the parent surrogate plus the language and edition discriminators.

Key Information Stored

The primary key for this table is documented as HR_WINDOW_PROPERTIES_TL_PK over (WINDOW_PROPERTY_ID, LANGUAGE). The unique index description extends this to (WINDOW_PROPERTY_ID, LANGUAGE, ZD_EDITION_NAME), which reflects the 12.2.x editioning column added with the Online Patching (AD/TXK) architecture. This composite uniquely identifies each translatable property row per language and edition.

  • WINDOW_PROPERTY_ID — surrogate foreign key referencing HR_WINDOW_PROPERTIES_B.WINDOW_PROPERTY_ID; the language-independent identifier of the window property.
  • LANGUAGE — the language code (for example US or ES) identifying the translation; part of the primary key.
  • SOURCE_LANG — the language of the source text, used by the translation infrastructure to track the origin language of the translatable string.
  • TITLE — the translated title of the configurable form window; the principal business attribute this table exists to hold.
  • ZD_EDITION_NAME — the editioning column enabling online patching; part of the documented unique index.

Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE follow the standard Oracle EBS WHO-column convention and support change tracking, concurrency, and audit reporting.

Common Use Cases and Queries

Typical usage centers on displaying window titles in a user's session language and on translation-completeness reporting. A common query joins the translation table to the base table and filters by language:

  • Session-language lookup: select the translated TITLE where WINDOW_PROPERTY_ID = :id and LANGUAGE = userenv('LANG').
  • Missing-translation audit: outer-join HR_WINDOW_PROPERTIES_B to this table to find windows lacking a row for a target language.
  • Multi-language comparison: pivot TITLE by LANGUAGE for a given WINDOW_PROPERTY_ID to review translations side by side.
  • Change audit: report on LAST_UPDATE_DATE and LAST_UPDATED_BY to track who last modified a translated title.

All queries should account for the ZD_EDITION_NAME column, applying the standard editioning predicate in 12.2.2 environments.

Related Objects

The most significant related objects follow from the documented foreign key and primary key relationships:

  • HR_WINDOW_PROPERTIES_B — the base table; joined on WINDOW_PROPERTIES_TL.WINDOW_PROPERTY_ID = WINDOW_PROPERTIES_B.WINDOW_PROPERTY_ID. This is the primary parent for the satellite.
  • Configurable forms metadata tables in the HR/PER schema that reference window definitions and consume the translated titles at runtime.
  • FND_LANGUAGES — the language repository used to interpret and validate LANGUAGE and SOURCE_LANG values.
  • FND_LANGUAGE-based views and EBS multilanguage views that expose the translated title alongside base attributes.

Because the table is a translation satellite, direct DML is rare in customer extensions; application code and the standard HRMS translation infrastructure are the normal owners of these rows.