Results for “ahl_ue_simulations”

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

Overview

AHL_UE_SIMULATIONS is a transaction and planning table within the Oracle E-Business Suite product AHL — Complex Maintenance Repair and Overhaul. It stores the results of maintenance program simulation runs, in which the maintenance requirements defined for a unit configuration are exploded against a given maintenance requirement header to produce a forecast of unit events (UEs) with calculated due dates, due counters, and tolerance windows. In the ETRM 12.2.2 documentation the object is owned by the AHL schema, holds VALID status, and exposes 33 columns.

The metadata classifies this object, heuristically mined from its foreign key structure, as standalone under a Data Vault model. That is, it is not a pure hub, link, or satellite, but behaves as a self-contained effectivity/planning record that references several independent parent entities. In practice it can be modeled as a satellite attached to simulation plan and maintenance requirement hubs, with the composite of simulation plan and unit event references acting as the natural business key.

Key Information Stored

The primary surrogate key is SIMULATION_UE_ID, a single-column identifier for each simulated unit event. Business-key candidates are formed from the combination of SIMULATION_PLAN_ID, CSI_ITEM_INSTANCE_ID, MR_HEADER_ID, and DUE_DATE (or FORECAST_SEQUENCE), which uniquely identify a simulated event within a plan run.

• SIMULATION_PLAN_ID — FK to AHL_SIMULATION_PLANS_B; identifies the simulation plan that produced the row.
• CSI_ITEM_INSTANCE_ID — the installed unit instance being forecast.
• MR_HEADER_ID, MR_EFFECTIVITY_ID, MR_INTERVAL_ID — the maintenance requirement, its effectivity, and its interval that drive the forecast.
• UNIT_CONFIG_HEADER_ID, FLEET_HEADER_ID — unit configuration and fleet context for the simulated event.
• DUE_DATE, EARLIEST_DUE_DATE, LATEST_DUE_DATE — the calculated due date and its tolerance window.
• DUE_COUNTER_VALUE, COUNTER_ID — the counter reading at which the requirement becomes due.
• STATUS_CODE, MESSAGE_CODE, TOLERANCE_FLAG, DATE_RUN — simulation status, diagnostics, tolerance outcome, and run timestamp.
• REPETITIVE_MR_FLAG, MANUALLY_PLANNED_FLAG, FORECAST_SEQUENCE — indicators of repetitive requirements and manual planning, with ordering of forecast occurrences.
• Standard EBS audit columns (OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, CREATED_BY, etc.) plus SECURITY_GROUP_ID support concurrency and access control.

Common Use Cases and Queries

Typical usage includes reviewing forecasted due events for a unit, comparing tolerance outcomes across plans, and reporting on the volume of events generated per simulation run.

Sample query listing events for a plan:

• SELECT s.SIMULATION_UE_ID, s.CSI_ITEM_INSTANCE_ID, s.MR_HEADER_ID, s.DUE_DATE, s.DUE_COUNTER_VALUE, s.STATUS_CODE FROM AHL.AHL_UE_SIMULATIONS s WHERE s.SIMULATION_PLAN_ID = :plan_id ORDER BY s.FORECAST_SEQUENCE;

A second pattern filters events falling outside tolerance or flagged for manual review:

• SELECT s.SIMULATION_UE_ID, s.DUE_DATE, s.MESSAGE_CODE FROM AHL.AHL_UE_SIMULATIONS s WHERE s.TOLERANCE_FLAG = 'Y' AND s.MANUALLY_PLANNED_FLAG = 'Y';

Related Objects

The foreign keys documented in the ETRM metadata identify the principal parent objects that reference this table via their join columns:

• AHL_SIMULATION_PLANS_B — joined on SIMULATION_PLAN_ID; the driving plan.
• AHL_MR_HEADERS_B — joined on MR_HEADER_ID; the maintenance requirement header.
• AHL_MR_EFFECTIVITIES — joined on MR_EFFECTIVITY_ID; effectivity context.
• AHL_MR_INTERVALS — joined on MR_INTERVAL_ID; interval definition.
• AHL_UNIT_CONFIG_HEADERS — joined on UNIT_CONFIG_HEADER_ID; unit configuration.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; access control.

These relationships make AHL_UE_SIMULATIONS the central fact record for maintenance forecasting within AHL, linking planning, requirement, and unit configuration data.