Search Results ahl_mr_effectivities_app_v




Overview
Explore in AI Chat

Overview

APPS.AHL_MR_EFFECTIVITIES_APP_V is a reporting and integration view in the Oracle E-Business Suite AHL (Complex Maintenance Repair and Overhaul) module. In ETRM 12.1.1 and 12.2.2 it exposes maintenance requirement (MR) effectivity records together with their header-level usage context. Effectivities define the validity rules — keyed primarily by threshold date and optionally scoped to an inventory item, organization, or configured relationship — under which a maintenance requirement applies to a fleet asset or component. The view joins the effectivity base records to the application usage code of their parent MR header, which indicates the functional area in which the maintenance requirement is used. Because it is a view rather than a table, it provides a read-only, denormalized projection suitable for concurrent programs, OAF pages, reports, and outbound integrations, and it is owned by the APPS schema with status VALID.

Underlying Base Objects

The documented view text is a single inner join between two objects:

  • AHL_MR_EFFECTIVITIES (referenced via synonym) — the primary source, supplying the effectivity identifier, header reference, name, threshold date, item and organization references, relationship and node references, default flag, program duration, security group, and the fifteen descriptive flexfield attribute columns.
  • AHL_MR_HEADERS_APP_V (VIEW) — the joined header view, which contributes only APPLICATION_USG_CODE and supplies MR_HEADER_ID as the join key.

Documented metadata further records AHL_FLEET_HEADERS_B (SYNONYM) and the FND_PROFILE package as referenced objects in the dependency chain of the view family, consistent with the fleet- and profile-driven security and context logic used throughout AHL maintenance requirement setup. Because the join is an equi-join on MR_HEADER_ID with no outer clause, an effectivity row is returned only when a matching header exists in AHL_MR_HEADERS_APP_V.

Key Columns

Common Use Cases and Queries

Typical uses include listing effectivities for a specific maintenance requirement, locating the default effectivity, resolving date-driven applicability for a fleet item, and extracting flexfield attributes for integration or validation reports. Note the APPS synonym; query as APPS or with the APPS schema on the path.

  • All effectivities for a header: SELECT mr_effectivity_id, name, threshold_date, default_flag FROM ahl_mr_effectivities_app_v WHERE mr_header_id = :p_header_id ORDER BY threshold_date;
  • Item-scoped effectivities: SELECT e.mr_effectivity_id, e.threshold_date, e.inventory_item_id FROM ahl_mr_effectivities_app_v e WHERE e.inventory_item_id = :p_item AND e.inventory_org_id = :p_org;
  • Default effectivity lookup: SELECT mr_effectivity_id, name FROM ahl_mr_effectivities_app_v WHERE default_flag = 'Y' AND mr_header_id = :p_header_id;
  • Usage-context extract: SELECT mr_header_id, mr_effectivity_id, application_usg_code, program_duration, program_duration_uom_code FROM ahl_mr_effectivities_app_v;

Because APPLICATION_USG_CODE and any fleet context derive from joined views and profile logic, confirm outer-join expectations in custom SQL when effectivities exist without a returned header row.