Search Results ahl_mr_headers_b

Overview

The AHL_MR_HEADERS_B table is the core repository for maintenance requirement (MR) definitions within the Complex Maintenance Repair and Overhaul (CMRO) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the master header table, storing the fundamental metadata that defines a maintenance procedure, inspection, or task. Every maintenance requirement created in the system is anchored to a record in this table, establishing it as a central object for managing maintenance programs, work orders, and service visits. The data in this table drives the execution of maintenance operations across assets and units.

Key Information Stored

The table's primary key is the system-generated identifier MR_HEADER_ID. A unique key constraint (AHL_MR_HEADERS_B_UK1) enforces business logic by ensuring the combination of TITLE, VERSION_NUMBER, and APPLICATION_USG_CODE is unique, preventing duplicate requirement definitions. Critical columns include TITLE for the MR name, VERSION_NUMBER for tracking revisions, and APPLICATION_USG_CODE which defines the MR's usage context (e.g., for a unit, serial, or lot). The PRECEDING_MR_HEADER_ID column supports versioning by linking a new MR version to its predecessor, creating a self-referential foreign key relationship within the same table.

Common Use Cases and Queries

This table is central to queries for maintenance program analysis, impact assessment of MR changes, and generating task lists. A common reporting requirement is to list all active maintenance requirements for a specific asset type or usage code. A typical query pattern involves joining to the translated table (AHL_MR_HEADERS_TL) for descriptions and to effectivity tables for applicability rules.

• Sample Query: Retrieving MR headers with their latest version for a specific application usage.

SELECT mrh.TITLE, mrh.VERSION_NUMBER, mrh.MR_HEADER_ID
FROM AHL_MR_HEADERS_B mrh
WHERE mrh.APPLICATION_USG_CODE = 'SERIAL'
AND mrh.VERSION_NUMBER = (
    SELECT MAX(version_number)
    FROM AHL_MR_HEADERS_B
    WHERE TITLE = mrh.TITLE
    AND APPLICATION_USG_CODE = mrh.APPLICATION_USG_CODE
)
ORDER BY mrh.TITLE;

Related Objects

AHL_MR_HEADERS_B has extensive relationships, underscoring its foundational role. Key dependent tables include AHL_MR_ACTIONS_B (detailed task steps), AHL_MR_EFFECTIVITIES (applicability rules), AHL_MR_ROUTES (routing instructions), and AHL_MR_HEADERS_TL for translated titles. It is referenced by execution entities like AHL_VISIT_TASKS_B (service tasks) and AHL_UNIT_EFFECTIVITIES_B (which tracks MR compliance for specific units). The AHL_MR_RELATIONSHIPS table uses MR_HEADER_ID and RELATED_MR_HEADER_ID to define hierarchical or associative links between different maintenance requirements.