Search Results ahl_fleet_headers

Overview

APPS.AHL_SIMULATION_FORECAST_V is an Oracle E-Business Suite internal database view owned by the APPS schema and registered under the FND Design Data application AHL (Complex Maintenance, Repair and Overhaul, also known as Enterprise Asset Management for asset-intensive industries). The view exposes simulation forecast data generated by the Maintenance Management simulation engine. It consolidates effectivity records produced during a simulation run together with descriptive attributes for the unit, item instance, master configuration, operating organisation, maintenance organisation, fleet, and maintenance requirement.

The view carries an explicit Oracle Internal Use Only warning. Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Consequently, the view should be treated as a supporting interface for seeded functionality rather than as a documented public API. Reports, extensions, or integrations that reference it do so at their own risk and must anticipate behavioural changes across releases, including EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The documented base objects referenced by the view include AHL_FLEET_HEADERS_B, AHL_MC_HEADERS_B, AHL_MR_HEADERS_B, AHL_UE_SIMULATIONS, AHL_UNIT_CONFIG_HEADERS, CSI_ITEM_INSTANCES, MTL_SYSTEM_ITEMS_KFV, MTL_PARAMETERS, HR_ALL_ORGANIZATION_UNITS, FND_LOOKUPS, and the AHL_UE_ORGS_DEPTS_V view. Supporting packages and utilities include AHL_UTIL_UC_PKG, FND_GLOBAL, HR_GENERAL, and HR_SECURITY. The HR_SECURITY and HR_GENERAL references indicate that organisation-level row filtering and organisation name resolution are applied when the view is queried, so results depend on the session's operating unit and security profile.

The fleet relationship is held through AHL_FLEET_HEADERS_B, which supplies the FLEET_HEADER_ID and FLEET_NAME columns. Because fleet assignment is resolved at due date, the FLEET_NAME column reflects the fleet as it stood on the calculated due date rather than at query time. Maintenance requirement attributes come from AHL_MR_HEADERS_B, while unit configuration and instance details originate from AHL_UNIT_CONFIG_HEADERS and CSI_ITEM_INSTANCES respectively.

Key Columns

The primary identifiers are SIMULATION_PLAN_ID, which refers to AHL_SIMULATION_PLANS_B, and SIMULATION_UE_ID, which refers to AHL_UE_SIMULATIONS. DUE_DATE holds the calculated due date for the effectivity, and FORECAST_SEQUENCE orders multiple instances of the same maintenance requirement for the same item instance in ascending due-date order.

Fleet-related columns are FLEET_HEADER_ID (foreign key to AHL_FLEET_HEADERS) and FLEET_NAME, presented as VARCHAR2(150). Asset identification columns include UNIT_CONFIG_HEADER_ID, UNIT, CSI_INSTANCE_ID, SERIAL_NUMBER, ITEM_NAME, MASTER_CONFIGURATION, and MC_HEADER_ID. Organisational context is provided by OPERATING_ORG_ID, OPERATING_ORG, MAINTENANCE_ORG_ID, and MAINTENANCE_ORG.

Maintenance requirement data is exposed through MR_TITLE, MR_HEADER_ID, PROGRAM_TYPE_CODE, PROGRAM_TYPE, PROGRAM_SUBTYPE_CODE, PROGRAM_SUBTYPE, and REPETITIVE_MR_FLAG. The REPETITIVE_MR_FLAG is set to 'Y' when the maintenance requirement originates from repetitivity, otherwise 'N'.

Common Use Cases and Queries

A frequent requirement is to forecast maintenance demand by fleet and due date. The query below joins the view to AHL_FLEET_HEADERS_B implicitly through the denormalised FLEET_NAME column.

• Forecast listing: SELECT fleet_name, unit, serial_number, mr_title, due_date, forecast_sequence FROM apps.ahl_simulation_forecast_v WHERE due_date BETWEEN :start_date AND :end_date ORDER BY fleet_name, due_date;
• Repetitive versus non-repetitive load: SELECT repetitive_mr_flag, COUNT(*) FROM apps.ahl_simulation_forecast_v GROUP BY repetitive_mr_flag;
• Fleet-level simulation summary: SELECT fleet_header_id, fleet_name, COUNT(*) forecast_count, MIN(due_date) first_due, MAX(due_date) last_due FROM apps.ahl_simulation_forecast_v GROUP BY fleet_header_id, fleet_name;

Because the view is flagged as internal use only, any custom SQL should be validated in a non-production environment before deployment, and expected to require review during upgrades from 12.1.1 to 12.2.2.