Results for “ahl_visit_tasks_b”

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

Overview

AHL_VISIT_TASKS_B is the base table within the Oracle E-Business Suite Advanced Service (AHL) module, more commonly known as Complex Maintenance Repair and Overhaul (CMRO). It stores the master definition of visit tasks — the discrete, schedulable units of maintenance or repair work that must be performed during a specific customer visit to a maintained asset. A visit, represented by the parent record in AHL_VISITS_B, groups together all tasks required at a given point in time (for example, a scheduled induction or inspection event), and each task line is captured in this table.

The table functions as the central transactional anchor for CMRO task execution. Because visit tasks drive material requirements, work orders, labor routing, and warranty entitlement, the record acts as the primary intersection between the customer service demand (incident/visit) and the execution supply (work order, material, department).

From a data modeling perspective, the ETRM heuristic classifies AHL_VISIT_TASKS_B as a hub. This is a suggested modeling classification, reflecting that it carries a system-generated surrogate primary key (VISIT_TASK_ID) and is referenced by numerous downstream tables, making it a stable, high-cardinality entity anchor around which satellite and link structures revolve.

Key Information Stored

The table contains 61 columns; the following are the most significant for understanding and querying the data:

• VISIT_TASK_ID — The surrogate primary key, populated via the sequence behind the AHL_VISIT_TASKS_B_PK constraint and enforced by the unique index AHL_VISIT_TASKS_B_U1. It is the identifier referenced by all child tables.
• VISIT_ID — Foreign key to AHL_VISITS_B. Identifies the visit under which this task is scheduled.
• VISIT_TASK_NUMBER — The business-facing task number. Together with VISIT_ID it constitutes the second unique key (AHL_VISIT_TASKS_B_U2), providing a user-recognizable alternative to the surrogate ID.
• ORIGINATING_TASK_ID — Self-referencing foreign key linking a task back to the task from which it was generated (e.g., a repeat or derived task).
• INSTANCE_ID — Reference to CSI_ITEM_INSTANCES, tying the task to the specific maintained asset instance in the field.
• INVENTORY_ITEM_ID and ITEM_ORGANIZATION_ID — Identify the item being serviced or the item associated with the task, joined against MTL_SYSTEM_ITEMS_B.
• MR_ROUTE_ID and MR_ID — Link the task to the maintenance route/repair definition (AHL_MR_ROUTES, AHL_MR_HEADERS_B) that governs the standard work performed.
• SERVICE_REQUEST_ID — Reference to CS_INCIDENTS_ALL_B, connecting the task to the originating customer service incident.
• PROJECT_TASK_ID — Links to PA_TASKS for project costing and integration with Oracle Projects.
• DEPARTMENT_ID — Foreign key to BOM_DEPARTMENTS, indicating the responsible execution department.
• STATUS_CODE and TASK_TYPE_CODE — Drive workflow and reporting on task state and classification.
• START_DATE_TIME / END_DATE_TIME, DURATION, START_FROM_HOUR — Scheduling attributes for the task window.
• QUANTITY, TARGET_QTY, RET_SERVICEABLE_QTY, RET_UNSERVICEABLE_QTY — Quantities processed and returned, central to repair yield measurement.
• ESTIMATED_PRICE / ACTUAL_PRICE / ACTUAL_COST — Financial attributes used for billing and cost roll-up.
• SUMMARY_TASK_FLAG and PRIMARY_VISIT_TASK_ID — Support hierarchical task roll-ups where one task summarizes others.

The fifteen ATTRIBUTE columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15) follow the standard Oracle EBS extensibility pattern (DDF) for customer-specific data.

Common Use Cases and Queries

Typical scenarios include task status dashboards, material requirement planning for a visit, and billing reconciliation.

To list all tasks for a given visit with their status:

• SELECT vt.VISIT_TASK_NUMBER, vt.STATUS_CODE, vt.START_DATE_TIME, vt.QUANTITY FROM AHL_VISIT_TASKS_B vt WHERE vt.VISIT_ID = :p_visit_id;

To find tasks whose summary status should roll up from child tasks:

• SELECT * FROM AHL_VISIT_TASKS_B WHERE PRIMARY_VISIT_TASK_ID IS NOT NULL;

To retrieve the asset instance and item for a task:

• SELECT vt.VISIT_TASK_NUMBER, cii.SERIAL_NUMBER, msi.SEGMENT1 FROM AHL_VISIT_TASKS_B vt, CSI_ITEM_INSTANCES cii, MTL_SYSTEM_ITEMS_B msi WHERE vt.INSTANCE_ID = cii.INSTANCE_ID AND vt.INVENTORY_ITEM_ID = msi.INVENTORY_ITEM_ID;

Common reports include: open task aging, scheduled versus actual duration variance, repair yield (target quantity versus returned serviceable quantity), and warranty-linked task analysis joining AHL_WARRANTY_ENTITLEMENTS.

Related Objects

• AHL_VISITS_B — Parent visit; join on VISIT_ID. Every task belongs to exactly one visit.
• AHL_VISIT_TASKS_B (self) — Join on ORIGINATING_TASK_ID or PRIMARY_VISIT_TASK_ID for task hierarchies and derivation.
• CSI_ITEM_INSTANCES — Maintained asset instance; join on INSTANCE_ID.
• MTL_SYSTEM_ITEMS_B — Item master; join on INVENTORY_ITEM_ID and ITEM_ORGANIZATION_ID.
• CS_INCIDENTS_ALL_B — Service request/incident origin; join on SERVICE_REQUEST_ID.
• AHL_MR_HEADERS_B / AHL_MR_ROUTES — Repair route definitions; join on MR_ID and MR_ROUTE_ID.
• AHL_WORKORDERS — Execution work orders generated for a task; child table referencing VISIT_TASK_ID.
• AHL_TASK_LINKS — Dependency structure between tasks; joins on VISIT_TASK_ID and PARENT_TASK_ID.
• AHL_VISIT_TASKS_TL — Translation table supplying the task description/name; join on VISIT_TASK_ID.
• AHL_SCHEDULE_MATERIALS and AHL_WARRANTY_ENTITLEMENTS — Downstream material planning and warranty relationships keyed by VISIT_TASK_ID.