Results for “pqh_templates_tl”

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

Overview

PQH_TEMPLATES_TL is the translation (TL) table for templates within the Oracle E-Business Suite Public Sector HR (PQH) module. In the Oracle EBS multilanguage architecture, translation tables hold the language-specific descriptive attributes of a base entity, while the corresponding base table (PQH_TEMPLATES_B) stores language-independent columns. Each row in PQH_TEMPLATES_TL represents the translated name of a template in a specific installed language, enabling organizations that operate in multiple languages to present the same template under localized labels. This object is owned by the HR schema and is marked VALID in the ETRM 12.2.2 data dictionary, with a documented physical schema of ten columns.

From a data-modeling perspective, the heuristic Data Vault classification derived from the foreign-key structure is standalone, meaning no explicit foreign key dependencies were mined. As a modeling suggestion, this classification should be treated with caution: functional translation tables such as this one are conventionally modeled as satellites attached to the base template hub, keyed by the surrogate template identifier and the language code. Designers building a dimensional or vault layer over EBS should therefore consider PQH_TEMPLATES_TL a satellite of the PQH_TEMPLATES_B template hub rather than a truly independent entity, despite the absence of declared constraints.

Key Information Stored

The table carries the following documented columns, which may be grouped into identification, translation payload, and standard EBS audit/MLS columns.

• TEMPLATE_ID — Surrogate identifier of the base template. Together with LANGUAGE it forms the primary key PQH_TEMPLATES_TL_PK, linking each translated row to its parent template.
• LANGUAGE — The installed language code for which the translated content applies.
• TEMPLATE_NAME — The translated, language-specific name of the template; this is the principal business attribute held by the table.
• SOURCE_LANG — The source language from which the translation row was derived or seeded, used by the MLS translation framework.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS online patching (Edition-Based Redefinition). It appears in the documented unique index PQH_TEMPLATES_TL_PK (TEMPLATE_ID, LANGUAGE, ZD_EDITION_NAME), making that three-column combination the effective business-key candidate at the physical level.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS who-columns recording row creation and maintenance audit information.

Note the distinction between the surrogate primary key (TEMPLATE_ID, LANGUAGE) and the unique index, which additionally includes ZD_EDITION_NAME to accommodate editioned data.

Common Use Cases and Queries

Reporting against translated template names is the primary use case. A typical join resolves the base template to its name for a requested language:

• Join PQH_TEMPLATES_TL to PQH_TEMPLATES_B on TEMPLATE_ID to list templates with localized names.
• Filter by LANGUAGE to produce language-specific extract files for interfaces or documentation.
• Audit translation coverage by comparing base template IDs against those having a row for each installed language.
• Reconcile SOURCE_LANG values to confirm seeded versus manually translated content.

A representative query pattern selects TEMPLATE_ID, TEMPLATE_NAME, and LANGUAGE from PQH_TEMPLATES_TL where LANGUAGE equals the user's session language, joined back to the base table for untranslated attributes. Because of editioning, queries against production 12.2.x environments should generally filter or join on ZD_EDITION_NAME to avoid duplicate rows across editions.

Related Objects

• PQH_TEMPLATES_B — The base (non-translated) template table; joined on TEMPLATE_ID.
• PQH_TEMPLATES_VL — The MLS view exposing both base and translated columns.
• PQH_TEMPLATES_TL_PK — Primary key constraint/index on TEMPLATE_ID and LANGUAGE.
• PQH_TEMPLATE_DEFINITIONS / related PQH_TEMPLATES child tables — Depend on TEMPLATE_ID for definition content associated with the template.
• FND_LANGUAGES — Provides the language codes referenced by LANGUAGE and SOURCE_LANG.
• FND_TERRITORIES — Supports regional language/territory resolution in reporting joins.

Together these objects form the template translation cluster within Public Sector HR, with PQH_TEMPLATES_TL supplying the localized naming layer for template-driven HR processes.