Results for “ahl_visit_tasks_b_u2”

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

Overview

AHL.AHL_VISIT_TASKS_B is the base transactional table within the Oracle E-Business Suite (EBS) Complex Maintenance, Repair, and Overhaul (CMRO) / Enterprise Asset Management (AHL) schema that stores the individual task lines belonging to a visit. Each row represents a discrete maintenance, repair, or service activity scheduled against a visit header, capturing planning attributes, execution status, pricing, quantity, and sourcing references used by the Service/Repair scheduling engine. In EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and is registered in FND Design Data as AHL.AHL_VISIT_TASKS_B with a VALID status.

From a dimensional modeling perspective (Data Vault heuristic), the FK structure—multiple inbound foreign keys referencing independent business entities such as visits, material requirements, unit effectivity, service requests, and projects—suggests classifying this table as a hub, with its unique business keys acting as the natural candidates for hub key derivation. The table is paired with a translated table (AHL_VISIT_TASKS_TL) that carries language-dependent descriptive fields keyed by VISIT_TASK_ID.

Key Information Stored

The table contains 61 documented columns. The surrogate primary key is VISIT_TASK_ID, exposed through the unique index AHL_VISIT_TASKS_B_U1, and is complemented by standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER for optimistic locking.

• Business-key candidates. The unique index AHL_VISIT_TASKS_B_U2 covers (VISIT_ID, VISIT_TASK_NUMBER), meaning every task line is uniquely identified within its parent visit by a user-facing task number. The user's search term ahl_visit_tasks_b_u2 refers directly to this composite unique index.
• Parent linkage. VISIT_ID is a foreign key to AHL_VISITS_B, anchoring each task to its visit header.
• Task hierarchy. ORIGINATING_TASK_ID (self-referencing FK), PRIMARY_VISIT_TASK_ID, COST_PARENT_ID, and SUMMARY_TASK_FLAG support parent/child and summary task structures.
• Asset and item context. INSTANCE_ID (FK to CSI_ITEM_INSTANCES) identifies the installed base instance; INVENTORY_ITEM_ID and ITEM_ORGANIZATION_ID identify the item and inventory organization.
• Material and repair references. MR_ID (FK to AHL_MR_HEADERS_B), MR_ROUTE_ID, and ORIGINATING_MR_HEADER_ID tie the task to material requirements and routing.
• Effectivity and scheduling. UNIT_EFFECTIVITY_ID (FK to AHL_UNIT_EFFECTIVITIES_B), START_FROM_HOUR, DURATION, START_DATE_TIME, and END_DATE_TIME define when and for how long the task runs.
• Commercial attributes. ESTIMATED_PRICE, ACTUAL_PRICE, PRICE_LIST_ID, and ACTUAL_COST capture pricing and cost.
• Quantity and returns. QUANTITY, TARGET_QTY, RET_SERVICEABLE_QTY, RET_UNSERVICEABLE_QTY, and RETURN_TO_SUPPLY_FLAG track returned material.
• Status and classification. STATUS_CODE, TASK_TYPE_CODE, SERVICE_TYPE_CODE, STAGE_TYPE_CODE, and DEPARTMENT_ID (FK to BOM_DEPARTMENTS) drive execution workflow.
• Cross-module references. SERVICE_REQUEST_ID (FK to CS_INCIDENTS_ALL_B) and PROJECT_TASK_ID (FK to PA_TASKS) link to Service and Projects.

Common Use Cases and Queries

Typical reporting and integration scenarios include retrieving all tasks for a visit, monitoring task status through execution, reconciling estimated versus actual cost, and populating maintenance work orders.

• List tasks for a visit. SELECT VISIT_TASK_ID, VISIT_TASK_NUMBER, STATUS_CODE, DURATION FROM AHL.AHL_VISIT_TASKS_B WHERE VISIT_ID = :p_visit_id ORDER BY VISIT_TASK_NUMBER;
• Task with translated description. Join to AHL_VISIT_TASKS_TL on VISIT_TASK_ID to retrieve language-specific text (2.2 supports multi-language).
• Cost variance reporting. Aggregate ESTIMATED_PRICE, ACTUAL_PRICE, and ACTUAL_COST by VISIT_ID, TASK_TYPE_CODE, or DEPARTMENT_ID.
• Hierarchy traversal. Use a recursive query on ORIGINATING_TASK_ID (or through AHL_TASK_LINKS) to explode summary tasks into child tasks.
• Work order bridge. Join to AHL_WORKORDERS on VISIT_TASK_ID to trace execution against scheduled tasks.
• Instance/billable reporting. Join INSTANCE_ID to CSI_ITEM_INSTANCES and INVENTORY_ITEM_ID to MTL_SYSTEM_ITEMS_B to report by customer asset.

Because VISIT_TASK_NUMBER is unique only within VISIT_ID, queries keyed on task number alone must always be qualified by the visit—this is the practical implication of index AHL_VISIT_TASKS_B_U2.

Related Objects

• AHL_VISITS_B — parent visit header; join on VISIT_ID.
• AHL_VISIT_TASKS_TL — translated descriptions; join on VISIT_TASK_ID.
• AHL_TASK_LINKS — task dependency/parent-child relationships; joins on both VISIT_TASK_ID and PARENT_TASK_ID.
• AHL_WORKORDERS — execution work orders; FK VISIT_TASK_ID.
• AHL_SCHEDULE_MATERIALS — scheduled material lines; FK VISIT_TASK_ID.
• AHL_SNAPSHOTS — historical snapshot of task state; FK VISIT_TASK_ID.
• AHL_MR_HEADERS_B and AHL_MR_ROUTES — material requirement headers and routing; joins on MR_ID and MR_ROUTE_ID.
• AHL_UNIT_EFFECTIVITIES_B — effectivity definition; join on UNIT_EFFECTIVITY_ID.
• CSI_ITEM_INSTANCES — installed base instance; join on INSTANCE_ID.
• MTL_SYSTEM_ITEMS_B, BOM_DEPARTMENTS, PA_TASKS, and CS_INCIDENTS_ALL_B — cross-module masters joined through INVENTORY_ITEM_ID, DEPARTMENT_ID, PROJECT_TASK_ID, and SERVICE_REQUEST_ID respectively.