Results for “ahl_aps_application”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.AHL_VISIT_TASKS_V is a reporting and integration view in the Oracle E-Business Suite Advanced Service (Complex Maintenance, Repair and Overhaul / Enterprise Asset Management) module. It presents visit task information — the individual tasks that make up a service visit — in a denormalized, language-aware form suitable for reports, concurrent programs, and external interfaces. The view resolves multilingual (TL) task name and description values against the current session language, and enriches each visit task with its parent visit number, simulation plan context, and a concatenated visit-task identifier. Because the view joins the transactional base table to its translation table and to the parent visit, it is the preferred object for read-only access to visit task data, avoiding the need for developers to replicate the language-filtering and simulation-plan logic themselves.
Underlying Base Objects
The view is defined over five documented objects:
- AHL_VISIT_TASKS_B — the base transactional table holding visit task rows (aliased B). Provides the majority of columns, including identifiers, dates, who-columns, and descriptive flexfield attributes.
- AHL_VISIT_TASKS_TL — the translation table (aliased T), joined on VISIT_TASK_ID and filtered by
T.LANGUAGE = USERENV('LANG')to return the task name and description in the session language. - AHL_VISITS_VL — the visit view (aliased C), joined on VISIT_ID, supplying visit_number and simulation_plan_id.
- AHL_SIMULATION_PLANS_B — the simulation plan table (aliased D), joined with an outer join (
(+)) on SIMULATION_PLAN_ID. The predicate restricts rows to the primary plan (d.primary_plan_flag = 'Y') or permits visits with no simulation plan at all. - FND_LOOKUP_VALUES_VL — used in a scalar subquery to resolve the meaning of the lookup type
AHL_APS_APPLICATION.
Key Columns
The view exposes the full transactional column set of AHL_VISIT_TASKS_B plus derived columns. Important identifiers include VISIT_TASK_ID (primary key), VISIT_TASK_NUMBER, VISIT_ID, PROJECT_TASK_ID, COST_PARENT_ID, MR_ROUTE_ID, MR_ID, INVENTORY_ITEM_ID, ITEM_ORGANIZATION_ID, INSTANCE_ID, PRIMARY_VISIT_TASK_ID, ORIGINATING_TASK_ID, SERVICE_REQUEST_ID, DEPARTMENT_ID, and UNIT_EFFECTIVITY_ID. Status and classification are represented by STATUS_CODE, TASK_TYPE_CODE, and SUMMARY_TASK_FLAG. Financial columns include PRICE_LIST_ID, ACTUAL_COST, ESTIMATED_PRICE, and ACTUAL_PRICE. Scheduling data appears in DURATION and START_FROM_HOUR. Descriptive flexfield support is provided through ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15. The derived CONCATENATED_VISIT_TASK column combines visit_number, visit_task_number, and the meaning of the AHL_APS_APPLICATION lookup value code CMRO, producing a human-readable label such as 1001.10. Corrective Maintenance. The view also returns ROW_ID (ROWID) and OBJECT_VERSION_NUMBER for ORM/versioning support, plus standard audit columns.
Common Use Cases and Queries
Typical uses include visit task reports, service work-order listings, and integrations needing translated task names. The simulation-plan filter ensures only primary plans are surfaced, which is essential for production reporting.
List all tasks for a visit:
SELECT visit_task_number, visit_task_name, status_code, task_type_code FROM apps.ahl_visit_tasks_v WHERE visit_id = :p_visit_id ORDER BY visit_task_number;
Display the concatenated task label with cost data:
SELECT concatenated_visit_task, actual_cost, actual_price FROM apps.ahl_visit_tasks_v WHERE status_code = 'COMPLETE';
Find tasks by item and organization:
SELECT visit_task_id, visit_task_name, inventory_item_id FROM apps.ahl_visit_tasks_v WHERE inventory_item_id = :p_item AND item_organization_id = :p_org;
Because the view applies USERENV('LANG') to the translation join, any report or interface that consumes AHL_VISIT_TASKS_V automatically returns locale-appropriate names, and customers requiring additional languages must ensure the corresponding AHL_VISIT_TASKS_TL rows exist.
-
Ahl Aps Application
-
Ahl Aps Application
-
VIEW: APPS.AHL_VISIT_TASKS_V 12.2.2
-
VIEW: APPS.AHL_VISIT_TASKS_V 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
View: AHL_VISIT_TASKS_V 12.1.1
This view is based Ahl_Visits_vl, Ahl_visit_tasks_vl
APPS.AHL_VISIT_TASKS_V·↳ AHL_SIMULATION_PLANS_B·↳ AHL_VISITS_VL·↳ AHL_VISIT_TASKS_B·Explore AHL module →
-
12.2.2 FND Design Data 12.2.2
-
View: AHL_VISIT_TASKS_V 12.2.2
This view is based Ahl_Visits_vl, Ahl_visit_tasks_vl
APPS.AHL_VISIT_TASKS_V·↳ AHL_SIMULATION_PLANS_B·↳ AHL_VISITS_VL·↳ AHL_VISIT_TASKS_B·Explore AHL module →