Search Results ahl_space_unavailable_b




Overview
Explore in AI Chat

Overview

The AHL_SPACE_UNAVAILABLE_B table is a core data object within the Oracle E-Business Suite (EBS) module for Complex Maintenance, Repair, and Overhaul (AHL). It serves as the primary transactional table for defining and storing space restrictions within a maintenance facility. In the context of asset and service management, this table is critical for capacity planning and scheduling, as it records periods when specific physical spaces (e.g., hangar bays, workshop stalls, inspection docks) are unavailable for work assignments. This ensures that maintenance operations, job scheduling, and resource allocation logic respect these constraints, preventing the booking of tasks into unavailable locations.

Key Information Stored

While the provided metadata does not list all columns, the structure centers on the SPACE_UNAVAILABILITY_ID, which is the table's primary key. This unique identifier is the anchor for all related data. The most critical foreign key is the SPACE_ID column, which links directly to the AHL_SPACES_B table to identify the specific physical location under restriction. Other typical columns in such a table would include effective start and end dates/times for the unavailability period, a reason code or description for the restriction, and creation/update audit information. The table's design as a "_B" (base) table indicates it holds the core transactional data, which is then paired with a corresponding "_TL" (translation) table for multilingual support.

Common Use Cases and Queries

The primary use case is to query active space restrictions during the scheduling of maintenance visits or jobs. A common operational report would list all current and future unavailability for a facility. Sample SQL to find unavailable spaces within a specific date range would join to the AHL_SPACES_B table to get space details:

  • SELECT sp.space_name, su.start_date_time, su.end_date_time FROM ahl_space_unavailable_b su, ahl_spaces_b sp WHERE su.space_id = sp.space_id AND su.start_date_time <= :p_end_date AND su.end_date_time >= :p_start_date;

Another critical use is validation within scheduling APIs or custom programs, where a check against this table is performed before assigning a work order to a space to prevent conflicts.

Related Objects

The table exists within a defined hierarchy of related AHL objects. The documented foreign key relationships are:

  • AHL_SPACES_B: This is the parent table, joined via AHL_SPACE_UNAVAILABLE_B.SPACE_ID = AHL_SPACES_B.SPACE_ID. This relationship ensures every restriction is defined for a valid, existing physical space.
  • AHL_SPACE_UNAVAILABLE_TL: This is the child translation table, joined via AHL_SPACE_UNAVAILABLE_B.SPACE_UNAVAILABILITY_ID = AHL_SPACE_UNAVAILABLE_TL.SPACE_UNAVAILABILITY_ID. It stores multilingual descriptions for the unavailability reason, supporting global deployments.

Given its function, this table is also likely referenced by various AHL scheduling and capacity planning APIs and may be used by views that aggregate resource availability data.