Results for “hr_tab_page_properties_tl_fk3”

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

Overview

HR_TAB_PAGE_PROPERTIES_TL is the translation (TL) table for tab page properties used by Oracle E-Business Suite configurable forms within the PER — Human Resources product. In the Oracle EBS architecture, translation tables store multilingual, language-specific attributes for a corresponding base table. This table stores the translated, display-facing properties of tab pages — most notably the label rendered to end users — keyed by the language in which that label is expressed.

Its documented foreign key relationship ties each row to HR_TAB_PAGE_PROPERTIES_B on TAB_PAGE_PROPERTY_ID, confirming the classic EBS _B (base) and _TL (translated) pairing. The _B table holds language-independent structural and configuration attributes, while this _TL table holds language-dependent text. In Data Vault modeling terms, the metadata's heuristic classification is satellite-leaning: the table behaves as a descriptive satellite attached to the base entity, carrying descriptive, time-versioned attributes rather than defining business keys themselves. It is owned by the HR schema and documented as VALID in release 12.1.1 / 12.2.2.

Key Information Stored

The table is documented with ten columns. The most significant are the following:

• TAB_PAGE_PROPERTY_ID — the surrogate identifier for the parent tab page property; also part of the composite primary key and the FK to HR_TAB_PAGE_PROPERTIES_B.
• LANGUAGE — the NLS language code for the translated content; the second component of the primary key.
• LABEL — the translated, user-visible text displayed on the tab page.
• SOURCE_LANG — the language code of the source row from which the translation was derived, supporting the standard EBS translation model.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard EBS WHO columns providing audit and change tracking.
• ZD_EDITION_NAME — the editioning column used in the 12.2 Online Patching (AD/TXK) architecture.

The documented primary key is HR_TAB_PAGE_PROPERTIES_TL_PK over (TAB_PAGE_PROPERTY_ID, LANGUAGE). The unique index in the documented physical schema additionally includes ZD_EDITION_NAME — (TAB_PAGE_PROPERTY_ID, LANGUAGE, ZD_EDITION_NAME) — which serves as the business-key candidate and reflects the edition-aware partitioning introduced under Online Patching. TAB_PAGE_PROPERTY_ID and LANGUAGE together form the natural traversal key, while ZD_EDITION_NAME scopes each row to a specific edition.

Common Use Cases and Queries

The primary use case is retrieving localized labels for configurable tab pages. Forms and framework components resolve a tab page property by joining this table to its base table and filtering on the active language. A representative pattern is:

• SELECT tl.label FROM hr.hr_tab_page_properties_tl tl WHERE tl.tab_page_property_id = :property_id AND tl.language = userenv('LANG');
• Joining to the base table: SELECT b.tab_page_property_id, tl.label FROM hr.hr_tab_page_properties_b b, hr.hr_tab_page_properties_tl tl WHERE b.tab_page_property_id = tl.tab_page_property_id AND tl.language = userenv('LANG');
• Auditing untranslated or missing labels by comparing the set of languages present in HR_TAB_PAGE_PROPERTIES_TL against the expected NLS language list for a given property.

Reporting scenarios include translation-coverage reports (which tab pages lack a given language), and label-change audits using the WHO and edition columns. Under 12.2 Online Patching, queries should be edition-aware, since ZD_EDITION_NAME distinguishes rows across editions.

Related Objects

• HR_TAB_PAGE_PROPERTIES_B — the base table; join on TAB_PAGE_PROPERTY_ID. This is the documented foreign-key parent and the primary related object.
• HR_TAB_PAGE_PROPERTIES_TL_PK — the composite primary-key constraint over (TAB_PAGE_PROPERTY_ID, LANGUAGE).
• HR_TAB_PAGE_PROPERTIES_TL — this table itself, referenced by the same surrogate key in dependent configuration and personalization logic.
• ZD_EDITION_NAME / AD_ZD_EDITION — the Online Patching edition infrastructure that governs row visibility per edition.
• FND_LANGUAGES — referenced logically via the LANGUAGE and SOURCE_LANG columns to map language codes to installed languages.