Results for “ahl_mr_headers_vl”

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

Overview

AHL_MR_HEADERS_VL is a translated (VL) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AHL – Complex Maintenance Repair and Overhaul product family. It presents maintenance requirement (MR) header information for complex assets, combining non-translated operational columns held on the base table with language-specific descriptive columns held on the translation table. The view exists to support the multilingual architecture of EBS release 12.1.1 and 12.2.2, in which translatable text is stored separately from language-independent data. Because it exposes a single, denormalized row per maintenance requirement header for the session language, the view is the standard access point for reports, concurrent programs, forms, and integration interfaces that must display MR header information in the user's own language.

AHL (Complex Maintenance Repair and Overhaul) is used by organizations performing heavy maintenance on complex assets such as aircraft, ships, and industrial equipment. The MR header is the top-level record defining a maintenance requirement, including its title, version, category, service type, and status. AHL_MR_HEADERS_VL provides the reporting layer through which this definition is queried without requiring application code to join the base and translation tables manually.

Underlying Base Objects

Per the documented metadata, the view is defined over two base objects: AHL_MR_HEADERS_B, which holds language-independent (base) columns such as identifiers, statuses, dates, flags, and descriptive flexfield attributes, and AHL_MR_HEADERS_TL, which holds the translated columns. Both are referenced in the ETRM 12.2.2 metadata as synonyms, resolving to the underlying AHL tables in the APPS schema.

The defining query joins the two tables on MR_HEADER_ID and filters the translation table with T.LANGUAGE = USERENV('LANG'), so that only the row matching the current session language is returned. This is the canonical _VL pattern in EBS: a one-to-one outer-equivalent join between a _B table and its _TL counterpart, with the language predicate supplied by USERENV('LANG'). The view is therefore a thin, read-oriented projection rather than a table with independent storage; all inserts and updates must target the base tables directly.

Key Columns

• MR_HEADER_ID – Primary identifier of the maintenance requirement header; the join key between the base and translation tables and the foreign key referenced by child MR entities.
• TITLE, VERSION_NUMBER, REVISION – Identification and versioning attributes of the maintenance requirement.
• DESCRIPTION, COMMENTS – Translatable text sourced from AHL_MR_HEADERS_TL; these are the columns that make the VL view language-sensitive.
• MR_STATUS_CODE, IMPLEMENT_STATUS_CODE – Status of the maintenance requirement and of its implementation.
• CATEGORY_CODE, SERVICE_TYPE_CODE, TYPE_CODE, PROGRAM_TYPE_CODE, PROGRAM_SUBTYPE_CODE – Classification codes driving processing and reporting.
• EFFECTIVE_FROM, EFFECTIVE_TO – Effective date range for the requirement.
• REPETITIVE_FLAG, SHOW_REPETITIVE_CODE, COPY_ACCOMPLISHMENT_FLAG, WHICHEVER_FIRST_CODE – Scheduling and execution behavior flags.
• PRECEDING_MR_HEADER_ID – Self-referencing link to a predecessor maintenance requirement.
• BILLING_ITEM_ID, BILLING_ORG_ID, SPACE_CATEGORY_CODE, QA_INSPECTION_TYPE, SERVICE_REQUEST_TEMPLATE_ID, DOWN_TIME, UOM_CODE – Operational attributes covering billing, space, quality, service requests, downtime, and units of measure.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – Descriptive flexfield columns for customer-defined extensions.
• Standard WHO columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER for auditing and optimistic locking.

Common Use Cases and Queries

The view is principally used for reporting and integration, where the caller wants MR header data in the session language without managing the translation join. Typical scenarios include maintenance requirement listings, status dashboards, interfaces feeding external planning systems, and validation queries in concurrent programs.

A basic listing retrieves active headers for the current language:

• SELECT mr_header_id, title, version_number, mr_status_code, effective_from FROM ahl_mr_headers_vl WHERE mr_status_code = 'ACTIVE';

Because the language filter is embedded in the view, callers cannot override the language at query time; reports requiring a specific language must join AHL_MR_HEADERS_TL directly with an explicit LANGUAGE predicate. When joining to child tables such as MR operations or resource requirements, the view is used on the header side with MR_HEADER_ID as the join key. For flexfield reporting, ATTRIBUTE_CATEGORY and the attribute columns may be selected alongside the descriptive flexfield definition tables. DBA reviews of the view in 12.1.1 and 12.2.2 may also inspect its text via DBA_VIEWS to confirm the base-to-translation join and language predicate remain intact after patching.