Results for “ue_flt_hdr_id”

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

Overview

APPS.AHL_UE_ORGS_DEPTS_V is a reporting view within the Oracle Enterprise Asset Management (eAM) and Maintenance Management product family (AHL schema). Its name reflects its purpose: it resolves Unit Effectivity (UE) records to their associated organizations and departments. Specifically, the view exposes, for each unit effectivity row, the operating organization and department of the fleet at the due date, alongside the operating and maintenance organization and department of the referenced Maintenance Requirement.

The view is designated Oracle Internal Use Only, meaning Oracle does not support direct data access except through standard Oracle Applications programs. It nonetheless serves as a convenient read-only projection joining maintenance requirement headers, fleet headers, unit effectivities, department shifts, and HR organization data, which makes it useful for diagnostic queries and reporting extensions where a supported API does not exist.

Underlying Base Objects

According to ETRM 12.2.2 metadata, AHL_UE_ORGS_DEPTS_V is defined over the following objects (most referenced through APPS synonyms): AHL_UNIT_EFFECTIVITIES_B, which supplies the driving UNIT_EFFECTIVITY_ID; AHL_MR_HEADERS_B, the Maintenance Requirement header; AHL_MR_ORGANIZATIONS, which links the MR to its operating and maintenance organizations and departments; AHL_FLEET_HEADERS_B for fleet name and fleet org context; AHL_UE_SIMULATIONS to determine whether the row originates from a simulation plan or a primary plan; AHL_DEPARTMENT_SHIFTS_V for department shift data; BOM_DEPARTMENTS for department identifiers; and the HR_GENERAL and HR_SECURITY packages with HR_ORGANIZATION_UNITS for organization name resolution and security-based filtering. The joins therefore traverse a hierarchy of unit effectivity → maintenance requirement → organizations/departments → HR organization master.

Key Columns

• UNIT_EFFECTIVITY_ID — Surrogate key for the unit effectivity record; the primary row identifier.
• SIM_UE_FLAG — Character flag indicating whether the effectivity belongs to a simulation plan or a primary plan.
• UE_MR_HEADER_ID / UE_MR_TITLE / ORG_MR_TITLE — Maintenance Requirement identifier and titles (unit-level and organization-level).
• UE_FLEET_HEADER_ID / UE_FLEET_NAME — Fleet identity associated with the unit effectivity.
• FLEET_OPERATING_ORG_ID / FLEET_DEPT_ID — The operating organization and department of the fleet at the due date.
• MR_OPERATING_ORG_ID / MR_OPERATING_ORG_NAME — Operating organization assigned to the Maintenance Requirement, with HR-resolved name.
• MR_MAINTENANCE_ORG_ID / MR_MAINTENANCE_ORG_NAME — MR_MAINTENANCE_ORG_ID is the column most commonly sought when users search for mr_maintenance_org_id; it identifies the maintenance organization responsible for executing the requirement. The paired name column provides the HR organization display name.
• MR_MAINTENANCE_DEPT_ID / MR_MAINTENANCE_DEPT_NAME — Maintenance department assigned to the requirement.

Common Use Cases and Queries

Typical scenarios include identifying the responsible maintenance organization for a set of unit effectivities, reconciling fleet operating context against MR maintenance assignments, and auditing simulation versus primary plan effectivities. A representative query filtering on the maintenance organization is:

SELECT unit_effectivity_id,
       sim_ue_flag,
       ue_mr_header_id,
       ue_fleet_name,
       mr_operating_org_name,
       mr_maintenance_org_id,
       mr_maintenance_org_name,
       mr_maintenance_dept_name
FROM   apps.ahl_ue_orgs_depts_v
WHERE  mr_maintenance_org_id = :p_maintenance_org_id
ORDER  BY ue_mr_header_id, unit_effectivity_id;

Because the view is internal-use and security-filtered through HR packages, results are constrained by the session's organization security profile. It should be used for inquiry and reporting rather than as an integration interface; production logic should call the corresponding eAM APIs. Note the metadata documents a column listed as MR_MAINTENANCE_DEPT_ NAME; the embedded space reflects a documentation artifact, and the actual column name should be verified in the data dictionary.