Results for “implement_status_code”

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

Overview

APPS.AHL_MR_HEADERS_V is a reporting view in the Oracle E-Business Suite AHL (Complex Maintenance Repair and Overhaul) product, valid in both release 12.1.1 and 12.2.2. It presents maintenance requirement (MR) header information in a denormalized, human-readable form. The view is defined primarily over the translated header view AHL_MR_HEADERS_VL, joined to FND_LOOKUP_VALUES_VL to resolve the descriptive meaning of the various coded columns maintained on the MR header, and to AHL_MR_HEADERS_B to expose the title and revision of any preceding (superseded) maintenance requirement. In this way the view converts stored code values — category, service type, status, implementation status, and similar flags — into their meaningful display strings, while preserving all descriptive and attribute columns of the underlying header. Its role is to serve as the standard read interface for MR headers, suitable for concurrent-program extracts, Oracle Reports, OBIEE/BI Publisher data models, and custom inquiry pages that must show meaningful values rather than raw codes. Because it exposes the complete header record together with its textual descriptions, it is the natural starting point for any reporting or integration requirement that needs MR header context without navigating to each lookup individually.

Underlying Base Objects

According to the documented view metadata, AHL_MR_HEADERS_V is defined over the following referenced objects: AHL_MR_HEADERS_B (SYNONYM), AHL_MR_HEADERS_TL (SYNONYM), AHL_WARRANTY_TEMPLATES_B (SYNONYM), FND_LOOKUP_VALUES (SYNONYM), FND_LOOKUP_VALUES_VL (VIEW), FND_PROFILE (PACKAGE), MTL_SYSTEM_ITEMS_KFV (SYNONYM), and QA_CHAR_VALUE_LOOKUPS (SYNONYM).

AHL_MR_HEADERS_B stores the base, non-translated MR header rows — identifiers, version number, preceding MR reference, coded attributes, effective dates, flags, and descriptive flexfield columns. AHL_MR_HEADERS_TL holds the translated title, description, and comments, which are exposed through the language-sensitive AHL_MR_HEADERS_VL. The lookup synonyms (including FND_LOOKUP_VALUES and its view variant FND_LOOKUP_VALUES_VL) supply the MEANING and DESCRIPTION strings used to replace stored codes with readable text. The AHL_MR_HEADERS_B alias (shown in the implementation text as PMR) is joined again on PRECEDING_MR_HEADER_ID to retrieve the preceding MR's title and revision. MTL_SYSTEM_ITEMS_KFV supplies the concatenated, key-flexfield item segments for the billing item, and QA_CHAR_VALUE_LOOKUPS and AHL_WARRANTY_TEMPLATES_B support quality-inspection and warranty-related lookups. The FND_PROFILE package is referenced in the profile-dependent logic that governs language and security handling. User-facing code should query this view rather than the base tables to avoid reimplementing the lookup joins.

Key Columns

• MR_HEADER_ID — primary identifier of the maintenance requirement header; the join key to MR lines and operations.
• TITLE, VERSION_NUMBER, REVISION — the MR title and its revision/version context, sourced from the base and translated tables.
• PRECEDING_MR_HEADER_ID, PMR.TITLE, PMR.REVISION — the identifier and descriptive title/revision of the MR this header supersedes, enabling revision-chain reporting.
• CATEGORY_CODE, SERVICE_TYPE_CODE, MR_STATUS_CODE, IMPLEMENT_STATUS_CODE, PROGRAM_TYPE_CODE, PROGRAM_SUBTYPE_CODE, TYPE_CODE, SPACE_CATEGORY_CODE — coded classifications; each is accompanied by a corresponding lookup MEANING column.
• REPETITIVE_FLAG, SHOW_REPETITIVE_CODE, WHICHEVER_FIRST_CODE, COPY_ACCOMPLISHMENT_FLAG — behavioral flags controlling scheduling and copy semantics, with resolved meanings.
• EFFECTIVE_FROM / EFFECTIVE_TO — validity window of the MR header.
• DESCRIPTION, COMMENTS — translated narrative text for the header.
• SERVICE_REQUEST_TEMPLATE_ID, BILLING_ITEM_ID, BILLING_ORG_ID, MTL — service-request and billing references, where MTL is the concatenated segment string of the billing item.
• QA_INSPECTION_TYPE_CODE, QA.DESCRIPTION — quality-inspection type and its description.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segment values.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO and optimistic-locking audit columns.

Common Use Cases and Queries

A typical use is listing all active MR headers with their descriptive classifications for a status dashboard or extract:

SELECT mr_header_id, title, version_number, revision,
       category_code, mr_status_code, effective_from, effective_to
FROM   apps.ahl_mr_headers_v
WHERE  mr_status_code = 'RELEASED'
ORDER  BY last_update_date DESC;

To report the revision chain of superseded maintenance requirements, the preceding MR columns are used:

SELECT c.title AS current_title, c.revision AS current_rev,
       p.title AS preceding_title, p.revision AS preceding_rev
FROM   apps.ahl_mr_headers_v c
WHERE  c.preceding_mr_header_id IS NOT NULL;

To verify billing item configuration on maintenance requirements, the concatenated item segments are retrieved without an additional join:

SELECT mr_header_id, title, billing_item_id, billing_org_id, mtl
FROM   apps.ahl_mr_headers_v
WHERE  billing_item_id IS NOT NULL;

These queries are read-only and consistent with the view's intended reporting purpose. Because the view performs multiple outer joins to lookup and item tables, selective predicates on MR_STATUS_CODE, CATEGORY_CODE, or EFFECTIVE dates significantly reduce execution cost on large AHL installations.