Search Results ahl_vwp_stages_b




Overview
Explore in AI Chat

Overview

The AHL_VWP_STAGES_B table is a core data object within the Oracle E-Business Suite (EBS) module for Complex Maintenance, Repair, and Overhaul (AHL). It serves as the primary repository for defining and storing discrete stages within a maintenance workflow. A stage represents a logical phase or grouping of tasks that must be completed as part of a complex service visit. The table's role is foundational to structuring and managing the sequence and dependencies of maintenance operations, enabling detailed planning, execution tracking, and reporting for service activities. Its existence is critical for the proper functioning of the AHL module's work planning capabilities.

Key Information Stored

The table's primary key is the STAGE_ID column, which uniquely identifies each stage record. A fundamental foreign key is the VISIT_ID, which links the stage to its parent service visit defined in the AHL_VISITS_B table. While the provided metadata does not list all columns, typical columns in such a base table would include attributes for sequencing (e.g., SEQUENCE_NUMBER), status control (e.g., STAGE_STATUS_CODE), scheduling dates (planned and actual start/end), and descriptive information. The table likely also contains standard Oracle EBS WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) for auditing, along with OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

This table is central to operations involving the breakdown and management of a maintenance visit. Common use cases include generating a work plan summary for a visit, calculating stage-level progress, and identifying bottlenecks. A typical reporting query would join AHL_VWP_STAGES_B to AHL_VISITS_B to list all stages for a specific visit or customer. For performance analysis, queries often aggregate data from child tasks (in AHL_VISIT_TASKS_B) to compare planned versus actual duration at the stage level. Developers use this table when building custom integrations to extract stage information or when creating triggers to enforce business rules upon stage status changes. A fundamental query pattern is:

  • SELECT stage.stage_id, stage.sequence_number, visit.visit_number FROM ahl_vwp_stages_b stage, ahl_visits_b visit WHERE stage.visit_id = visit.visit_id AND visit.visit_id = :p_visit_id ORDER BY stage.sequence_number;

Related Objects

The AHL_VWP_STAGES_B table is a central node in the AHL data model with documented relationships to several key objects. Its primary key is referenced by the translated descriptions table, AHL_VWP_STAGES_TL (via STAGE_ID), which holds multilingual stage names. It has a foreign key relationship to AHL_VISITS_B (via VISIT_ID), establishing the parent visit. Furthermore, it is the parent table for AHL_VISIT_TASKS_B, where the STAGE_ID foreign key in that table links individual maintenance tasks to their parent stage. This hierarchy—Visit to Stage to Task—forms the structural backbone of the AHL work planning process.