Search Results ahl_mr_effectivity_dtls_app_v




Overview
Explore in AI Chat

Overview

The view APPS.AHL_MR_EFFECTIVITY_DTLS_APP_V is a public, applications-facing view within the Oracle E-Business Suite (EBS) Complex Maintenance Repair and Overhaul (AHL) module. It exposes manufacturer effectivity detail records in a denormalized form by joining the underlying effectivity detail table to header and effectivity views, thereby enriching each detail row with the originating application usage code. The view is documented as VALID in both the 12.1.1 and 12.2.2 releases and resides in the APPS schema, which confirms it is intended for use by reporting, integration, and form-based lookups rather than for direct transactional manipulation. Its naming convention — the _APP_V suffix — signals that it is an application-layer view layered over a base detail table, designed to simplify access patterns for downstream consumers such as Oracle Forms, OAF pages, concurrent programs, and third-party integrations.

Underlying Base Objects

The view text defines an inner join across three referenced objects. The primary detail source is AHL_MR_EFFECTIVITY_DTLS, consumed through the synonym in the APPS schema. This table supplies all effectivity detail attributes. It is joined to AHL_MR_EFFECTIVITIES_APP_V on MR_EFFECTIVITY_ID, which provides effectivity-level context and the APPLICATION_USG_CODE column. That view is in turn joined to AHL_MR_HEADERS_APP_V on MR_HEADER_ID, establishing the linkage between effectivity detail records and the maintenance repair (MR) header. The documented metadata also references FND_PROFILE, indicating that profile option resolution (commonly for security or org context) participates in the application view chain. The joins are strictly equi-joins, so only detail rows with matching effectivity and header records are returned.

Key Columns

The view exposes the full set of detail attributes plus the inherited application usage code. Principal columns include:

Common Use Cases and Queries

Typical uses include reporting on effectivity ranges for a given MR header, validating excludes versus includes, and integration extracts that require the application usage code alongside detail ranges. A representative query retrieving all details for a specific effectivity follows:

  • SELECT MR_EFFECTIVITY_DETAIL_ID, EXCLUDE_FLAG, MANUFACTURER_ID, COUNTRY_CODE, SERIAL_NUMBER_FROM, SERIAL_NUMBER_TO FROM APPS.AHL_MR_EFFECTIVITY_DTLS_APP_V WHERE MR_EFFECTIVITY_ID = :p_effectivity_id;
  • Filtering by usage: SELECT * FROM APPS.AHL_MR_EFFECTIVITY_DTLS_APP_V WHERE APPLICATION_USG_CODE = :p_code;
  • Extracting include-only ranges: SELECT * FROM APPS.AHL_MR_EFFECTIVITY_DTLS_APP_V WHERE NVL(EXCLUDE_FLAG,'N') = 'N';

Because the view performs inner joins, queries should account for the possibility that details lacking a matching header or effectivity are not returned, which is consistent with its role as an application-layer consumer view.