Results for “fleet_header_id”

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

Overview

The AHL_FLEET_DOWNTIMES table resides in the AHL schema, which supports the Complex Maintenance Repair and Overhaul (CMRO) module of Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, AHL provides the maintenance and overhaul framework used by asset-intensive industries such as aerospace, defense, and heavy equipment. Within this framework, fleet downtime records define the periods during which a fleet—or a specific fleet configuration—is expected to be unavailable for operational use, together with a tolerance expressed as a maximum permitted percentage. These records are consumed by scheduling and capacity-planning functions so that maintenance windows, resource allocation, and mission availability calculations reflect realistic non-operational intervals.

The metadata classifies this table heuristically as standalone under the Data Vault model. Because the only documented foreign key points to the FND_SECURITY_GROUPS lookup rather than to another business entity table, the standalone classification is appropriate. Modelers may nonetheless treat AHL_FLEET_DOWNTIMES as a satellite attached to a fleet hub, since FLEET_HEADER_ID implies an association with a fleet-defining parent object even where that relationship is not exposed through a documented constraint.

Key Information Stored

The table contains twelve documented columns. The most significant are:

• FLEET_DOWNTIME_ID — the surrogate primary key uniquely identifying each downtime definition.
• FLEET_HEADER_ID — the business-key candidate linking the downtime record to its owning fleet header.
• PERIOD_START and PERIOD_END — the effective date range for which the downtime definition applies.
• MAX_PERCENTAGE — the maximum allowable downtime expressed as a percentage, used in availability and readiness calculations.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data segregation.
• OBJECT_VERSION_NUMBER — used for optimistic locking during concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO columns providing full audit lineage.

The pairing of FLEET_HEADER_ID with PERIOD_START and PERIOD_END constitutes the natural business key for a given downtime window.

Common Use Cases and Queries

Typical reporting scenarios include identifying active downtime windows for a fleet, comparing committed downtime against the MAX_PERCENTAGE threshold, and auditing records by user or creation date. A representative query retrieves current downtime definitions:

SELECT fleet_downtime_id, fleet_header_id, period_start, period_end, max_percentage
FROM ahl.ahl_fleet_downtimes
WHERE SYSDATE BETWEEN period_start AND period_end
AND security_group_id = :p_security_group_id;

A second pattern aggregates permissible downtime by fleet header for capacity dashboards, while a third joins audit columns to trace recent maintenance-window changes. All queries should filter on SECURITY_GROUP_ID to respect the module's access controls.

Related Objects

The following objects are most relevant to AHL_FLEET_DOWNTIMES:

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to resolve the owning security group.
• AHL_FLEET_HEADERS — the implied parent of FLEET_HEADER_ID, defining the fleet to which downtime applies.
• AHL_FLEET_UNITS — child fleet components affected by the parent header's downtime windows.
• AHL_MAINTENANCE_VISITS and AHL_WORKORDERS — scheduling entities that consume downtime availability.
• AHL_MTL_SYSTEM_ITEMS_V — the item view used to resolve fleet assets for reporting.
• AHL_FLEET_DOWNTIMES public API / concurrent programs — the maintenance-availability batch processes that read this table.

These relationships support end-to-end fleet availability analysis within the CMRO module.