Search Results ahl_space_unavailable_vl




Overview
Explore in AI Chat

Overview

The AHL_SPACE_UNAVAILABLE_VL view is a public, language-sensitive (VL) database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the AHL product family — Complex Maintenance Repair and Overhaul (CMRO) — and is documented as VALID in ETRM for both release 12.1.1 and 12.2.2. As described in the ETRM metadata, the view "stores the query relates to space restriction information." In practical terms, it exposes the set of records that define periods during which a physical space (such as a hangar bay, dock, maintenance slot, or overhaul cell) is unavailable for scheduling or use.

Because the object is a VL view, it joins the base entity table with its translation table and filters on the session language via USERENV('LANG'). It therefore presents a single, de-normalized row per space-unavailability record with the translated description already resolved. This makes it the preferred access path for forms, concurrent programs, OAF pages, and custom reports that need to display space restriction data without performing an explicit language join. It is read-only in practice; all DML is performed against the underlying _B and _TL tables.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both accessed through synonyms:

  • AHL_SPACE_UNAVAILABLE_B — the base (non-translated) table holding the transactional and descriptive-flexfield columns, aliased as B in the view text.
  • AHL_SPACE_UNAVAILABLE_TL — the translation table holding the language-specific DESCRIPTION column, aliased as T.

The two are joined on the primary key SPACE_UNAVAILABILITY_ID (B.SPACE_UNAVAILABILITY_ID = T.SPACE_UNAVAILABILITY_ID), with the additional predicate T.LANGUAGE = USERENV('LANG') restricting the result to the current runtime language. The view also projects B.ROWID as ROW_ID, the standard mechanism by which EBS VL views preserve a row identifier for downstream processing. No additional tables are joined, so the view is a straightforward master/translation construct.

Key Columns

  • SPACE_UNAVAILABILITY_ID — primary key of the unavailability record; the join key between the _B and _TL tables.
  • SPACE_ID — identifies the space to which the restriction applies; the operational link back to the space definition.
  • START_DATE / END_DATE — the effective window during which the space is unavailable.
  • DESCRIPTION — the translated, user-facing description sourced from the _TL table.
  • ROW_ID — the underlying rowid of the _B record, exposed to support VL View conventions.
  • OBJECT_VERSION_NUMBER — optimistic locking column for the base record.
  • SECURITY_GROUP_ID — used for Multi-Org / security-group filtering.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (Descriptive Flexfield) columns carried through from the base table.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include reporting on space restrictions for maintenance planning, validating scheduling conflicts, and exposing restriction data to integrations or custom OAF pages. A simple availability check for a given space and date range:

  • SELECT space_id, start_date, end_date, description FROM apps.ahl_space_unavailable_vl WHERE space_id = :p_space_id AND start_date < :p_end AND end_date > :p_start;
  • SELECT space_unavailability_id, space_id, description FROM apps.ahl_space_unavailable_vl WHERE TRUNC(start_date) BETWEEN :p_from AND :p_to;

Because the view applies the USERENV('LANG') predicate automatically, callers must set the session language (for example via FND_GLOBAL.APPS_INITIALIZE) to retrieve the correct translated description. Queries against the view should always be schema-qualified as APPS.AHL_SPACE_UNAVAILABLE_VL.