Results for “ahl_visits_info_v”

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

Overview

APPS.AHL_VISITS_INFO_V is a reporting view in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, delivered under the AHL (Complex Maintenance Repair and Overhaul) product family. Its documented purpose is to store the query used to retrieve visit information. In EBS terminology a "visit" represents a scheduled maintenance, repair, or overhaul engagement associated with an item instance, typically an aircraft, component, or other serialized asset managed within an MRO context.

The view consolidates visit header data with descriptive attributes drawn from organization, department, item master, serial number, lookup, and simulation plan sources. Rather than requiring integrators and report authors to write the multi-table joins themselves, AHL_VISITS_INFO_V exposes a denormalized, human-readable projection that resolves codes to meanings and derives additional date and unit information through PL/SQL package calls. This makes it well suited to operational dashboards, visit workbench reports, and inbound/outbound integrations that need a single-row-per-visit representation. Because the view is owned by APPS and marked VALID, it is queryable by any responsibility with appropriate grants, and it is commonly reached through synonym definitions in downstream schemas.

The user search term "planned_end_date" is directly relevant here: the view aliases AVTS.CLOSE_DATE_TIME as PLANNED_END_DATE, which is the principal column used for planned completion of a visit.

Underlying Base Objects

The documented 12.2.2 metadata lists the following referenced base objects: AHL_VISITS_VL, AHL_SIMULATION_PLANS_VL, AHL_UNIT_EFFECTIVITIES_APP_V, AHL_VISIT_TASKS_B, AHL_VISIT_TASKS_VL, AHL_MC_HEADERS_B, AHL_UNIT_CONFIG_HEADERS, AHL_UTILITY_PVT, AHL_LTP_SPACE_SCHEDULE_PVT (referenced in the view text), BOM_DEPARTMENTS, CSI_ITEM_INSTANCES, FND_LOOKUP_VALUES_VL, FND_PROFILE, HR_ALL_ORGANIZATION_UNITS, and MTL_SYSTEM_ITEMS_KFV.

AHL_VISITS_VL is the primary driving source, supplying visit identity, numbering, dates, status, space category, and scheduling attributes. AHL_SIMULATION_PLANS_VL supplies the simulation plan name and the primary plan flag. CSI_ITEM_INSTANCES provides the serial number of the maintained unit. HR_ALL_ORGANIZATION_UNITS and BOM_DEPARTMENTS resolve organization and department names. MTL_SYSTEM_ITEMS_KFV provides concatenated item segments. Three FND_LOOKUP_VALUES_VL instances resolve visit type, space category, and status meanings. AHL_UNIT_EFFECTIVITIES_APP_V joined to AHL_VISIT_TASKS_B is used in a scalar subquery to compute the DUE_BY value as the maximum due date across visit tasks. The packages AHL_UTILITY_PVT and AHL_LTP_SPACE_SCHEDULE_PVT supply the derived unit name and derived end date respectively. Note that several organization and department joins are outer joins, so visits lacking those attributes still appear.

Key Columns

• VISIT_ID, VISIT_NUMBER, VISIT_NAME — primary identifier, business number, and descriptive name of the visit.
• ORGANIZATION_ID / ORGANIZATION_NAME — owning maintenance organization and its resolved name.
• DEPARTMENT_ID / DEPARTMENT_NAME — executing department and description.
• ITEM_INSTANCE_ID, SERIAL_NUMBER, UNIT_NAME — the maintained unit; UNIT_NAME is derived via AHL_UTILITY_PVT.GET_UNIT_NAME.
• INVENTORY_ITEM_ID, ITEM_DESCRIPTION — item and concatenated segments from MTL_SYSTEM_ITEMS_KFV.
• VISIT_TYPE_CODE / VISIT_TYPE_MEAN, SPACE_CATEGORY_CODE / SPACE_CATEGORY_MEAN, STATUS_CODE / STATUS_MEAN — coded values with lookup meanings.
• START_DATE_TIME, CLOSE_DATE_TIME (PLANNED_END_DATE), END_DATE_TIME — visit start, planned completion, and derived end date.
• START_TIME_HOURS, PLANNED_END_TIME_HOURS — hour-of-day components extracted for scheduling grids.
• SIMULATION_PLAN_ID, SIMULATION_PLAN_NAME, PRIMARY_PLAN_FLAG — simulation plan context.
• DUE_BY — maximum due date across associated visit tasks.
• OBJECT_VERSION_NUMBER, SCHEDULE_DESIGNATOR (MRP_SCH_DESIGNATOR) — concurrency control and MRP scheduling designator.

Common Use Cases and Queries

Typical uses include visit workbench reporting, planned-versus-actual completion analysis, capacity planning by organization or department, and integration extracts feeding external MRO or ERP systems. The following query returns visits whose planned end date falls within a date range:

• SELECT visit_number, visit_name, serial_number, organization_name, status_mean, planned_end_date, due_by FROM ahl_visits_info_v WHERE planned_end_date BETWEEN :p_from AND :p_to ORDER BY planned_end_date;

The next example groups open visits by organization and department for workload review:

• SELECT organization_name, department_name, COUNT(*) visit_count, MIN(planned_end_date) earliest_planned_end FROM ahl_visits_info_v WHERE status_meaning IS NOT NULL AND end_date_time IS NULL GROUP BY organization_name, department_name;

Because the view performs function-based derivations (UNIT_NAME, END_DATE_TIME) and a correlated subquery (DUE_BY), performance-sensitive extracts should filter aggressively on VISIT_ID, ORGANIZATION_ID, or the date columns, and should avoid applying functions to PLANNED_END_DATE in the WHERE clause so that any underlying indexes remain usable.