Search Results space_object_version_number




Overview
Explore in AI Chat

Overview

APPS.AHL_SPACE_UNAVABL_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema and registered under the FND Design Data path AHL.AHL_SPACE_UNAVABL_V. The object is classified as an internal view, carrying the standard Oracle restriction that it is intended solely for use by standard Oracle Applications programs rather than direct customer access.

The view presents consolidated information about space unavailability records within the Oracle Enterprise Asset Management (eAM) and Asset Lifecycle Management (ALM) domain, specifically the AHL (Asset) product family. It joins space definitions to their associated unavailability periods, organizational context, and department assignments, thereby offering a denormalized perspective suitable for reporting and integration purposes. The presence of both SPACE_OBJECT_VERSION_NUMBER and OBJECT_VERSION_NUMBER columns reflects Oracle's standard optimistic locking mechanism, which is the most likely subject of the user's search for "space_object_version_number."

Underlying Base Objects

According to documented ETRM 12.2.2 metadata, the view is defined over the following referenced base objects:

The view therefore acts as a join layer, combining space master data with its temporal unavailability records while enriching both with department, lookup, and HR organization attributes.

Key Columns

Common Use Cases and Queries

Typical uses include reporting on spaces that are unavailable during a given window, identifying which departments or organizations own unavailable spaces, and reconciling optimistic-locking version numbers during integration. A representative query follows:

SELECT space_id, space_name, space_object_version_number, space_unavailability_id, object_version_number, start_date, end_date, status_meaning, org_name FROM apps.ahl_space_unavabl_v WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));

Because the view is flagged Oracle Internal Use Only, customers should query it for read-only reporting purposes and avoid depending on its structure for custom extensions.