Results for “task_type_code”

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

Overview

APPS.AHL_SEARCH_VISIT_TASK_V is a read-only database view in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments, owned by the APPS schema and shipped as part of the AHL – Complex Maintenance Repair and Overhaul (CMRO) product family. Its documented purpose is to store the query used by the Search Visit Tasks screen to retrieve visit task information. In practice, the view functions as the data access layer behind that screen, joining visit header data, visit task detail, master route configuration, asset instance data, service requests, departments, and the work orders generated against visit tasks into one denormalized result set.

The view is heavily used in reporting and integration scenarios because it consolidates attributes that normally reside across a dozen or more AHL, CSI, CS, BOM, and MTL objects. The reference to WORKORDER_ID in the view text (aliased from AWO.WORKORDER_ID in AHL_WORKORDERS) is the primary correlation point between a scheduled visit task and its execution work order, which is why users searching for "work_order_id" land on this object. Only non-template visits are returned, because the view filters AVTS.TEMPLATE_FLAG = 'N'.

Underlying Base Objects

The view is defined over the following documented base objects:

• AHL_VISITS_VL – visit header (VISIT_ID, VISIT_NUMBER, TEMPLATE_FLAG, STATUS_CODE).
• AHL_VISIT_TASKS_VL – visit task detail, joined twice: once as ATSK for the task itself and once as ORIGTSK for the originating task.
• AHL_WORKORDERS – work order execution records (WORKORDER_ID, WORKORDER_NAME, STATUS_CODE, actual dates).
• AHL_MR_ROUTES_V and AHL_MR_HEADERS_VL – master route and route header information.
• AHL_UNIT_EFFECTIVITIES_VL – unit effectivity ranges applicable to the task.
• CSI_ITEM_INSTANCES – serialized asset instance (SERIAL_NUMBER).
• CS_INCIDENTS_ALL_B – service request / incident (INCIDENT_NUMBER).
• BOM_DEPARTMENTS – owning department description.
• MTL_SYSTEM_ITEMS_B_KFV – concatenated item segments for the inventory item.
• FND_LOOKUP_VALUES_VL – joined twice to translate TASK_TYPE_CODE and work order STATUS_CODE into meanings.

All joins to optional parents (asset instance, service request, originating task, master route, unit effectivity, department, lookups) are outer joins, so a visit task is still returned even when those relationships are absent.

Key Columns

• VISIT_ID, VISIT_NUMBER – visit identity and user-facing number.
• VISIT_TASK_ID, VISIT_TASK_NUMBER, VISIT_TASK_NAME – task identity within the visit.
• WORKORDER_ID, WORKORDER_NAME – the execution work order linked to the visit task, along with its STATUS_CODE and ACTUAL_START_DATE / ACTUAL_END_DATE.
• INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, ITEM_ORGANIZATION_ID – the maintained item and its concatenated segment display.
• INSTANCE_ID, SERIAL_NUMBER – the maintained asset instance.
• MR_ROUTE_ID, ROUTE_NUMBER, TITLE, MR_ID – master route and route header context.
• SERVICE_REQUEST_ID, INCIDENT_NUMBER – originating service request.
• TASK_TYPE_CODE and its lookup MEANING, DEPARTMENT_ID and DEPARTMENT_NAME.
• ORIGINATING_TASK_ID, ORIGINATING_TASK_NUMBER, ORIGINATING_TASK_NAME – predecessor task linkage.
• UNIT_EFFECTIVITY_ID and DUE_DATE – effectivity and scheduling information.

Common Use Cases and Queries

Typical scenarios include locating the work order generated for a given visit task, reviewing all tasks on a visit with their statuses and actual dates, and reporting task-to-asset or task-to-service-request traceability.

Find work orders for a specific visit task number:

• SELECT VISIT_NUMBER, VISIT_TASK_NUMBER, WORKORDER_ID, WORKORDER_NAME, STATUS_CODE FROM APPS.AHL_SEARCH_VISIT_TASK_V WHERE VISIT_TASK_NUMBER = :task_number;

List all tasks and their work orders for a visit:

• SELECT VISIT_TASK_NUMBER, VISIT_TASK_NAME, WORKORDER_ID, WORKORDER_NAME, ACTUAL_START_DATE FROM APPS.AHL_SEARCH_VISIT_TASK_V WHERE VISIT_ID = :visit_id ORDER BY VISIT_TASK_NUMBER;

Because the view embeds FND_LOOKUP_VALUES joins and outer joins across large maintenance tables, queries should be filtered on indexed identifiers such as VISIT_ID, VISIT_TASK_ID, WORKORDER_ID, or INSTANCE_ID to avoid full scans. As with all AHL views, query it with read-only privileges and never attempt DML, since it is a non-updatable join view.