Results for “maintenance_org_id”

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

Overview

The AHL_SIMULATION_FORECAST_V view is an APPS-owned database object within the Oracle E-Business Suite Complex Maintenance, Repair and Overhaul (AHL) module. It exposes simulation forecast data generated by the maintenance forecasting engine, presenting denormalized, human-readable information about simulated maintenance programs, the units (fleet assets) they apply to, and the associated items and master configurations. In EBS 12.1.1 and 12.2.2, the view is marked VALID in the APPS schema.

Its principal role is to support reporting and integration scenarios where users need to inspect forecast output across fleet headers, unit configurations, CSI instances, and maintenance requirement (MR) headers without writing complex joins against the underlying transactional tables. Because it resolves program types, subtypes, and service category codes through FND_LOOKUPS, it delivers descriptive meanings rather than raw codes, making it suitable for concurrent program output, OBIEE/BI Publisher datasets, and custom inquiry forms.

Underlying Base Objects

The view is defined over the following documented base objects: AHL_UE_SIMULATIONS (the driving resource for simulation plan and forecast sequence data), AHL_UNIT_CONFIG_HEADERS (outer-joined unit configuration), CSI_ITEM_INSTANCES (instances such as serialized assets), MTL_SYSTEM_ITEMS_KFV (concatenated-segment item names), AHL_MC_HEADERS_B (master configuration headers), AHL_FLEET_HEADERS_B (fleet definitions), AHL_MR_HEADERS_B (maintenance requirement headers), and AHL_UE_ORGS_DEPTS_V (maintenance organization information).

Supporting objects include FND_LOOKUPS for lookup meanings, HR_ALL_ORGANIZATION_UNITS and MTL_PARAMETERS (restricted with EAM_ENABLED_FLAG = 'Y') for the operating organization name, and the packages AHL_UTIL_UC_PKG, FND_GLOBAL, HR_GENERAL, and HR_SECURITY. The join to AHL_UNIT_CONFIG_HEADERS is outer (+) because a unit may not yet exist during data copy from the effectivities table; unit status is filtered to exclude DRAFT and EXPIRED, and only checked when a unit configuration header exists on the simulation row.

Key Columns

• SIMULATION_PLAN_ID / SIMULATION_UE_ID / FORECAST_SEQUENCE — identify the simulation and ordering of forecast occurrences.
• DUE_DATE — the forecast maintenance due date, central to planning output.
• FLEET_HEADER_ID / FLEET_NAME — the fleet to which the forecast applies.
• UNIT_CONFIG_HEADER_ID / UNIT — the unit configuration and its name.
• CSI_INSTANCE_ID / SERIAL_NUMBER / ITEM_NAME — the underlying CSI instance and its concatenated item segment description.
• MASTER_CONFIGURATION / MC_HEADER_ID — master configuration details for the unit.
• OPERATING_ORG_ID / OPERATING_ORG — the EAM-enabled operating organization name.
• MR_MAINTENANCE_ORG_ID / MAINTENANCE_ORG — the organization responsible for maintenance execution.
• MR_TITLE / MR_HEADER_ID / REPETITIVE_MR_FLAG — the maintenance requirement heading and its repetitive indicator.
• PROGRAM_TYPE_CODE / PROGRAM_TYPE / PROGRAM_SUBTYPE_CODE / PROGRAM_SUBTYPE — program classification derived from lookups.
• DOWN_TIME — expected downtime for the maintenance activity.
• SERVICE_CATEGORY_CODE — aliased from MR.SERVICE_CATEGORY_RANK; this is the column users typically search for when filtering forecasts by service category ranking.

Common Use Cases and Queries

Typical usage includes auditing forecast coverage by fleet, verifying service category assignments, and feeding downstream planning dashboards. A representative query:

• SELECT simulation_plan_id, due_date, fleet_name, unit, item_name, program_type, program_subtype, service_category_code, down_time FROM ahl_simulation_forecast_v WHERE fleet_header_id = :p_fleet_id ORDER BY due_date;
• Filtering by service_category_code to group forecasts by rank — note that only the numeric rank is exposed, not a lookup meaning, so a join to the appropriate lookup or category table may be needed.
• Restricting by operating_org_id when ORG_ID security relies on HR security profiles resolved through HR_SECURITY / FND_GLOBAL.

Because the view depends on CSI, MTL, and AHL setup, query performance benefits from filtering on indexed keys such as SIMULATION_PLAN_ID, FLEET_HEADER_ID, or MR_HEADER_ID.