Search Results ahl_unit_schedules




Overview
Explore in AI Chat

Overview

The AHL_UNIT_SCHEDULES table is a core data object within the Oracle E-Business Suite module for Complex Maintenance, Repair, and Overhaul (CMRO), denoted by the AHL product code. It serves as the primary transactional repository for recording scheduled usage events of configured assets, known as units. As per the official ETRM description, each row represents an event describing the usage of a configured unit for a specific time period. A quintessential example is the scheduling of an airplane flight for a specific aircraft unit. This table is fundamental to the CMRO lifecycle, as it captures planned operational activity, which directly influences maintenance planning, resource allocation, and service history tracking. Its status is documented as VALID, confirming its active role in both EBS 12.1.1 and 12.2.2 implementations.

Key Information Stored

The table's primary purpose is to define a unit schedule event. Its structure is anchored by the UNIT_SCHEDULE_ID column, which serves as the unique primary key identifier for each schedule record. A critical foreign key is the UNIT_CONFIG_HEADER_ID, which links the schedule to a specific configured asset defined in the AHL_UNIT_CONFIG_HEADERS table. This relationship ensures every usage event is associated with a valid, configurable unit. While the full column list is not exhaustively detailed in the provided metadata, typical data stored would include schedule start and end dates/times, the schedule type or purpose (e.g., flight, test run), operational parameters, status, and creation/modification audit columns. The existence of a foreign key from AHL_VISITS_B indicates the table also stores data that subsequently triggers or is associated with maintenance visits.

Common Use Cases and Queries

This table is central to operational planning and maintenance integration. Common use cases include generating flight logs or operational timelines for configured units, forecasting maintenance windows based on accumulated usage hours or cycles, and reconciling planned versus actual unit deployment. For reporting, a fundamental query involves joining to the unit configuration header to retrieve asset details. A sample SQL pattern to list upcoming schedules for a specific unit would be:

SELECT aus.unit_schedule_id, aus.scheduled_start_date, aus.scheduled_end_date, auch.unit_config_header_id, auch.unit_name
FROM ahl_unit_schedules aus,
ahl_unit_config_headers auch
WHERE aus.unit_config_header_id = auch.unit_config_header_id
AND auch.unit_config_header_id = :p_unit_id
AND aus.scheduled_start_date > SYSDATE
ORDER BY aus.scheduled_start_date;

Another critical use case is identifying schedules that have generated maintenance visits, leveraging the relationship with AHL_VISITS_B.

Related Objects

The AHL_UNIT_SCHEDULES table is integral within the CMRO schema, with documented relationships to other key entities. The primary foreign key relationship is with the AHL_UNIT_CONFIG_HEADERS table, via the UNIT_CONFIG_HEADER_ID column. This ensures every schedule is for a valid, configured asset. Furthermore, the table has a dependent relationship with the AHL_VISITS_B table, which stores visit and work order information. The foreign key AHL_VISITS_B.UNIT_SCHEDULE_ID references this table, indicating that a scheduled unit usage event can be the direct cause or associated context for one or more maintenance visits. These relationships form a critical data flow from asset configuration (AHL_UNIT_CONFIG_HEADERS) to operational scheduling (AHL_UNIT_SCHEDULES) and finally to maintenance execution (AHL_VISITS_B).