Results for “doc_revision_id”

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

Overview

AHL_DOC_REVISIONS_TL is the translation table for document revisions in the Oracle E-Business Suite (EBS) Complex Maintenance Repair and Overhaul (AHL) product. Its role is to hold the language-specific (translated) column values for each row defined in the base table AHL_DOC_REVISIONS_B, allowing a single document revision to present its descriptive text in multiple installed languages. The "_TL" suffix denotes a translation table following the standard Oracle Applications multi-language design pattern, in which the "_B" table stores language-independent attributes and the "_TL" table stores translatable attributes such as comments or descriptions for each language code.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is satellite-leaning. In modeling terms, it functions as a satellite attached to the hub-like base entity AHL_DOC_REVISIONS_B, carrying descriptive, language-dependent attributes keyed by the revision identifier plus the language code. The granularity of the table is one row per document revision per installed language.

Key Information Stored

The table is owned by the AHL schema and comprises ten documented columns in the ETRM 12.2.2 physical schema. The most significant of these are:

• DOC_REVISION_ID — surrogate identifier that links the translated row back to its parent revision in AHL_DOC_REVISIONS_B. It is the first component of the composite primary key.
• LANGUAGE — the installed language code for which the translated values apply; second component of the composite primary key and of the unique index.
• COMMENTS — the translated free-text column carried by this table; the primary reason the row exists in a "_TL" table.
• SOURCE_LANG — the language of the source (typically the base) row from which the translation was derived; used by the translation framework to determine whether a translated value is current.
• SECURITY_GROUP_ID — the security group FK to FND_SECURITY_GROUPS, enforcing multi-organization and data-access partitioning.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle Applications WHO columns capturing audit and concurrency information.

The primary key is AHL_DOC_REVISIONS_TL_PK over (DOC_REVISION_ID, LANGUAGE). The unique index AHL_DOC_REVISIONS_TL_U1 also spans (DOC_REVISION_ID, LANGUAGE), which serves as the business-key candidate: it guarantees exactly one translated row per revision per language. The surrogate key proper is DOC_REVISION_ID, inherited from the base table rather than generated locally.

Common Use Cases and Queries

Typical uses include retrieving the translated revision text for a specific language, auditing translation coverage, and joining translated attributes to base revision data in reports.

• Retrieve translated comments for a revision in a target language: select tl.comments from ahl_doc_revisions_tl tl where tl.doc_revision_id = :p_revision_id and tl.language = userenv('LANG').
• Join base and translation rows: select b.doc_revision_id, tl.language, tl.comments from ahl_doc_revisions_b b, ahl_doc_revisions_tl tl where b.doc_revision_id = tl.doc_revision_id.
• Find revisions missing a translated row for a given language: an outer join from AHL_DOC_REVISIONS_B to AHL_DOC_REVISIONS_TL on DOC_REVISION_ID and LANGUAGE, filtering for null translation rows, supports translation-completeness reporting.
• Security-scoped reporting: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict results to the operating unit or security group of the running user.
• Audit and change tracking: query the WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY) to identify recently translated revisions.

Related Objects

The following objects are the most significant dependencies for this table, based on the documented foreign-key and primary-key relationships:

• AHL_DOC_REVISIONS_B — base table holding language-independent document revision data; joined on AHL_DOC_REVISIONS_TL.DOC_REVISION_ID = AHL_DOC_REVISIONS_B.DOC_REVISION_ID. This is the primary parent relationship.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID, providing the security group definition used for access partitioning.
• AHL_DOC_REVISIONS_TL_PK / AHL_DOC_REVISIONS_TL_U1 — the primary-key constraint and unique index that enforce one translation per revision per language and drive the index access paths for joins.
• Translation framework objects (FND_LANGUAGES) — supplies the installed language definitions used by the LANGUAGE and SOURCE_LANG columns.
• Document management and revision history tables in the AHL schema — consumed through the parent revision entity to present translated revision content in maintenance and repair workflows.