Results for “ahl_yes_no_type”

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

Overview

The view APPS.AHL_MR_HEADERS_V is a reporting and integration layer exposed by Oracle E-Business Suite for the Maintenance Management (Enterprise Asset Management) product family. It presents maintenance requirement headers — the top-level definition of a planned maintenance, service, or overhaul work specification — together with their translated descriptive text and a large set of decoded lookup meanings. The view is owned by the APPS schema and is intended to be consumed directly by reports, concurrent programs, OAF pages, and external integrations rather than queried at the base table level.

Its principal value is that it resolves raw code columns (status, category, service type, proposal type, UOM, and similar) into human-readable meanings by joining to the appropriate lookup and value-set sources in a single access path. This shelters reporting code from the underlying normalization of the AHL_MR_HEADERS_B / AHL_MR_HEADERS_TL pair and removes the need for report authors to write repeated lookup subqueries.

Underlying Base Objects

The view is defined over a join of the base table AHL_MR_HEADERS_B (aliased MR) and its translation table AHL_MR_HEADERS_TL (aliased MR_TL), which together hold the language-independent and language-dependent maintenance requirement header attributes. Additional documented base objects referenced in the view text are:

• AHL_WARRANTY_TEMPLATES_B — supplies the warranty template name for the header.
• FND_LOOKUP_VALUES and FND_LOOKUP_VALUES_VL — supply decoded meanings for many coded columns, including the AHL_YES_NO_TYPE lookups.
• FND_PROFILE — the profile option package, referenced for session or context values.
• MTL_SYSTEM_ITEMS_KFV — the key flexfield view used to resolve the billing item's concatenated segments.
• QA_CHAR_VALUE_LOOKUPS — source for quality inspection type descriptions.

In the ETRM 12.2.2 metadata these appear as synonyms owned by APPS, with FND_LOOKUP_VALUES_VL itself being a view and FND_PROFILE a package. The precedence maintenance requirement (PMR) rows are also joined to expose the preceding header's title and revision.

Key Columns

The view exposes the full identity and descriptive set of the maintenance requirement header. Significant columns include:

• MR_HEADER_ID — primary key of the maintenance requirement header.
• TITLE, VERSION_NUMBER, REVISION, and DESCRIPTION/COMMENTS from MR_TL — user-facing definition text.
• MR_STATUS_CODE, IMPLEMENT_STATUS_CODE, CATEGORY_CODE, SERVICE_TYPE_CODE, PROGRAM_TYPE_CODE, PROGRAM_SUBTYPE_CODE, and TYPE_CODE — each accompanied by a decoded MEANING column.
• COPY_INIT_ACCOMPL_FLAG and COPY_DEFERRALS_FLAG — yes/no indicators decoded against the AHL_YES_NO_TYPE lookup into COPY_INIT_ACCOMPLSMNTS and COPY_DEFERRALS. These are the columns most closely associated with the user's search term.
• REPETITIVE_FLAG, SHOW_REPETITIVE_CODE, WHICHEVER_FIRST_CODE, COPY_ACCOMPLISHMENT_FLAG, and AUTO_SIGNOFF_FLAG — scheduling and signoff behaviour flags.
• EFFECTIVE_FROM / EFFECTIVE_TO — validity window of the header.
• BILLING_ITEM and BILLING_ITEM_ID, BILLING_ORG_ID — the billable item resolved through MTL_SYSTEM_ITEMS_KFV.
• WARRANTY_TEMPLATE_ID and WARRANTY_TEMPLATE_NAME — warranty coverage associated with the header.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the standard descriptive flexfield columns.

Common Use Cases and Queries

Typical usage includes maintenance program listings, status dashboards, integration extracts that must map coded values to meanings, and ad-hoc lookups of yes/no flag behaviour. Because the view already supplies decoded meanings, queries are concise:

• List active headers with their status and category meanings, filtered on EFFECTIVE_TO IS NULL OR EFFECTIVE_TO > SYSDATE.
• Report on copy behaviour flags, for example SELECT MR_HEADER_ID, TITLE, COPY_INIT_ACCOMPLSMNTS, COPY_DEFERRALS FROM APPS.AHL_MR_HEADERS_V.
• Join to MTL_SYSTEM_ITEMS_KFV or billing tables using BILLING_ITEM_ID and BILLING_ORG_ID.
• Filter by SERVICE_TYPE_CODE or MR_STATUS_CODE for workload and scheduling reporting.

Always qualify the view as APPS.AHL_MR_HEADERS_V and restrict rows on indexed base columns where possible, since the view performs numerous correlated lookups that can affect performance on large data sets.