Search Results implement_status_code




Overview
Explore in AI Chat

Overview

The AHL_MR_HEADERS_APP_V view is a standard Oracle E-Business Suite application view owned by the APPS schema and delivered as part of the AHL (Complex Maintenance Repair and Overhaul) product family. It presents maintenance requirement (MR) header information in a translated, language-aware format, combining the base language-independent attributes stored in AHL_MR_HEADERS_B with the translated descriptive columns held in AHL_MR_HEADERS_TL. In Oracle EBS 12.1.1 and 12.2.2 the view carries a VALID status and is used throughout AHL reporting, forms, and integration layers as the primary read interface for MR header data.

A distinguishing characteristic of this view is its inclusion of the APPLICATION_USG_CODE filter. The view text selects from AHL_MR_HEADERS_VL and restricts rows using WHERE APPLICATION_USG_CODE = RTRIM(LTRIM(FND_PROFILE.VALUE('AHL_APPLN_USAGE'))). This means the view is context-sensitive: it returns only those MR headers whose application usage code matches the current session value of the AHL_APPLN_USAGE profile option, trimmed of leading and trailing whitespace. This design supports deployments where a single instance hosts more than one AHL usage context.

Underlying Base Objects

Per the ETRM metadata, the documented referenced base objects are AHL_MR_HEADERS_VL (a VIEW) and FND_PROFILE (a PACKAGE). The AHL_MR_HEADERS_VL view in turn resolves to the two physical tables described in the product documentation: AHL_MR_HEADERS_B, which holds the base, language-independent columns, and AHL_MR_HEADERS_TL, which holds the translated columns (TITLE, DESCRIPTION, and COMMENTS) keyed by language. The FND_PROFILE package supplies the profile value used in the WHERE clause.

The dependency chain is therefore: AHL_MR_HEADERS_APP_V reads AHL_MR_HEADERS_VL, which joins AHL_MR_HEADERS_B and AHL_MR_HEADERS_TL, while FND_PROFILE.VALUE supplies the runtime filter value. Because the filter is applied through a profile call, the view is not a simple pass-through and cannot be treated as a static snapshot.

Key Columns

Common Use Cases and Queries

The view is commonly used in custom reports, concurrent programs, and OAF or Forms-based pages that need to display MR headers without directly joining the B and TL tables. Because the profile filter is implicit, queries return only rows valid for the current AHL application usage context. A typical inspection-oriented query, driven by the search term, is:

SELECT mr_header_id, title, version_number, mr_status_code, qa_inspection_type_code
FROM apps.ahl_mr_headers_app_v
WHERE qa_inspection_type_code IS NOT NULL
AND mr_status_code = 'ACTIVE';

Analysts can group MR headers by inspection type to gauge workload or compliance coverage:

SELECT qa_inspection_type_code, COUNT(*)
FROM apps.ahl_mr_headers_app_v
GROUP BY qa_inspection_type_code;

When a report must span all usage codes regardless of profile value, the underlying AHL_MR_HEADERS_VL or the base tables should be queried instead, since the profile filter is enforced exclusively within this view.