Search Results ahl_visits_b

Overview

The AHL_VISITS_B table is a core transactional entity within the Oracle E-Business Suite (EBS) module AHL (Complex Maintenance, Repair, and Overhaul). It serves as the primary data repository for visit records, which are fundamental to managing service events for assets, such as equipment or aircraft, within a maintenance organization. A visit typically represents a discrete instance where a unit is brought in for inspection, repair, or overhaul. This table is central to the CMRO lifecycle, linking maintenance requirements, work execution, and resource planning. Its status as VALID and its ownership under the AHL schema confirm it is a production-grade, application-managed table in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary key is the VISIT_ID, a unique system-generated identifier for each visit record. As indicated by its foreign key relationships, the table stores critical contextual and organizational data for a visit. This includes references to a simulation plan (SIMULATION_PLAN_ID), a project from Project Accounting (PROJECT_ID), a customer service request (SERVICE_REQUEST_ID), and the specific asset instance being serviced (ITEM_INSTANCE_ID). It also links to inventory items (INVENTORY_ITEM_ID and ITEM_ORGANIZATION_ID), the responsible department (DEPARTMENT_ID), and higher-level scheduling via the UNIT_SCHEDULE_ID. While specific descriptive columns are not listed in the metadata, the existence of a related translation table (AHL_VISITS_TL) suggests the base table holds seeded code columns, while translatable descriptions like the visit name or short description are stored in the TL table.

Common Use Cases and Queries

This table is essential for reporting and integration across CMRO processes. Common use cases include generating visit schedules, tracking the status of all active maintenance visits, and linking work orders to their parent visit. A typical query might join AHL_VISITS_B to asset, project, and service request tables to provide a comprehensive visit summary report. For example, to list visits with associated asset details and project numbers, one might use a SQL pattern such as:

• SELECT avb.VISIT_ID, cii.INSTANCE_NUMBER, pa.SEGMENT1 PROJECT_NUMBER, csr.INCIDENT_NUMBER
• FROM AHL_VISITS_B avb, CSI_ITEM_INSTANCES cii, PA_PROJECTS_ALL pa, CS_INCIDENTS_ALL_B csr
• WHERE avb.ITEM_INSTANCE_ID = cii.INSTANCE_ID(+)
• AND avb.PROJECT_ID = pa.PROJECT_ID(+)
• AND avb.SERVICE_REQUEST_ID = csr.INCIDENT_ID(+);

Data from this table is also critical for creating and managing the tasks, work orders, and space assignments associated with a visit.

Related Objects

AHL_VISITS_B has extensive relationships within the AHL schema and integrates with other EBS modules. Key child tables that depend on the VISIT_ID include AHL_VISIT_TASKS_B (for detailed task breakdowns), AHL_WORKORDERS (for execution), AHL_VWP_STAGES_B (for workflow stages), AHL_SPACE_ASSIGNMENTS (for facility planning), and AHL_SNAPSHOTS. Its primary foreign key relationships, as documented, integrate visits with core EBS entities: CSI_ITEM_INSTANCES (Assets), PA_PROJECTS_ALL (Projects), CS_INCIDENTS_ALL_B (Service), MTL_SYSTEM_ITEMS_B (Inventory), BOM_DEPARTMENTS (Resources), and AHL_UNIT_SCHEDULES (Scheduling). This network of relationships underscores the table's role as a central hub connecting asset management, service, projects, and execution within Oracle CMRO.