Results for “hxc_layouts_tl”

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

Overview

HXC_LAYOUTS_TL is the translated (TL) child table of HXC_LAYOUTS within the Oracle E-Business Suite Time and Labor Engine (HXC) schema. It stores the language-dependent descriptive attributes of timecard, time collection, and layout definitions used throughout Oracle Time and Labor (OTL) and related modules such as Oracle Payroll and Oracle Projects. Because Oracle EBS supports multiple installed languages, the base table HXC_LAYOUTS holds the primary definition (identifiers, functional flags, and structural attributes), while HXC_LAYOUTS_TL carries the displayable text — principally the layout name — for each installed language. This separation follows the standard Oracle EBS MLS (Multi-Lingual Support) pattern in which a non-translated table is paired with a _TL companion keyed by LAYOUT_ID plus LANGUAGE.

From a data-modeling perspective, the metadata's heuristic Data Vault classification identifies this object as satellite-leaning. That is a modeling suggestion rather than a physical attribute of the EBS table: HXC_LAYOUTS_TL behaves as a descriptive satellite whose parent hub-equivalent is HXC_LAYOUTS, keyed through the LAYOUT_ID foreign key and qualified by the LANGUAGE and edition attributes that track translation context and seed-data lineage.

Key Information Stored

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

• LAYOUT_ID — The foreign key to HXC_LAYOUTS and part of the composite primary key. It links each translated row to its parent layout definition.
• LANGUAGE — The installed language code for the translated row; the second component of the composite primary key.
• DISPLAY_LAYOUT_NAME — The user-visible layout name rendered in the corresponding language. This is the principal business attribute stored in the table and the value most often surfaced in LOVs, reports, and setup screens.
• SOURCE_LANG — The language from which the translation originated, used by the MLS translation framework to track provenance when a new language row is created or copied.
• ZD_EDITION_NAME — The edition identifier used by Oracle's edition-based redefinition and seed-data upgrade framework to distinguish delivered data versions.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture standard Oracle EBS who/when audit information.

The documented primary key is HXC_LAYOUTS_TL_PK (LANGUAGE, LAYOUT_ID). A unique index, HXC_LAYOUTS_TL_PK (LANGUAGE, LAYOUT_ID, ZD_EDITION_NAME), is listed as the business-key candidate, reflecting the addition of the edition column to preserve uniqueness across delivered editions. The surrogate identifier remains LAYOUT_ID from the parent table.

Common Use Cases and Queries

Typical uses include resolving the display name of a layout for a given session language, auditing missing translations, and joining translated names into reporting queries over timecard configuration.

• Resolve the display name for a specific language: SELECT layout_id, display_layout_name FROM hxc_layouts_tl WHERE language = USERENV('LANG') AND layout_id = :p_layout_id;
• Identify layouts lacking a translation for an installed language using an outer join against HXC_LAYOUTS.
• Report all available translations for a layout: SELECT language, display_layout_name, source_lang FROM hxc_layouts_tl WHERE layout_id = :p_layout_id ORDER BY language;
• Feed OTL setup and configuration reports (for example, layout listings in timecard administration) where the localized name must appear rather than the internal layout identifier.

Related Objects

The dominant relationship is to the base table HXC_LAYOUTS via HXC_LAYOUTS_TL.LAYOUT_ID. Other significant related objects in the HXC and OTL schema family include the layout definition and structure tables used to assemble timecard layouts, the time collection and timecard definition tables referenced by those layouts, and the HXC MLS lookup and translation utilities that populate _TL rows. Join patterns should always key on LAYOUT_ID and filter or join on LANGUAGE to avoid multiplying rows across installed languages.