Results for “ahl_mr_intervals_v”

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

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, AHL_MR_INTERVALS_V is a reporting and integration view owned by the APPS schema within the AHL – Complex Maintenance Repair and Overhaul product. It presents the interval definitions used by maintenance requirement (MR) effectivities, enriched with the descriptive name of the associated counter and the unit of measure in which interval values are expressed. Rather than exposing raw foreign keys alone, the view resolves the counter name and UOM so that downstream reports, concurrent programs, and interfaces can consume interval data in a business-readable form. The view is documented as VALID and is built from the views AHL_MR_INTERVALS, CS_COUNTERS, and MTL_UNITS_OF_MEASURE_VL, with the underlying implementation selecting from AHL_MR_INTERVALS_APP_V joined to the counters and UOM views. Because it depends on the counters object CS_COUNTERS — the object most directly associated with the search term "cs_counters" — this view is frequently encountered when investigating counter-driven maintenance intervals.

Underlying Base Objects

The view joins the interval source to two supporting views. The documented referenced base objects include AHL_MR_EFFECTIVITIES, AHL_MR_HEADERS_B, AHL_MR_INTERVALS, CS_COUNTERS, FND_GLOBAL, FND_LOOKUPS, FND_PROFILE, and MTL_UNITS_OF_MEASURE_VL. The primary join conditions are I.COUNTER_ID = C.COUNTER_ID and C.UOM_CODE = M.UOM_CODE. This means the counter record supplies the UOM code, which is then resolved to a unit of measure description through MTL_UNITS_OF_MEASURE_VL. References to FND_GLOBAL, FND_PROFILE, and FND_LOOKUPS indicate that the underlying app view applies organization and language context, which is typical of multi-org and MLS-aware ETRM views.

Key Columns

• MR_INTERVAL_ID – Primary identifier of the maintenance requirement interval.
• OBJECT_VERSION_NUMBER – Optimistic locking version, relevant during updates.
• MR_EFFECTIVITY_ID – Links the interval to its parent maintenance requirement effectivity.
• COUNTER_ID / COUNTER_NAME – The counter identifier and the resolved counter name from CS_COUNTERS.
• UNIT_OF_MEASURE – UOM description derived from the counter's UOM code.
• INTERVAL_VALUE, START_VALUE, STOP_VALUE – The interval increment and its lower/upper bounds.
• START_DATE, STOP_DATE – Effective date range for the interval.
• TOLERANCE_BEFORE, TOLERANCE_AFTER – Acceptable thresholds either side of the interval.
• RESET_VALUE – Value at which the counter interval resets.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – Descriptive flexfield columns.
• APPLICATION_USG_CODE – Indicates the usage context of the interval.

Common Use Cases and Queries

The view is typically used to report counter-based maintenance intervals for a given counter or effectivity, and to validate that interval configuration is correctly aligned with the counter UOM.

• Listing intervals for a specific counter: SELECT mr_interval_id, counter_name, interval_value, unit_of_measure FROM apps.ahl_mr_intervals_v WHERE counter_id = :p_counter_id;
• Reviewing intervals by effectivity: SELECT * FROM apps.ahl_mr_intervals_v WHERE mr_effectivity_id = :p_effectivity_id;
• Auditing tolerance and reset configuration across counters: SELECT counter_name, start_value, stop_value, tolerance_before, tolerance_after, reset_value FROM apps.ahl_mr_intervals_v ORDER BY counter_name;

These queries support maintenance planning, interval verification, and integration extracts in AHL implementations.