Results for “ahl_unit_deferrals_vl”

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

Overview

AHL_UNIT_DEFERRALS_VL is a validated, translation-enabled view owned by the APPS schema and delivered as part of the AHL - Complex Maintenance Repair and Overhaul product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name follows Oracle's standard "_VL" convention, indicating that it exposes both the transactional columns of a base ("_B") table and the language-dependent descriptive columns of a translation ("_TL") table in a single, user-language-filtered result set.

Functionally, the view presents unit deferral records — maintenance deferrals applied against a unit's effectivity definition — allowing both deferral identity/attribute data and free-text remarks to be reported together. This makes the view a natural integration point for operational reporting, such as deferral status dashboards, and for interfaces that must read deferral data without joining the base and translation tables manually.

Underlying Base Objects

The view is defined over two documented base objects:

• AHL_UNIT_DEFERRALS_B — the base table holding non-translatable deferral data (aliased B in the view definition).
• AHL_UNIT_DEFERRALS_TL — the translation table holding language-specific text (aliased T).

Per the documented view text, the two are joined on B.UNIT_DEFERRAL_ID = T.UNIT_DEFERRAL_ID, with the additional predicate T.LANGUAGE = USERENV('LANG'). That predicate restricts the result to a single language row per deferral, so each deferral ID appears at most once, and the text returned is the session's current language. The ROW_ID column is sourced from B.ROWID. Note that the underlying objects are documented as synonyms within APPS rather than as the physical tables themselves; the view text further refers to AHL_UNIT_DEFERRALS_TL in the FROM clause.

Key Columns

The view exposes the complete set of columns from the base table plus REMARKS and APPROVER_NOTES from the translation table. The most significant include:

• UNIT_DEFERRAL_ID — primary key identifying the deferral record; the join key between the base and translation tables.
• UNIT_EFFECTIVITY_ID — links the deferral to the unit effectivity definition it applies to.
• UNIT_DEFERRAL_TYPE — classifies the deferral.
• SET_DUE_DATE — the due date established by the deferral.
• APPROVAL_STATUS_CODE — approval state of the deferral.
• DEFERRAL_EFFECTIVE_ON — the date on which the deferral takes effect; this is the column most directly associated with the user's search term "deferral_effective_on". This is often the caller's intent when searching for that term.
• DEFER_REASON_CODE, SKIP_MR_FLAG, AFFECT_DUE_CALC_FLAG — reason and behavioral flags controlling whether maintenance requirements are skipped or due-date calculations are affected.
• REMARKS and APPROVER_NOTES — translated free-text fields from the TL table.
• OBJECT_VERSION_NUMBER and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — concurrency and audit tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include reporting on deferrals awaiting approval, listing deferrals effective within a date range, and integration extracts that require both deferral attributes and translated remarks. Deferral lists are frequently filtered by the effective date column, which is why a search on "deferral_effective_on" resolves to this view.

A simple listing for a unit effectivity:

• SELECT unit_deferral_id, unit_deferral_type, deferral_effective_on, set_due_date, approval_status_code, remarks FROM ahl_unit_deferrals_vl WHERE unit_effectivity_id = :p_effectivity_id ORDER BY deferral_effective_on;

A date-range filter with approval status:

• SELECT unit_deferral_id, unit_effectivity_id, deferral_effective_on, approver_notes FROM ahl_unit_deferrals_vl WHERE deferral_effective_on BETWEEN :p_from AND :p_to AND approval_status_code = :p_status;

Because the view applies USERENV('LANG') automatically, consumers should not join to AHL_UNIT_DEFERRALS_TL again unless they require a specific language outside the session default. Queries against APPS.AHL_UNIT_DEFERRALS_VL must be run from a session with the AHL product's data access and with the appropriate language initialization, consistent with standard EBS multi-language reporting practice.