Results for “operations_h_id”

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

Overview

AHL_OPERATIONS_H_TL is a translation (TL) table within the Oracle E-Business Suite AHL module, which provides Complex Maintenance Repair and Overhaul (CMRO) functionality. It stores the language-specific translated attributes of operation history records, working in conjunction with the base table AHL_OPERATIONS_H_B to represent historical operation definitions in multiple installed languages. In an EBS 12.1.1 or 12.2.2 environment, the TL table exists primarily to support the Multilingual Support (MLS) architecture, allowing descriptions, remarks, and notes associated with operation history records to be presented in a user's session language.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object is satellite-leaning. The combination of a surrogate identifier inherited from the parent base table and a natural business key (the language code) is characteristic of a dependent descriptive satellite attached to the AHL_OPERATIONS_H_B hub. In heuristic terms, this table behaves as a satellite that holds translatable descriptive context tied to each operation history record.

Key Information Stored

The table comprises 12 documented columns. Its primary key, AHL_OPERATIONS_H_TL_PK, is defined over OPERATIONS_H_ID and LANGUAGE, and a unique index, AHL_OPERATIONS_H_TL_U1, exists on the same pair, making them the business-key candidates. OPERATIONS_H_ID is the foreign key that identifies the parent operation history record in AHL_OPERATIONS_H_B, while LANGUAGE specifies the language in which the descriptive text is stored.

The translatable payload is held in OPERATION_DESCRIPTION, REMARKS, and NOTE, each carrying the translated text for its respective language. SOURCE_LANG records the source language from which the current row was derived, which is important in MLS maintain-translation workflows. Standard EBS audit columns are also present: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. SECURITY_GROUP_ID is retained as a foreign key to FND_SECURITY_GROUPS, which supports the security-group architecture used to partition application data.

Common Use Cases and Queries

Reporting on operation history descriptions in a specific language is the most common use case. A typical query joins the TL and base tables and filters by the language code:

• Multilingual description report: SELECT b.OPERATIONS_H_ID, t.LANGUAGE, t.OPERATION_DESCRIPTION FROM AHL_OPERATIONS_H_B b, AHL_OPERATIONS_H_TL t WHERE b.OPERATIONS_H_ID = t.OPERATIONS_H_ID AND t.LANGUAGE = USERENV('LANG').
• Translation completeness audit: identify operation history records that lack a row in a given language, or whose SOURCE_LANG differs from the stored LANGUAGE.
• Remarks and notes extraction: retrieve REMARKS and NOTE for transmittal or maintenance history documentation in the reporting language.
• Security-scoped reporting: filter by SECURITY_GROUP_ID to align reporting output with the caller's security profile, joining to FND_SECURITY_GROUPS.

Because the table is maintained by the CMRO application, queries should generally be read-only and joined through the parent OPERATIONS_H_ID rather than keyed on the surrogate alone.

Related Objects

The most significant related object is AHL_OPERATIONS_H_B, the master (base) table that this translation table depends on through OPERATIONS_H_ID. AHL_OPERATIONS_H_TL references AHL_OPERATIONS_H_B.OPERATIONS_H_ID as a foreign key and is joined to it in nearly every query for translated content. The SECURITY_GROUP_ID column references FND_SECURITY_GROUPS, which participates in any security-scoped retrieval. Additional related objects include the parent operation history hierarchy within AHL that references the same OPERATIONS_H_ID, and the standard FND language and MLS metadata used to interpret LANGUAGE and SOURCE_LANG. The primary key constraint AHL_OPERATIONS_H_TL_PK and unique index AHL_OPERATIONS_H_TL_U1 enforce the one-row-per-language rule, and changes to the base table should be validated against this constraint before translation rows are inserted or updated.