Search Results hxc_alias_definitions_tl




Overview
Explore in AI Chat

Overview

The HXC_ALIAS_DEFINITIONS_TL table resides in the HXC schema, which supports the Time and Labor Engine within Oracle E-Business Suite. As the "_TL" suffix indicates, this is a translated (language-specific) table that stores alternate name definitions in multiple languages. Its parent table, HXC_ALIAS_DEFINITIONS_B, holds the base (language-independent) rows, while this table holds the translated equivalents keyed by language.

The table's role is to provide user-facing, localized labels for alternate names used throughout the Time and Labor Engine — for example, alternate terminology for time entry fields, approval statuses, or other configurable attributes that vary by locale or business terminology. From a data-modeling perspective, the ETRM metadata classifies this object heuristically as standalone under the Data Vault classification heuristic, meaning it does not participate as a hub, link, or satellite in a documented FK network. This is a modeling suggestion only; in practice the table is a dependent child of its base table via the shared primary-key column ALIAS_DEFINITION_ID.

Key Information Stored

The documented physical schema for release 12.2.2 contains 12 columns. The most significant are:

  • ALIAS_DEFINITION_ID — Surrogate/primary identifier for the alias definition. This is the first component of the composite primary key and the join key to the base table HXC_ALIAS_DEFINITIONS_B.
  • LANGUAGE — The language code of the translated row. This is the second component of the primary key and the discriminator that makes this a _TL table.
  • ALIAS_DEFINITION_NAME — The translated alternate name itself; the core business content of the row.
  • DESCRIPTION — A translated description providing additional context for the alias definition.
  • SOURCE_LANG — The source language from which the translation was derived, used by the translation framework.
  • PROMPT — The translated prompt text displayed to end users in the application UI.
  • ZD_EDITION_NAME — Editioning column used by the EBS online patching infrastructure; it appears in the unique index HXC_ALIAS_DEFINITIONS_TL_PK alongside ALIAS_DEFINITION_ID and LANGUAGE.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE capture standard WHO-style audit information.

The composite primary key HXC_ALIAS_DEFINITIONS_TL_PK is defined on (ALIAS_DEFINITION_ID, LANGUAGE, ZD_EDITION_NAME), which uniquely identifies a translated alias row per edition.

Common Use Cases and Queries

Typical use cases include localizing reporting output, retrieving translated prompts for a given alias in a specific language, and joining to the base table to reconcile definitions across locales. A common query pattern retrieves the translated name for a specific alias and language:

  • SELECT ALIAS_DEFINITION_NAME FROM HXC_ALIAS_DEFINITIONS_TL WHERE ALIAS_DEFINITION_ID = :id AND LANGUAGE = USERENV('LANG');
  • Joining base and translated rows: SELECT b.ALIAS_DEFINITION_ID, t.ALIAS_DEFINITION_NAME FROM HXC_ALIAS_DEFINITIONS_B b, HXC_ALIAS_DEFINITIONS_TL t WHERE b.ALIAS_DEFINITION_ID = t.ALIAS_DEFINITION_ID AND t.LANGUAGE = :lang;

Reporting scenarios often aggregate translated aliases for a bilingual or multilingual UI, or audit which aliases lack a translation for a required language.

Related Objects

  • HXC_ALIAS_DEFINITIONS_B — Base (language-independent) table; joined on ALIAS_DEFINITION_ID.
  • HXC_ALIAS_DEFINITIONS_VL — The view combining base and translated rows, commonly queried by applications and reports.
  • The _TL pattern itself follows the standard EBS MLS (Multi-Lingual Support) framework shared by other HXC and FND translated tables keyed by ID and LANGUAGE.