Search Results ahl_user_statuses_tl




Overview

AHL_USER_STATUSES_TL is a translation table in the AHL schema, the Oracle E-Business Suite module for Complex Maintenance Repair and Overhaul (CMRO). It stores the language-specific, translated content for user-defined statuses used throughout the maintenance and overhaul process. In Oracle EBS, the "_TL" suffix denotes a translation table that holds a row for each installed or enabled language. This pattern enables Oracle's Multi-Language Support (MLS) architecture, in which descriptive attributes such as names and descriptions are maintained separately from the base transactional record so that operators in different locales can view status labels in their own language.

The object is documented as VALID in the ETRM repository and belongs to the AHL product family. Although only a brief description is provided, the presence of the translation table implies a corresponding base table — AHL_USER_STATUSES_B — that holds the actual status records, workflow flags, and configuration settings, while AHL_USER_STATUSES_TL holds the human-readable text that accompanies them.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. In other words, AHL_USER_STATUSES_TL functions like a descriptive satellite attached to the base status entity, carrying descriptive attributes (translated NAME and DESCRIPTION) keyed by the parent business key plus a language discriminator. This classification is a modeling suggestion rather than a physical constraint.

Key Information Stored

The table contains ten documented columns. The most important are:

  • USER_STATUS_ID — The surrogate primary key and the join key to the base table. It is part of AHL_USER_STATUSES_TL_PK and is a foreign key to AHL_USER_STATUSES_B.USER_STATUS_ID.
  • LANGUAGE — The language code for the translated row. The combination of USER_STATUS_ID and LANGUAGE forms the unique business key candidate AHL_USER_STATUSES_TL_U1.
  • SOURCE_LANG — Indicates the source language from which the translation was derived or entered.
  • NAME — The translated display name of the user status.
  • DESCRIPTION — The translated descriptive text for the user status.
  • CREATED_BY, CREATION_DATE — Audit columns identifying who created the translation row and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE — Audit columns identifying who last modified the row and when.
  • LAST_UPDATE_LOGIN — The login identifier associated with the most recent update.

The primary key is the surrogate USER_STATUS_ID, while the unique index AHL_USER_STATUSES_TL_U1 (USER_STATUS_ID, LANGUAGE) represents the true business-key candidate. This distinction matters because a single status can appear in multiple languages, whereas the base configuration row is unique.

Common Use Cases and Queries

Typical usage involves resolving a status identifier to its translated label for reporting, OAF pages, or concurrent program output. A common reporting pattern joins the translation table to the base table and filters by the session or requested language:

  • Retrieve translated status names for a specific language: SELECT b.user_status_id, t.name, t.description FROM ahl.ahl_user_statuses_b b, ahl.ahl_user_statuses_tl t WHERE b.user_status_id = t.user_status_id AND t.language = USERENV('LANG');
  • List all available translations for a given status: SELECT language, name FROM ahl.ahl_user_statuses_tl WHERE user_status_id = :status_id;
  • Audit translation coverage by comparing languages present in the table against the set of installed languages.
  • Feed lookup views or BI Publisher reports that require localized status captions.

Because the table is maintained by the AHL application, direct DML is not recommended. Translators should use the standard CMRO setup interface to add or revise translations.

Related Objects

The following objects are most significant in relation to AHL_USER_STATUSES_TL:

  • AHL_USER_STATUSES_B — The base table holding the actual user status records; joined on USER_STATUS_ID. It is the parent entity to this translation satellite.
  • AHL_USER_STATUSES_TL_PK — The primary key constraint on USER_STATUS_ID.
  • AHL_USER_STATUSES_TL_U1 — The unique index on (USER_STATUS_ID, LANGUAGE), enforcing one translation per language per status.
  • FND_LANGUAGES — The EBS language reference table, used to validate LANGUAGE and SOURCE_LANG values.
  • FND_USER — Referenced indirectly through CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for audit traceability.
  • AHL status lookup views — Application views and OAF pages that surface translated status labels depend on this table for display text.

Together these objects form the configuration backbone for user-defined statuses in Oracle CMRO.