Results for “ahl_visits_tl”

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

Overview

AHL_VISITS_TL is the translation table for visits maintained within the Oracle E-Business Suite Complex Maintenance Repair and Overhaul (AHL) module. In EBS Release 12.1.1 and 12.2.2, the AHL product supports depot-level maintenance, repair, and overhaul operations for complex assets such as aircraft, rail fleets, and defence equipment. A "visit" represents a scheduled or ad hoc maintenance event in which an asset arrives at a facility, undergoes work, and departs. AHL_VISITS_TL stores the language-specific, translatable attributes of those visits—principally the visit name and its descriptive text—so that the same visit record can surface in multiple installed languages.

The table follows the standard EBS "_TL" design pattern: one row per visit per language, keyed on the combination of the visit identifier and the language code. It is a pure dependent of AHL_VISITS_B, the base table holding language-independent visit data. Under the heuristic Data Vault classification derived from the foreign-key structure, AHL_VISITS_TL is satellite-leaning: it carries descriptive, time-variant context about the AHL_VISITS_B business key rather than acting as a hub or a link. This should be treated as a modeling suggestion, not an architectural constraint.

Key Information Stored

The documented physical schema comprises eleven columns. The most significant are:

• VISIT_ID – Surrogate identifier of the visit. Combined with LANGUAGE it forms the primary key AHL_VISITS_PK. The unique index AHL_VISITS_TL_U1 also covers (VISIT_ID, LANGUAGE), confirming this pair as the business-key candidate.
• LANGUAGE – The language code for the translated row, typically the NLS language of the session that created the record.
• VISIT_NAME – The translated display name of the visit; the primary user-visible attribute.
• DESCRIPTION – Free-text translated description providing additional context about the visit.
• SOURCE_LANG – The language in which the row was originally authored, used by the translation framework to identify the source for derived rows.
• SECURITY_GROUP_ID – References FND_SECURITY_GROUPS and enforces multi-tenant data segregation in a shared EBS instance, including hosted or multi-org deployments.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – Standard EBS audit columns recording who created and last modified the row, when, and from which login.

Common Use Cases and Queries

The dominant reporting requirement is to display visit information in the user's session language while falling back to the base record when no translated row exists. A typical query joins the base table to its translation using the composite key:

• Language-specific listing: SELECT b.visit_id, t.visit_name, t.description FROM ahl_visits_b b, ahl_visits_tl t WHERE b.visit_id = t.visit_id AND t.language = USERENV('LANG').
• Completeness audit: counting base rows without a corresponding translation row for a given language, to identify untranslated visits.
• Data extraction for integration or migration, filtering on SECURITY_GROUP_ID to restrict output to the relevant operating unit or tenant.
• Change tracking, using LAST_UPDATE_DATE and LAST_UPDATED_BY to reconcile translation maintenance performed in the Oracle EBS translation (NLS) framework.

Because the table holds only descriptive text, it should be joined rather than queried in isolation; direct DML is not recommended and is normally performed through the AHL visit maintenance forms or public APIs.

Related Objects

• AHL_VISITS_B – The base table; AHL_VISITS_TL.VISIT_ID references it, forming the parent-child translation pair that is the core join in every reporting query.
• FND_SECURITY_GROUPS – Referenced by SECURITY_GROUP_ID; governs access to translation rows in multi-tenant installations.
• AHL_VISIT_ITEMS and related visit line tables – Child entities of the visit that depend on the visit identified by VISIT_ID.
• AHL_WORKORDERS – Work orders executed during a visit; frequently joined for status and cost reporting by visit name.
• AHL_VISITS_V or equivalent visit views and AHL visit public APIs – Expose translated visit data and are the supported mechanisms for creating and maintaining visit records.
• FND_LANGUAGES – Provides the installed-language reference against which the LANGUAGE code is validated.