Results for “whichever_first_code”

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

Overview

The AHL_APPLICABLE_MRS table is a core data object within the Oracle E-Business Suite Complex Maintenance Repair and Overhaul (AHL) module. It stores the applicable maintenance requirement (MR) records that govern which maintenance tasks, effectivities, and program-level requirements apply to a given maintained item or configuration. In EBS 12.1.1 and 12.2.2 environments, this table acts as the operational bridge between the definition of maintenance requirements and their application to specific instantiations of assets, service lines, and contracts. It belongs to the AHL schema and is documented as VALID in the ETRM repository, containing 17 columns in the 12.2.2 physical schema.

Using the heuristic Data Vault classification mined from its foreign key structure, this object is modeled as a standalone entity — that is, it does not behave as a pure hub, link, or satellite but rather as an independent associational table. In practice, it can be interpreted as a link-style entity that associates multiple parent records (maintenance requirement headers, effectivities, and item instances), while carrying its own descriptive and qualifying attributes. This makes it a junction and configuration table simultaneously.

Key Information Stored

The table’s surrogate key relationships are established through MR_HEADER_ID, which references AHL_MR_HEADERS_B, and MR_EFFECTIVITY_ID, which references AHL_MR_EFFECTIVITIES. The most significant columns include:

• MR_HEADER_ID – the maintenance requirement header this applicability row belongs to.
• MR_EFFECTIVITY_ID – the specific effectivity definition governing when the MR applies.
• CSI_ITEM_INSTANCE_ID – the maintained item instance to which the MR is applied.
• PRECEDING_MR_HEADER_ID – a predecessor maintenance requirement that constrains sequencing.
• PROGRAM_MR_HEADER_ID – the parent program-level MR, if the record participates in a program.
• WHICHEVER_FIRST_CODE – control flag indicating which of multiple triggering conditions applies first.
• REPETITIVE_FLAG / SHOW_REPETITIVE_CODE – flags governing repetitive maintenance behavior and its visibility.
• COPY_ACCOMPLISHMENT_CODE – controls whether accomplishment data is copied forward.
• IMPLEMENT_STATUS_CODE – the implementation/lifecycle status of the applicability record.
• DESCENDENT_COUNT – count of descendant records in the applicability hierarchy.
• SERVICE_LINE_ID – the service line context for the MR.
• COVERAGE_IMP_LEVEL – coverage implementation level applied.
• CONTRACT_START_DATE / CONTRACT_END_DATE – the contract validity window for the applicable MR.
• PM_SCHEDULE_EXISTS – indicates whether a preventive maintenance schedule exists.
• PROGRAM_END_DATE – the terminating date for the associated program.

Primary-key identity is generally carried by the internal ID column, while the combination of MR_HEADER_ID and MR_EFFECTIVITY_ID serves as a natural business-key candidate linking applicability to demand.

Common Use Cases and Queries

Typical usage centers on reporting which maintenance requirements apply to which assets, and under what effectivity and contract windows. For example, to list all applicable MRs for an item instance:

SELECT m.MR_HEADER_ID, m.MR_EFFECTIVITY_ID, m.CSI_ITEM_INSTANCE_ID, m.IMPLEMENT_STATUS_CODE
FROM   AHL.AHL_APPLICABLE_MRS m
WHERE  m.CSI_ITEM_INSTANCE_ID = :item_instance_id;

Other scenarios include validating effectivity dates, identifying program-nested MRs via PROGRAM_MR_HEADER_ID, and reporting on repetitive maintenance through REPETITIVE_FLAG. Contract compliance reports filter on CONTRACT_START_DATE and CONTRACT_END_DATE.

Related Objects

• AHL_MR_HEADERS_B – joined via MR_HEADER_ID.
• AHL_MR_EFFECTIVITIES – joined via MR_EFFECTIVITY_ID.
• Item instance and service line entities referenced through CSI_ITEM_INSTANCE_ID and SERVICE_LINE_ID.
• Program-level MR records referenced via PROGRAM_MR_HEADER_ID.