Search Results ahl_fleet_utilization

Overview

AHL_FLEET_UTILIZATION is a transactional table in the AHL (Complex Maintenance Repair and Overhaul) product of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores fleet utilization records that capture forecasted versus actual usage metrics for a fleet over a defined operating period. Each row represents a single utilization snapshot tied to a fleet header, an operating organization, and a date range, making it a core fact source for fleet capacity planning, sortie tracking, and simulation comparisons in aerospace and defense MRO environments.

Based on the foreign-key structure mined from the metadata, this object is best modeled as a standalone entity in a Data Vault classification. It does not act as a pure hub, link, or satellite since it carries both descriptive measures and a foreign key to a simulation plan, but it can be treated as a standalone fact-style table keyed by its own surrogate identifier.

Key Information Stored

The table contains 36 documented columns. The most significant include:

• FLEET_UTILIZATION_ID — surrogate primary key uniquely identifying each utilization record.
• FLEET_HEADER_ID — business-key candidate linking the record to the fleet definition; typically part of a unique index with the period and org.
• NAME — descriptive label for the utilization record.
• OPERATING_ORG_ID — operating organization owning the fleet.
• PERIOD_START_DATE / PERIOD_END_DATE — the date range over which utilization is measured.
• UOM_CODE — unit of measure for the reported usage metrics.
• FLEET_SIZE — number of assets in the fleet for the period.
• FORECASTED_DAILY_USAGE / FORECASTED_DAILY_SORTIES — planned daily utilization and sortie counts.
• ACTUAL_DAILY_USAGE / ACTUAL_DAILY_SORTIES — realized daily utilization and sortie counts.
• SIMULATION_PLAN_ID — foreign key to AHL_SIMULATION_PLANS_B, enabling what-if comparison.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for row-level data security.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the AHL framework.
• ATTRIBUTE1–ATTRIBUTE15 — DFF (descriptive flexfield) columns for customer extensions.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting compares forecast and actual utilization to identify maintenance capacity gaps. A representative query joining to the fleet header and simulation plan follows:

• SELECT fu.NAME, fu.PERIOD_START_DATE, fu.FLEET_SIZE, fu.FORECASTED_DAILY_SORTIES, fu.ACTUAL_DAILY_SORTIES FROM AHL.AHL_FLEET_UTILIZATION fu WHERE fu.OPERATING_ORG_ID = :org AND fu.PERIOD_START_DATE BETWEEN :from_dt AND :to_dt;
• Variance analysis: compute (ACTUAL_DAILY_USAGE - FORECASTED_DAILY_USAGE) grouped by fleet and period.
• Simulation comparisons: join to AHL_SIMULATION_PLANS_B on SIMULATION_PLAN_ID to evaluate alternative fleet plans.
• Security-filtered extracts: restrict rows using SECURITY_GROUP_ID against FND_SECURITY_GROUPS for multi-org deployments.

Related Objects

The metadata documents two foreign-key relationships that anchor this table to the broader AHL data model:

• AHL_SIMULATION_PLANS_B — joined via SIMULATION_PLAN_ID; parent of simulation plan definitions used for utilization forecasting scenarios.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; enforces row-level security across operating units.
• AHL_FLEET_HEADERS — implied parent of FLEET_HEADER_ID; supplies the fleet master definition.
• HR_ALL_ORGANIZATION_UNITS — resolves OPERATING_ORG_ID to organizational context.
• FND_USER / FND_LOOKUPS — resolve audit and UOM references in most reporting extracts.

Together these relationships support utilization reporting across MRO fleet management, simulation planning, and organization-secured analytics.