Search Results ahl_unit_effectivities_vl




Overview
Explore in AI Chat

Overview

Within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments, the view APPS.AHL_UNIT_EFFECTIVITIES_VL serves as the primary reporting and integration interface for unit effectivity data belonging to the AHL (Complex Maintenance Repair and Overhaul) product family. Unit effectivities represent the scheduling and forecasting records attached to maintainable units and item instances. Each row reflects a due, forecast, or accomplished maintenance requirement generated against a specific instance as identified through the CSI item instance identifier.

The _VL suffix denotes a "view with language" — a standard EBS construct that joins a base (_B) table with its translation (_TL) table, filtering the latter by the session language through USERENV('LANG'). This view therefore presents the descriptive and translatable content in the language of the querying user while exposing the full set of descriptive and transactional attributes from the base table. Object status is documented as VALID in the ETRM repository, and the view is owned by the APPS schema.

Underlying Base Objects

The view is defined over two documented synonyms:

The join condition is B.UNIT_EFFECTIVITY_ID = T.UNIT_EFFECTIVITY_ID, with the additional predicate T.LANGUAGE = USERENV('LANG'). This ensures that exactly one translated row is returned per base row, corresponding to the runtime language setting. Because the view also exposes B.ROWID AS ROW_ID, the underlying base row can be identified through a derived pseudo-column, which supports certain forms-based and integration patterns where row identity is required.

Key Columns

The view exposes the full column set of the base table plus the translated REMARKS column. Notable columns include:

Common Use Cases and Queries

This view is typically consumed by reports and integrations that need effectivity information in the user's language without a manual join to the translation table. A representative query retrieving upcoming due effectivities for a specific unit instance is:

SELECT ue.unit_effectivity_id,
       ue.csi_item_instance_id,
       ue.status_code,
       ue.due_date,
       ue.latest_due_date,
       ue.remarks
FROM   apps.ahl_unit_effectivities_vl ue
WHERE  ue.csi_item_instance_id = :p_instance_id
AND    ue.due_date >= TRUNC(SYSDATE)
ORDER  BY ue.due_date;

A second common pattern joins to the maintenance requirement header to report effectivity context for AHL work planning:

SELECT ue.mr_header_id,
       ue.unit_effectivity_id,
       ue.forecast_sequence,
       ue.due_counter_value,
       ue.remarks
FROM   apps.ahl_unit_effectivities_vl ue
WHERE  ue.repetitive_mr_flag = 'Y'
AND    ue.status_code = 'ACTIVE';

Because it is a view rather than a table, it is read-only and cannot be used for DML. Referential integrity, concurrency control via OBJECT_VERSION_NUMBER, and standard WHO audit columns are all inherited from the base table, ensuring consistent behavior across EBS 12.1.1 and 12.2.2.