Search Results mr_description




Overview
Explore in AI Chat

Overview

APPS.AHL_SR_UE_ASSOCIATIONS_V is a reporting view within the Oracle E-Business Suite AHL (Complex Maintenance Repair and Overhaul) module. Its documented purpose is to retrieve the unit effectivities that are associated to a Service Request. In ETRM terms, a unit effectivity identifies a physical or tracked configuration item or component against which maintenance activity is planned, while a Service Request captured in Oracle Service (CS_INCIDENTS_ALL_B) represents the field or customer-reported issue that drives the maintenance work. This view bridges the two: given a Service Request, it exposes the related unit effectivities, the maintenance requirement headers linked to them, and the relationship semantics that connect the associated unit effectivities to one another.

The view is validated (status VALID) under the APPS schema and is intended primarily for reporting and integration. Because it joins service incidents, maintenance requirement headers, and effectivity relationships in a single flattened result set, it is well suited for building concurrent program extracts, Oracle Discoverer worksheets, OBIEE/BI Publisher data sources, or custom forms and APIs that must present the maintenance context of a Service Request without requiring callers to reconstruct the join graph manually.

Underlying Base Objects

The view is defined over the following documented base objects:

Joins are driven from the Service Request-linked effectivity (SR_UE) through UER to the related effectivity (UE), then to its maintenance requirement header. Effectivities in DEFERRED or EXCEPTION status, or with a null status, are excluded from the SR_UE side.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all unit effectivities and their maintenance requirements for a given Service Request, reporting on parent-child effectivity relationships with decoded meaning, and extracting effectivity status and program type for maintenance dashboards.

Retrieve all associations for a Service Request:

SELECT cs_incident_id, unit_effectivity_id, csi_item_instance_id,
       status_meaning, mr_title, mr_version, program_type_meaning,
       relationship_code, relationship_meaning
FROM   apps.ahl_sr_ue_associations_v
WHERE  cs_incident_id = :p_incident_id;

Find all parent relationships and their meanings for a maintenance requirement:

SELECT mr_header_id, mr_title, relationship_meaning,
       COUNT(*) related_effectivities
FROM   apps.ahl_sr_ue_associations_v
WHERE  relationship_code = 'PARENT'
GROUP  BY mr_header_id, mr_title, relationship_meaning;

Because the view enforces the PARENT relationship filter and excludes DEFERRED/EXCEPTION effectivities, consumers can rely on it as a curated set of active, parent-level associations suitable for downstream maintenance planning and reporting.