Results for “ahl_visit_tasks_v”

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

Overview

AHL_VISIT_TASKS_V is a reporting and integration view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the AHL product family, Complex Maintenance Repair and Overhaul (CMRO), a module used in heavily regulated and asset-intensive industries such as aerospace, defense, and utilities. The view consolidates visit-level and visit-task-level information into a single denormalized access point, joining visit header data with task detail data.

The view presents maintenance and overhaul tasks associated with a specific maintenance visit — a discrete service event during which one or more tasks are executed against an asset or inventory item. Its primary role is to support operational reporting, costs and pricing analysis, task scheduling displays, and downstream integrations that must retrieve visit tasks without navigating the normalized _B and _TL table pairs directly. Its status is documented as VALID, indicating a compiled and available object in the APPS schema.

Underlying Base Objects

The ETRM metadata documents the view as being defined over four referenced objects, all resolved through APPS-owned synonyms and related views:

• AHL_VISIT_TASKS_B (SYNONYM) — the base table holding visit task records, aliased as B. Provides the task identifiers, foreign keys, cost and price columns, descriptive flexfields, and audit columns.
• AHL_VISIT_TASKS_TL (SYNONYM) — the translation table, aliased as T. Supplies language-dependent attributes, namely VISIT_TASK_NAME and DESCRIPTION.
• AHL_VISITS_VL (VIEW) — the visit header view, aliased as C. Contributes VISIT_NUMBER and SIMULATION_PLAN_ID.
• AHL_SIMULATION_PLANS_B (SYNONYM) — the simulation plan table, aliased as D, used here only as a filter and not projected into the output.
• FND_LOOKUP_VALUES_VL (VIEW) — referenced within an inline scalar subquery to translate the AHL_APS_APPLICATION lookup code 'CMRO' into its display meaning.

Join predicates enforce B.VISIT_TASK_ID = T.VISIT_TASK_ID, B.VISIT_ID = C.VISIT_ID, and C.SIMULATION_PLAN_ID = D.SIMULATION_PLAN_ID. Critically, the view restricts output to the primary simulation plan via D.PRIMARY_PLAN_FLAG = 'Y', and restricts translated text to the session language using T.LANGUAGE = USERENV('LANG'). As a result, only tasks belonging to the primary plan of each visit are returned, and only one language row per task is exposed.

Key Columns

• ROW_ID — the ROWID of the AHL_VISIT_TASKS_B row, useful for identifying the base record.
• VISIT_TASK_ID / VISIT_TASK_NUMBER — the primary key and system-assigned task number.
• VISIT_ID / VISIT_NUMBER — links the task to its parent visit and exposes the visit number.
• VISIT_TASK_NAME / DESCRIPTION — language-dependent name and description sourced from AHL_VISIT_TASKS_TL.
• CONCATENATED_VISIT_TASK — a computed display string composed as VISIT_NUMBER || '.' || VISIT_TASK_NUMBER || '. ' || meaning of 'CMRO', intended for user-facing lists and reports.
• PROJECT_TASK_ID, MR_ROUTE_ID, MR_ID, SERVICE_REQUEST_ID — cross-module references to Projects, maintenance routes, and service requests.
• INVENTORY_ITEM_ID, ITEM_ORGANIZATION_ID, INSTANCE_ID — identify the item, its organization, and the specific instance (serialized unit) under maintenance.
• PRIMARY_VISIT_TASK_ID, SUMMARY_TASK_FLAG, ORIGINATING_TASK_ID — support task hierarchies, summarizing parent tasks and originating task relationships.
• START_FROM_HOUR, DURATION, UNIT_EFFECTIVITY_ID — scheduling and effectivity attributes.
• TASK_TYPE_CODE, DEPARTMENT_ID, STATUS_CODE — classification and workflow-state attributes.
• ACTUAL_COST, ESTIMATED_PRICE, ACTUAL_PRICE, PRICE_LIST_ID — financial columns supporting cost capture and pricing analysis.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — descriptive flexfield segments.
• SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER — multi-organization security and optimistic locking support.

Common Use Cases and Queries

Typical usage includes listing all tasks for a given visit, producing cost and price variance reports, feeding task data into scheduling or shop-floor dashboards, and extracting task details for integration. Because the view already filters to the primary simulation plan and the session language, it simplifies reporting logic considerably.

Retrieve all tasks for a specific visit:

SELECT VISIT_NUMBER, VISIT_TASK_NUMBER, VISIT_TASK_NAME, STATUS_CODE, DURATION
FROM APPS.AHL_VISIT_TASKS_V
WHERE VISIT_ID = :p_visit_id
ORDER BY START_FROM_HOUR;

Compare estimated and actual pricing by task:

SELECT CONCATENATED_VISIT_TASK, ESTIMATED_PRICE, ACTUAL_PRICE, ACTUAL_COST
FROM APPS.AHL_VISIT_TASKS_V
WHERE STATUS_CODE = 'COMPLETE';

Locate tasks for a specific inventory item or instance:

SELECT VISIT_TASK_ID, VISIT_TASK_NAME, TASK_TYPE_CODE
FROM APPS.AHL_VISIT_TASKS_V
WHERE INVENTORY_ITEM_ID = :p_item_id
AND INSTANCE_ID = :p_instance_id;

Analysts should note that the PRIMARY_PLAN_FLAG = 'Y' restriction means tasks tied solely to non-primary simulation plans will not appear. Reports requiring all simulation plans must query AHL_VISIT_TASKS_B and AHL_VISITS_VL directly rather than relying on this view. Similarly, the language restriction means translations are returned only for the current session language, which should be considered when building multilingual or batch extraction processes.