Search Results ahl_mr_effectivities_uk1

Overview

The AHL_MR_EFFECTIVITIES table is a core data object within the Complex Maintenance, Repair, and Overhaul (CMRO) module of Oracle E-Business Suite (EBS). It serves as the master repository for defining the effectivity of maintenance requirements. In CMRO, a maintenance requirement (MR) is a defined task or procedure. An effectivity specifies the precise conditions under which that MR applies, such as which specific units, item models, or serial numbers the maintenance task is valid for. This table is fundamental for ensuring maintenance plans are accurately targeted, preventing the misapplication of tasks to incorrect assets, and enabling precise compliance tracking.

Key Information Stored

The table's primary key is MR_EFFECTIVITY_ID, a unique system-generated identifier. A unique key constraint (AHL_MR_EFFECTIVITIES_UK1) also exists on the combination of NAME and MR_HEADER_ID, enforcing unique effectivity names within a given maintenance requirement header. Critical foreign key columns define the effectivity's scope and relationships. The MR_HEADER_ID links to AHL_MR_HEADERS_B, the parent maintenance requirement. The INVENTORY_ITEM_ID and INVENTORY_ORG_ID columns link to MTL_SYSTEM_ITEMS_B to define effectivity based on an inventory item. The RELATIONSHIP_ID links to AHL_RELATIONSHIPS_B, allowing effectivity to be defined based on configurator relationships or product structures. Other columns typically store effectivity dates, quantity ranges, and status information, though specific column details are not enumerated in the provided metadata.

Common Use Cases and Queries

Primary use cases involve retrieving all effectivities for a specific maintenance requirement or identifying which maintenance requirements apply to a given asset. For reporting, it is central to generating compliance matrices and maintenance schedules filtered by asset type. Common SQL patterns include joining to the item master and MR header tables. For example, to list effectivities for a specific MR:

• SELECT ame.name, ame.mr_effectivity_id, msib.segment1 item_code FROM ahl_mr_effectivities ame, ahl_mr_headers_b amh, mtl_system_items_b msib WHERE ame.mr_header_id = amh.mr_header_id AND ame.inventory_item_id = msib.inventory_item_id AND ame.inventory_org_id = msib.organization_id AND amh.mr_header_id = <header_id>;

Another key query identifies MRs applicable to a specific unit or serial number by joining through AHL_UNIT_EFFECTIVITIES_B.

Related Objects

AHL_MR_EFFECTIVITIES has extensive relationships within the AHL schema, acting as a hub for detailed effectivity data. It is a parent table to several key entities: AHL_MR_EFFECTIVITY_DTLS stores more granular effectivity details like serial number ranges. AHL_MR_INTERVALS defines the timing or meter-based intervals for the MR within this effectivity scope. AHL_UNIT_EFFECTIVITIES_B links specific unit instances to the effectivity. As shown by its foreign keys, it is a child of AHL_MR_HEADERS_B (the MR definition), AHL_RELATIONSHIPS_B (for configuration rules), and MTL_SYSTEM_ITEMS_B (the item master). Any technical customization or data fix related to MR applicability will likely involve this table and its dependencies.