Results for “status_description”

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

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:

• AHL_UNIT_EFFECTIVITIES_APP_V (VIEW) — appears twice in the definition, aliased SR_UE (the effectivity tied to the Service Request) and UE (the related effectivity). It supplies unit effectivity identity, version, item instance, status, and maintenance requirement header reference.
• AHL_MR_HEADERS_VL (VIEW) — aliased MR, supplying the maintenance requirement title, version number, description, and program type code.
• AHL_UE_RELATIONSHIPS (SYNONYM) — aliased UER, the association table linking UE_ID to RELATED_UE_ID and carrying the relationship code. In this view only rows with RELATIONSHIP_CODE = 'PARENT' are retained.
• CS_INCIDENTS_ALL_B (SYNONYM) — aliased CS, the Service Request (incident) base table.
• FND_LOOKUP_VALUES_VL (VIEW) — used three times as inline lookup subqueries: F1 for AHL_UNIT_EFFECTIVITY_STATUS, F2 for AHL_FMP_MR_RELATIONSHIP, and F3 for AHL_FMP_MR_PROGRAM_TYPE.
• FND_PROFILE (PACKAGE) — referenced for profile option evaluation, typically for multi-org or MO security context.

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

• UNIT_EFFECTIVITY_ID, OBJECT_VERSION_NUMBER, CSI_ITEM_INSTANCE_ID, STATUS_CODE — identity, optimistic locking version, item instance, and status of the related unit effectivity (UE).
• STATUS_MEANING / STATUS_DESCRIPTION — decoded effectivity status from the AHL_UNIT_EFFECTIVITY_STATUS lookup.
• MR_HEADER_ID, MR_TITLE, MR_VERSION, MR_DESCRIPTION — maintenance requirement header details.
• PROGRAM_TYPE_CODE, PROGRAM_TYPE_MEANING, PROGRAM_TYPE_DESCRIPTION — program classification decoded from AHL_FMP_MR_PROGRAM_TYPE.
• CS_INCIDENT_ID — the Service Request identifier linking the effectivity to the incident.
• UE_RELATIONSHIP_ID, RELATIONSHIP_CODE, RELATIONSHIP_MEANING, RELATIONSHIP_DESCRIPTION — the association between related effectivities. RELATIONSHIP_MEANING is the translated display value for RELATIONSHIP_CODE from the AHL_FMP_MR_RELATIONSHIP lookup, which is why searches for that term typically surface this view.

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.