Results for “ahl_mc_headers_tl”

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

Overview

In Oracle E-Business Suite releases 12.1.1 and 12.2.2, AHL.AHL_MC_HEADERS_TL is the translation table for the Complex Maintenance Repair and Overhaul (AHL) module's Master Configuration header entity. Master Configuration records represent the top-level configuration definition used by MRO operations to organize maintenance bills of material, configuration items, and routings. Because descriptive text associated with a Master Configuration header must be presented in multiple installed languages, Oracle stores the translatable attributes in this dedicated _TL table rather than in the base entity table.

From a data modeling perspective, the metadata classifies this object as satellite-leaning. In Data Vault terms, a satellite stores descriptive, time-variant, or language-variant attributes that hang off a hub or link. Here the natural parent is the base table that owns the Master Configuration identifier, and every row in AHL_MC_HEADERS_TL enriches that parent with a language-specific description. Treating it as a satellite is a modeling suggestion rather than a schema fact; Oracle implements it as a standard multi-language child table.

Key Information Stored

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

• MC_HEADER_ID — Surrogate identifier for the Master Configuration header. Together with LANGUAGE it forms the composite primary key AHL_MC_HEADERS_TL_PK.
• LANGUAGE — The NLS language code for the row, distinguishing one translation of a header from another.
• SOURCE_LANG — The language in which the description was originally entered, used for translation tracking.
• DESCRIPTION — The translatable descriptive text for the Master Configuration header; this is the principal payload column of the table.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing Oracle Applications row-level security and multi-organization data access.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and modification metadata for each translation row.

The unique index AHL_MC_HEADERS_TL_U1 on (MC_HEADER_ID, LANGUAGE) is a business-key candidate, guaranteeing exactly one translation row per header per language and enforcing uniqueness independent of surrogate identifiers.

Common Use Cases and Queries

Typical use cases center on multilingual reporting and integration. When extracting Master Configuration data for interfaces or operational reports, developers join the translation table back to its parent to retrieve the language-specific description. A representative query pattern is:

• SELECTION BY ID AND LANGUAGE: SELECT description FROM ahl_mc_headers_tl WHERE mc_header_id = :id AND language = USERENV('LANG');
• JOIN TO BASE ENTITY: SELECT h.mc_header_id, t.description FROM ahl_mc_headers_vl t WHERE t.mc_header_id = :id; (the _VL view is the standard EBS mechanism that unions translations with the base table.)
• AUDIT AND COMPLETENESS: querying SOURCE_LANG and LANGUAGE to identify headers lacking translations for installed languages.
• SECURITY-FILTERED EXTRACTION: joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS when extracting data for restricted organizations.

Reporting layers typically resolve the translatable description through the associated _VL view rather than querying this table directly, but direct access is required for bulk translation loads and audit checks.

Related Objects

• Base Master Configuration header table — The parent entity on MC_HEADER_ID; the _TL table is meaningless without it.
• AHL_MC_HEADERS_TL._VL view — The language-resolving view typically exposed to forms and reports.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for row-level security enforcement.
• AHL_MC_HEADERS_TL_PK / _U1 — Primary and unique indexes enforcing identity and translation uniqueness.
• AHL MRO configuration child tables — Bills of material, configuration items, and routings that reference the header via MC_HEADER_ID.

Because the metadata documents only the self-referential key and the security-group foreign key, additional relationships are inferred from the AHL data model and should be validated against the specific 12.1.1 or 12.2.2 installation.