Results for “mr_maintenance_dept_id”

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

Overview

AHL_UE_ORGS_DEPTS_V is an APPS-owned reporting view within the AHL (Complex Maintenance Repair and Overhaul) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name reflects its purpose: it exposes Unit Effectivity (UE) records joined to the organizations (ORGS) and departments (DEPTS) that own or maintain the associated fleet and maintenance requirement. The view is commonly referenced as ahl_ue_orgs_depts_v in reporting and integration queries, and it holds a VALID status in the APPS schema.

Unlike a simple join, this view embeds substantial business logic. It resolves — through nested CASE expressions — the effective maintenance organization and maintenance department for a unit effectivity, selecting between the organization defined on the maintenance requirement versus the organization defined on the fleet header. It also exposes a SIM_UE_FLAG discriminator, which allows simulation records created via AHL_UE_SIMULATIONS to be handled separately from real unit effectivity records. This makes the view a convenient single source for reporting on the organizational context of unit effectivity and repair work.

Underlying Base Objects

The documented base objects underlying AHL_UE_ORGS_DEPTS_V are:

• AHL_UNIT_EFFECTIVITIES_B — the core unit effectivity records (aliased AUE), providing UNIT_EFFECTIVITY_ID, MR_HEADER_ID, and FLEET_HEADER_ID.
• AHL_FLEET_HEADERS_B — fleet header definition (AFH), supplying fleet name, operating organization, and department.
• AHL_MR_HEADERS_B — maintenance requirement headers (AMH), providing the MR title.
• AHL_MR_ORGANIZATIONS — organization and department assignments for maintenance requirements (AMO), holding OPERATING_ORG_ID, MAINTENANCE_ORG_ID, MAINTENANCE_DEPT_ID, and MR_TITLE.
• AHL_DEPARTMENT_SHIFTS_V — a view used in the department/shift resolution logic.
• AHL_UE_SIMULATIONS — source of simulated unit effectivity records reflected by the SIM_UE_FLAG.
• HR_ORGANIZATION_UNITS and HR_GENERAL / HR_SECURITY packages — used to resolve organization names and to apply organization security.
• BOM_DEPARTMENTS — used to resolve the department name/description for the resolved maintenance department.

The view therefore sits on top of the fleet, maintenance requirement, and unit effectivity data model, resolving organizational attributes that are not stored in a single table.

Key Columns

• UNIT_EFFECTIVITY_ID — primary identifier of the unit effectivity record.
• SIM_UE_FLAG — indicates whether the row originates from a simulation record ('N' for real records as shown).
• UE_MR_HDR_ID, TITLE, MR_TITLE — the maintenance requirement header and its descriptive titles.
• UE_FLT_HDR_ID, FLEET_NAME, FLEET_OP_ORG_ID, FLEET_DEPT_ID — fleet identity and its operating organization and department.
• MR_OP_ORG_ID, MR_OPERATING_ORG_NAME — the operating organization from the maintenance requirement.
• MR_MAINTENANCE_ORG_ID, MR_MAINTENANCE_ORG_NAME — the resolved maintenance organization, derived by CASE logic that prioritizes the fleet organization when it differs from the MR organization, or when no MR title exists.
• MR_MAINTENANCE_DEPT_ID — the resolved maintenance department, following the same resolution rules and falling back to the fleet department.

Common Use Cases and Queries

The view is typically used to report on unit effectivity alongside the responsible maintenance organization and department, or to reconcile fleet and MR organizational assignments.

• Listing unit effectivity with resolved maintenance organization and department for operational reporting.
• Identifying records where the fleet operating organization differs from the maintenance requirement organization.
• Separating simulation records from live records using SIM_UE_FLAG.

Example query:

SELECT unit_effectivity_id,
       sim_ue_flag,
       fleet_name,
       mr_maintenance_org_name,
       mr_maintenance_dept_id
FROM   apps.ahl_ue_orgs_depts_v
WHERE  sim_ue_flag = 'N'
ORDER BY unit_effectivity_id;

Because the view references HR security packages, query results are subject to the organization security profile of the connected user.