Search Results igs_ad_room_all




Overview
Explore in AI Chat

Overview

The IGS_AD_ROOM_ALL table is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS), specifically designed to manage physical room information. Its primary role is to serve as a master repository for room definitions, enabling the scheduling of academic activities, admissions processes, and unit delivery by associating them with specific physical locations. As indicated by the "_ALL" suffix, the table is multi-org enabled, meaning it can store data partitioned by operating unit, a standard architectural pattern in EBS for supporting complex organizational structures. It is critical to note the metadata explicitly states the Student System module is marked as "Obsolete," and the table is "Not implemented in this database" for the referenced documentation instance. This suggests the table is part of a legacy or decommissioned product line, and its use in active implementations of EBS 12.1.1 or 12.2.2 should be carefully validated.

Key Information Stored

While the provided metadata does not list individual columns, the primary and unique key structures define the table's fundamental data entities. The table is uniquely identified by ROOM_ID (primary key IGS_AD_ROOM_PK). Furthermore, a unique key constraint (IGS_AD_ROOM_U2) enforces that the combination of BUILDING_ID and ROOM_CD is unique within the system. This logical structure indicates that the table stores, at a minimum, a system-generated surrogate key (ROOM_ID), a building identifier to group rooms, and a room code (e.g., "101", "Lab-A", "Auditorium") for human-readable identification. The foreign key relationships imply the table likely contains additional descriptive attributes such as room capacity, type, or facilities to support scheduling logic.

Common Use Cases and Queries

The primary use case for this table is the management and lookup of room details for scheduling and planning. In the context of admissions (AD), it could be used to schedule interview panels or committee meetings. For the Productive Systems (PS) module, it is central to scheduling unit section occurrences, with dedicated, preferred, or general room assignments. A typical query would join this table to scheduling entities to list all sessions occurring in a specific building or to find available rooms of a required capacity. Given its obsolete status, direct operational use is unlikely in current implementations; queries would typically be for historical data migration or reporting.

  • Sample Query (Historical Lookup): SELECT room_cd, building_id FROM igs_ad_room_all WHERE room_id = :p_room_id;
  • Reporting Use Case: Generating a legacy report of all rooms previously used for admissions panels or unscheduled classes.

Related Objects

The table sits at the center of a relational network primarily concerning scheduling and location assignment. As per the foreign keys, it is referenced by several key tables in the Student System:

These relationships underscore the table's historical role in connecting physical infrastructure data to core academic and administrative processes within the obsolete IGS module.