Search Results billing_item




Overview
Explore in AI Chat

Overview

AHL_MR_DETAILS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the AHL (Complex Maintenance Repair and Overhaul) product family. It presents consolidated Maintenance Requirements (MR) data by joining the header view AHL_MR_HEADERS_V with relationship and document-association views, so that each MR record is enriched with its parent MR title and revision as well as its originating document. The view exists specifically to support the MR Search function within the AHL module, where users query maintenance requirements by attributes such as title, revision, category, service type, or status. Rather than requiring the calling form or report to perform multiple joins across header, relationship, and document tables, AHL_MR_DETAILS_V delivers a single denormalized row per MR header that carries both structural context (parent/child relationships) and documentary provenance (source document title). Because it is a view and not a table, it holds no data of its own; all values are derived at runtime from the underlying AHL base tables. Its status is VALID, confirming that it compiles without error in the documented 12.1.1 and 12.2.2 environments. For reporting and integration purposes, it serves as a stable read-only interface that shields external queries from the more complex join logic inside the AHL data model.

Underlying Base Objects

The view is defined as an outer-join query over the following documented base objects: AHL_DOCUMENTS_B, AHL_DOCUMENTS_TL, AHL_DOC_REVISIONS_B, AHL_DOC_TITLE_ASSOS_B, AHL_MR_HEADERS_B, AHL_MR_HEADERS_TL, AHL_MR_RELATIONSHIPS, AHL_WARRANTY_TEMPLATES_B, FND_LOOKUP_VALUES, and the FND_PROFILE package — the latter two supplying lookup meanings and profile-driven values. Conceptually, AHL_MR_HEADERS_V supplies the core MR header and translated title/description information drawn from AHL_MR_HEADERS_B and AHL_MR_HEADERS_TL. AHL_MR_RELATIONSHIPS contributes parent-child linkage: the join condition restricts the relationship code to 'PARENT', and the parent title is resolved against the headers view aliased PMR. Document provenance is attached through the document association and document views, which trace back to AHL_DOC_TITLE_ASSOS_B, AHL_DOCUMENTS_B, AHL_DOCUMENTS_TL, and AHL_DOC_REVISIONS_B, filtered on object type 'MR' and source reference 'SOURCE'. All joins to the relationship and document sources use Oracle outer-join syntax (+), so an MR without a parent or without an originating document still returns a row, with NULLs in the corresponding columns.

Key Columns

Common Use Cases and Queries

The principal use case is the AHL MR Search screen, which drives this view to locate maintenance requirements by title, category, or status while displaying the parent and originating document context. The user's search term "source_doc_id" maps directly to the document traceability columns (DOCUMENT_ID, and the SOURCE_REF_CODE = 'SOURCE' association) that this view surfaces. A basic search query resembles:

SELECT mr_header_id, title, revision, category, status, document_title
FROM apps.ahl_mr_details_v
WHERE title LIKE :search_term
ORDER BY title;

To retrieve the source document for a given MR, the caller filters on the document columns exposed by the view, since the originating document is attached through the DOCUMENT_ID join rather than stored on the header itself. A typical traceability query is:

SELECT mr_header_id, title, document_id, document_title
FROM apps.ahl_mr_details_v
WHERE document_id IS NOT NULL
AND mr_header_id = :mr_header_id;

Additional scenarios include dependency analysis, where the parent title and preceding MR title columns reconstruct the revision and relationship hierarchy for a set of maintenance requirements, and status-based operational reporting, where decoded category, status, and implementation columns feed dashboards or concurrent programs. Because all joins are outer joins, queries that do not filter on document or parent columns return every MR header, making the view safe for broad listings as well as targeted retrieval.