Search Results ahl_unit_effectivities_b




Overview
Explore in AI Chat

Overview

The AHL_UNIT_EFFECTIVITIES_B table is a core transactional entity within the Oracle E-Business Suite Complex Maintenance, Repair, and Overhaul (CMRO) module. It serves as the central repository for establishing and tracking the applicability of maintenance requirements (MRs) to specific serialized units and their installed components. Each record, known as a unit effectivity, defines a specific instance of a maintenance task that is due or has been performed on a particular unit configuration item. This table is fundamental to the execution of maintenance programs, enabling the scheduling of work orders, tracking of compliance, and management of maintenance history and deferrals within the asset lifecycle.

Key Information Stored

The table's structure captures the critical relationships and statuses for each maintenance requirement instance. The primary identifier is the UNIT_EFFECTIVITY_ID. Key foreign key columns define its core relationships: CSI_ITEM_INSTANCE_ID links to the specific serialized item, MR_HEADER_ID and MR_INTERVAL_ID identify the mandated maintenance task and its interval, and UNIT_CONFIG_HEADER_ID associates it with the unit's structural configuration. The table also manages complex execution states through columns like DEFER_FROM_UE_ID and ORIG_DEFERRAL_UE_ID for deferral chains, PRECEDING_UE_ID for sequence, and CLEAR_STATION_ORG_ID/DEPT_ID for completion location. Status and timing are tracked via LOG_SERIES_NUMBER, while links to service contracts (SERVICE_LINE_ID) and service requests (CS_INCIDENT_ID) integrate maintenance execution with broader service operations.

Common Use Cases and Queries

This table is central to numerous operational and reporting processes. A common use case is generating a list of all pending maintenance tasks for a specific unit. Another critical scenario involves querying the deferral history of a requirement. Analysts frequently query this table to report on maintenance compliance or to analyze the maintenance burden across a fleet. For example, to find all open unit effectivities for a specific aircraft (item instance), a query would join AHL_UNIT_EFFECTIVITIES_B to CSI_ITEM_INSTANCES and filter on the instance and relevant status columns. Performance tuning is essential, as queries often involve multiple joins to related CMRO tables like AHL_MR_HEADERS_B and AHL_UNIT_CONFIG_HEADERS.

Related Objects

AHL_UNIT_EFFECTIVITIES_B is a highly connected hub within the CMRO schema. Its primary relationships, as defined by its foreign keys, include:

  • CSI_ITEM_INSTANCES: The foundational link to the physical serialized asset.
  • AHL_MR_HEADERS_B / AHL_MR_INTERVALS: Define the maintenance task and scheduling rules.
  • AHL_UNIT_CONFIG_HEADERS: Provides the structural context of the unit.
  • AHL_UE_RELATIONSHIPS: Stores hierarchical or dependency links between different unit effectivities.
  • AHL_SCHEDULE_MATERIALS: References unit effectivities to track parts required for scheduled tasks.
  • OKC_K_LINES_B (Service Contracts) and CS_INCIDENTS_ALL_B (Service Requests): Integrate maintenance execution with the Service and Contracts modules.
This network of dependencies underscores the table's critical role in the end-to-end maintenance workflow.