Results for “ahl_unit_effectivities_vl”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
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:
- AHL_UNIT_EFFECTIVITIES_B — the base table holding all transactional and descriptive columns.
- AHL_UNIT_EFFECTIVITIES_TL — the translation table holding language-specific content, principally the
REMARKScolumn.
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:
UNIT_EFFECTIVITY_ID— primary identifier for the effectivity record.CSI_ITEM_INSTANCE_ID— the item instance (unit) to which the effectivity applies.MR_HEADER_ID,MR_INTERVAL_ID,MR_EFFECTIVITY_ID,PROGRAM_MR_HEADER_ID— maintenance requirement associations driving the effectivity.STATUS_CODE— current status of the effectivity.EARLIEST_DUE_DATE,DUE_DATE,LATEST_DUE_DATE,ACCOMPLISHED_DATE,SET_DUE_DATE— temporal scheduling and tolerance boundaries.DUE_COUNTER_VALUE,COUNTER_ID— counter-based due tracking.FORECAST_SEQUENCE,REPETITIVE_MR_FLAG,TOLERANCE_FLAG— forecasting and eligibility flags.PRECEDING_UE_ID,DEFER_FROM_UE_ID,ORIG_DEFERRAL_UE_ID— chaining and deferral relationships between effectivities.MESSAGE_CODE,CANCEL_REASON_CODE,OBJECT_TYPE,APPLICATION_USG_CODE— diagnostic and classification attributes.ATTRIBUTE1throughATTRIBUTE_CATEGORY— the standard DFF (descriptive flexfield) columns.REMARKS— the translatable descriptive text from the TL table.
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.
-
This view stores the query to retrieve unit effectivities information based on the base( AHL_UNIT_EFFECTIVITIES_B ) and TL ( AHL_UNIT_EFFECTIVITIES_TL ) tables.
APPS.AHL_UNIT_EFFECTIVITIES_VL·↳ AHL_UNIT_EFFECTIVITIES_B·↳ AHL_UNIT_EFFECTIVITIES_TL·Explore AHL module →
-
This view stores the query to retrieve unit effectivities information based on the base( AHL_UNIT_EFFECTIVITIES_B ) and TL ( AHL_UNIT_EFFECTIVITIES_TL ) tables.
APPS.AHL_UNIT_EFFECTIVITIES_VL·↳ AHL_UNIT_EFFECTIVITIES_B·↳ AHL_UNIT_EFFECTIVITIES_TL·Explore AHL module →
-
This view stores the query to retrieve unit effectivities information based on the base( AHL_UNIT_EFFECTIVITIES_B ) and TL ( AHL_UNIT_EFFECTIVITIES_TL ) tables striped by the language and application usage code.
APPS.AHL_UNIT_EFFECTIVITIES_APP_V·↳ AHL_UNIT_EFFECTIVITIES_VL·↳ FND_PROFILE·Explore AHL module →
-
This view stores the query to retrieve unit effectivities information based on the base( AHL_UNIT_EFFECTIVITIES_B ) and TL ( AHL_UNIT_EFFECTIVITIES_TL ) tables striped by the language and application usage code.
APPS.AHL_UNIT_EFFECTIVITIES_APP_V·↳ AHL_UNIT_EFFECTIVITIES_VL·↳ FND_PROFILE·Explore AHL module →
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2