Search Results ahl_mr_intervals_app_v




Overview
Explore in AI Chat

Overview

AHL_MR_INTERVALS_APP_V is a global, multi-org aware application view owned by the APPS schema in Oracle E-Business Suite, belonging to the AHL (Complex Maintenance Repair and Overhaul) product family. Its primary purpose is to expose maintenance interval definitions — the value, counter, date or usage thresholds used to trigger scheduled maintenance activities — while enriching each row with the Application Usage Code resolved from the parent maintenance effectivity. The "_APP_V" suffix indicates that the view is designed for consumption by application code and by reporting or integration layers, rather than representing a raw base entity. The view is documented as VALID in ETRM 12.2.2, and the same definition is shipped in 12.1.1 and 12.2.2, so queries written against it are portable across both releases.

Underlying Base Objects

The view is defined over the following documented objects:

  • AHL_MR_INTERVALS (base table, referenced through a synonym) — the driver object supplying all interval attributes, aliased as C in the view text.
  • AHL_MR_EFFECTIVITIES_APP_V (view, aliased A) — supplies the effectivity context and the APPLICATION_USG_CODE.
  • AHL_MR_HEADERS_APP_V (view, aliased B) — provides the maintenance header linkage used to correlate effectivities with their owning header.
  • FND_PROFILE (package) — referenced by the underlying _APP_V views as part of the standard multi-org / security profile resolution mechanism.

The join logic is: A.MR_HEADER_ID = B.MR_HEADER_ID AND A.MR_EFFECTIVITY_ID = C.MR_EFFECTIVITY_ID. Because AHL_MR_INTERVALS carries a SECURITY_GROUP_ID and the upstream effectivity and header views apply organization security context, the composite view returns only intervals whose effectivity is reachable through the appropriate operating unit. Each interval row is therefore effectively scoped by its maintenance header and effectivity.

Key Columns

  • MR_INTERVAL_ID — Primary key of the interval record.
  • MR_EFFECTIVITY_ID — Foreign key to the maintenance effectivity to which the interval belongs.
  • COUNTER_ID — The counter (for example, an odometer or cycle counter) against which the interval is measured.
  • INTERVAL_VALUE — The recurring interval magnitude at which maintenance repeats.
  • START_VALUE / STOP_VALUE — Numeric counter boundaries within which the interval applies.
  • START_DATE / STOP_DATE — Date boundaries for date-based interval scheduling.
  • TOLERANCE_BEFORE / TOLERANCE_AFTER — Permitted early and late execution windows around the due point.
  • RESET_VALUE — Value to which the counter is reset after maintenance is performed.
  • APPLICATION_USG_CODE — Sourced from AHL_MR_EFFECTIVITIES_APP_V; identifies the application usage context of the effectivity.
  • OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO and optimistic-locking audit columns.
  • SECURITY_GROUP_ID, ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15 — Multi-org security and descriptive flexfield (DFF) context columns inherited from the base table.

Common Use Cases and Queries

Typical scenarios include maintenance program reporting, interval validation for scheduled maintenance generation, and downstream integration feeds that require intervals joined to their application usage context. Because the view already resolves the header and effectivity join, reporting queries are simplified.

List all intervals for a given effectivity:

SELECT mr_interval_id, counter_id, interval_value,
       start_value, stop_value, tolerance_before, tolerance_after
FROM   ahl_mr_intervals_app_v
WHERE  mr_effectivity_id = :p_effectivity_id;

Identify date-based intervals within a window:

SELECT mr_interval_id, start_date, stop_date, application_usg_code
FROM   ahl_mr_intervals_app_v
WHERE  start_date >= :p_from_date
AND    stop_date  <= :p_to_date
ORDER BY start_date;

Reporting the usage context of all defined intervals:

SELECT application_usg_code, COUNT(*)
FROM   ahl_mr_intervals_app_v
GROUP BY application_usg_code;

As with all _APP_V views, queries should not assume rows are returned without organization context; callers must ensure the correct operating unit is initialized so that SECURITY_GROUP_ID filtering behaves as expected. The view is read-only and should not be used for inserts or updates, which must be directed to AHL_MR_INTERVALS.