Results for “ahl_visit_tasks_tl”

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

Overview

The AHL_VISIT_TASKS_TL table resides in the AHL schema, which supports the Complex Maintenance Repair and Overhaul (CMRO) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a translation (TL) table that stores language-specific, multilingual descriptive content for visit tasks maintained within the CMRO visit planning framework. In Oracle EBS, the "_TL" suffix convention designates a table that holds translated attribute values keyed by language, while the corresponding "_B" (base) table stores the language-independent, operational data. The base table for this object is AHL_VISIT_TASKS_B, and AHL_VISIT_TASKS_TL holds only the user-enterable translated columns — notably the visit task name and description.

Applying a heuristic Data Vault classification based on the foreign key structure, this table is satellite-leaning. In Data Vault modeling terms, it behaves like a satellite attached to the AHL_VISIT_TASKS_B hub, capturing descriptive and translated attributes for each visit task entity rather than acting as a hub or link. This classification is a modeling suggestion derived from the FK topology, not an official Oracle designation.

Key Information Stored

The table is documented with 11 physical columns. The most significant are summarized below.

• VISIT_TASK_ID — The surrogate identifier of the parent visit task. It is the first component of the composite primary key AHL_VISIT_TASKS_TL_PK and forms the foreign key to AHL_VISIT_TASKS_B.VISIT_TASK_ID.
• LANGUAGE — The NLS language code identifying the translation. Combined with VISIT_TASK_ID, it constitutes the composite primary key and mirrors the unique index AHL_VISIT_TASKS_TL_U1 (VISIT_TASK_ID, LANGUAGE), which is the business-key candidate for this object.
• VISIT_TASK_NAME — The translated, language-specific name of the visit task, the primary human-readable translated attribute.
• DESCRIPTION — The translated long description providing detailed context for the visit task in the selected language.
• SOURCE_LANG — The language of the source (base) record from which the translation was derived, used by the translation framework to track provenance.
• SECURITY_GROUP_ID — The security group (operating unit) to which the row is scoped; it carries a foreign key to FND_SECURITY_GROUPS for multi-org and data-security filtering.
• LAST_UPDATE_DATE — Timestamp of the most recent modification, central to concurrent-program incremental extraction.
• LAST_UPDATED_BY — The application user who last modified the row.
• CREATION_DATE — Timestamp when the translation row was created.
• CREATED_BY — The application user who created the row.
• LAST_UPDATE_LOGIN — The login identifier associated with the most recent update.

The surrogate primary key is the composite (VISIT_TASK_ID, LANGUAGE); the same pair is also the documented unique index and therefore the business-key candidate. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit and high-water-mark tracking.

Common Use Cases and Queries

Typical usage centers on retrieving visit task names and descriptions in the user's session language, and on building bilingual or multilingual maintenance reports. A common pattern joins the translation table to the base table to surface the correct language row:

• Fetch the translated name for a specific task and language:
  SELECT b.visit_task_id, t.visit_task_name, t.description
FROM ahl_visit_tasks_b b, ahl_visit_tasks_tl t
WHERE b.visit_task_id = t.visit_task_id
AND t.language = USERENV('LANG');
• Incremental extraction for a data warehouse using the audit columns:
  SELECT * FROM ahl_visit_tasks_tl
WHERE last_update_date >= :last_run_date;
• Detecting missing translations by comparing base records against translated rows per language.
• Security-scoped reporting filtered on SECURITY_GROUP_ID to honor operating-unit access.

Because SOURCE_LANG and LANGUAGE frequently differ, reports should always constrain language explicitly to avoid duplicate output when multiple translations exist.

Related Objects

The following objects are most significant to this table based on the documented relationship data.

• AHL_VISIT_TASKS_B — The base (language-independent) visit task table; joined on VISIT_TASK_ID. It is the parent of the FK from AHL_VISIT_TASKS_TL.VISIT_TASK_ID.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; governs data security and multi-org scoping.
• AHL_VISIT_TASKS_TL_PK — The composite primary key constraint (VISIT_TASK_ID, LANGUAGE).
• AHL_VISIT_TASKS_TL_U1 — The unique index (VISIT_TASK_ID, LANGUAGE) serving as the business-key candidate.
• Visit task scheduling and visit planning interfaces that read translated task labels for display in CMRO work execution screens.

Together these objects form the visit task translation layer within the AHL module, linking operational task data to localized user-facing text through the VISIT_TASK_ID and LANGUAGE keys.