Results for “ahl_mr_headers_b”

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

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, AHL.AHL_MR_HEADERS_B is the base (untranslated) header table for Maintenance Requirements within the AHL – Complex Maintenance Repair and Overhaul product. A Maintenance Requirement (MR) defines a reusable, versioned maintenance program or task template that can be applied to assets, units, or visits in complex MRO environments such as aerospace, defense, and heavy equipment maintenance. Each row represents a single MR header, holding classification, versioning, effectivity, program type, and status information that downstream detail tables consume.

From a Data Vault modeling perspective, this table is best classified as a hub. It anchors a stable business key (the MR identity) that is referenced by numerous satellites and link tables such as AHL_MR_HEADERS_TL (translations), AHL_MR_ACTIONS_B, AHL_MR_ROUTES, and AHL_MR_EFFECTIVITIES. The table carries 55 documented columns and is owned by the AHL schema.

Key Information Stored

• MR_HEADER_ID — The surrogate primary key, enforced by the AHL_MR_HEADERS_B_PK constraint and additionally protected by unique index AHL_MR_HEADERS_B_U1. This is the value propagated to nearly every dependent table.
• TITLE, VERSION_NUMBER, APPLICATION_USG_CODE — The business-key candidate set, enforced by unique index AHL_MR_HEADERS_B_UK1 (also documented as AHL_MR_HEADERS_B_U2). Together they guarantee that an MR title is unique per version and usage context.
• MR_STATUS_CODE and IMPLEMENT_STATUS_CODE — Track the lifecycle of the requirement, such as draft vs. released, and its implementation state.
• PRECEDING_MR_HEADER_ID — A self-referencing foreign key that links a versioned MR to its predecessor, supporting version lineage.
• CATEGORY_CODE, TYPE_CODE, SERVICE_TYPE_CODE — Classify the nature of the requirement for filtering and reporting.
• EFFECTIVE_FROM and EFFECTIVE_TO — Define the date range during which the MR is valid.
• PROGRAM_TYPE_CODE and PROGRAM_SUBTYPE_CODE — Identify the maintenance program category, which is central to program-driven MRs referenced by AHL_UNIT_EFFECTIVITIES_B.PROGRAM_MR_HEADER_ID.
• REPETITIVE_FLAG, SHOW_REPETITIVE_CODE, AUTO_SIGNOFF_FLAG — Behavioural flags controlling repetition and sign-off handling.
• SECURITY_GROUP_ID — The foreign key to FND_SECURITY_GROUPS, enforcing multi-org data security.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — The standard EBS DFF (Descriptive Flexfield) columns for client-specific extension data.
• OBJECT_VERSION_NUMBER and the WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — Support optimistic locking and audit tracking.

Common Use Cases and Queries

The most frequent scenario is retrieving active MRs and joining to the translated title table for display:

SELECT h.mr_header_id, t.title, h.version_number, h.mr_status_code
FROM   ahl_mr_headers_b h, ahl_mr_headers_tl t
WHERE  h.mr_header_id = t.mr_header_id
AND    t.language = USERENV('LANG');

Reporting on the version chain uses the self-referencing key:

SELECT prior.mr_header_id, prior.title, prior.version_number
FROM   ahl_mr_headers_b curr, ahl_mr_headers_b prior
WHERE  curr.preceding_mr_header_id = prior.mr_header_id
AND    curr.mr_header_id = :p_mr_id;

Other practical uses include effectivity validation against EFFECTIVE_FROM and EFFECTIVE_TO, extracting DFF attribute values for custom reports, and querying MRs by PROGRAM_TYPE_CODE for program-level maintenance scheduling. The table is also a common starting point for tracing which assets or visits a given requirement affects through AHL_UNIT_EFFECTIVITIES_B and AHL_VISIT_TASKS_B.

Related Objects

• AHL_MR_HEADERS_TL — Translated (language) titles joined on MR_HEADER_ID.
• AHL_MR_ACTIONS_B — Actions defined for the MR, joined on MR_HEADER_ID.
• AHL_MR_ROUTES — Routing steps belonging to the MR, joined on MR_HEADER_ID.
• AHL_MR_EFFECTIVITIES — Effectivity definitions for the MR, joined on MR_HEADER_ID.
• AHL_MR_RELATIONSHIPS — Links MRs to related MRs via MR_HEADER_ID and RELATED_MR_HEADER_ID.
• AHL_UNIT_EFFECTIVITIES_B — Associates MRs to units via MR_HEADER_ID and PROGRAM_MR_HEADER_ID.
• AHL_VISIT_TASKS_B — Generated visit tasks referencing the MR via MR_ID.
• AHL_SNAPSHOTS — Captured snapshots referencing the MR via MR_ID.
• FND_SECURITY_GROUPS — Security group definition for the SECURITY_GROUP_ID foreign key.
• Self-reference — PRECEDING_MR_HEADER_ID points back into AHL_MR_HEADERS_B for version lineage.