Search Results ahl_mr_instances_v




Overview
Explore in AI Chat

Overview

AHL_MR_INSTANCES_V is an APPS-owned database view in the Oracle E-Business Suite Release 12.1.1 / 12.2.2 environment, delivered as part of the AHL – Complex Maintenance Repair and Overhaul (CMRO) product family. Its documented purpose is "View To get all the Maintenance Requirements in Production." In practical terms, the view consolidates unit effectivity records, maintenance requirement headers, visit records, visit tasks, and master work orders into a single denormalized result set that reports the current production status of a maintenance requirement against a specific asset instance.

Because the view is built over the operational AHL transaction tables rather than a reporting-only snapshot, it reflects live production data. It is typically consumed by CMRO inquiry screens, Oracle Reports, BI Publisher layouts, and customer-written SQL used for maintenance dashboards and status reporting. The view derives the maintenance requirement status dynamically by calling AHL_COMPLETIONS_PVT.GET_MR_STATUS, so status values are not stored on the base tables but computed at query time.

Underlying Base Objects

The documented base objects referenced by the view include the unit effectivity and visit foundations of the AHL schema. The principal join path is:

The metadata also documents references to supporting objects such as AHL_UTILITY_PVT (used in the GET_UNIT_NAME call), AHL_COMPLETIONS_PVT, AHL_PRD_PRINT_PVT, FND_GLOBAL, FND_PROFILE, HR_GENERAL, HR_SECURITY, MO_GLOBAL, CSI_ITEM_INSTANCES, CS_INCIDENTS_ALL_VL, MTL_SYSTEM_ITEMS_KFV, and WIP_DISCRETE_JOBS, reflecting the view's inheritance of organization security and item master context.

Key Columns

Common Use Cases and Queries

Typical reporting scenarios include maintenance requirement status dashboards, upcoming visit schedules, and completion tracking per asset instance.

  • Upcoming visits by start date: 
    SELECT VISIT_NUMBER, VISIT_START_DATE, UNIT_NAME, STATUS
FROM   APPS.AHL_MR_INSTANCES_V
WHERE  VISIT_START_DATE >= TRUNC(SYSDATE)
ORDER  BY VISIT_START_DATE;
  • Production status for an asset instance: 
    SELECT INSTANCE_NUMBER, MR_TITLE, STATUS, ACTUAL_END_DATE
FROM   APPS.AHL_MR_INSTANCES_V
WHERE  CSI_ITEM_INSTANCE_ID = :instance_id;
  • Open requirements within an organization: 
    SELECT ORGANIZATION_NAME, VISIT_NUMBER, VISIT_START_DATE, STATUS
FROM   APPS.AHL_MR_INSTANCES_V
WHERE  ORGANIZATION_ID = :org_id
AND    STATUS_CODE NOT IN ('ACCOMPLISHED','ALL_JOBS_CLOSED');

Because status is computed through AHL_COMPLETIONS_PVT.GET_MR_STATUS, queries returning large result sets can be resource-intensive; filtering by ORGANIZATION_ID, UNIT_EFFECTIVITY_ID, or VISIT_START_DATE range is recommended. Organization-level security inherited from MO_GLOBAL and HR_SECURITY also applies, so results are naturally restricted to the operating unit context of the session.