Search Results igs_ad_room_v

Overview

The view IGS_AD_ROOM_V belongs to the Oracle E-Business Suite IGS — Student System product family, a module marked as obsolete in the ETRM documentation. It presents room records, exposing the physical or logical rooms that comprise the institution's teaching and administrative estate. In an admissions, scheduling, and student-record context, rooms are reference data against which class sections, examinations, and events are scheduled, so the view functions as a reporting and integration surface for validated room master data rather than as an operational entry form.

Unlike a denormalized reporting view, IGS_AD_ROOM_V performs a single decoded lookup join, translating the coded PRIMARY_USE_CD value into a printable meaning via IGS_LOOKUPS_VIEW. This makes the view directly consumable by reports, interfaces, and extracts that must render human-readable room usage without embedding lookup logic in each query. ETRM records that the object is not implemented in this database and carries no documented owner, and that no referenced base objects are documented in the 12.2.2 metadata — facts that materially affect how the view should be treated on any given instance.

Underlying Base Objects

The view text is defined over exactly two sources:

• IGS_AD_ROOM (aliased RM) — the base room table supplying all descriptive and audit columns.
• IGS_LOOKUPS_VIEW (aliased LKUP) — the decoded lookup source joined to supply the PRIMARY_USE_DESC meaning.

The join is an equi-join on RM.PRIMARY_USE_CD = LKUP.LOOKUP_CODE, restricted by the predicate LKUP.LOOKUP_TYPE = 'PRIMARY_USE'. Because the predicate is applied in the WHERE clause rather than as an outer join, any room whose PRIMARY_USE_CD is null or does not resolve to an active 'PRIMARY_USE' lookup row is silently excluded from the result set. Consumers requiring a full room listing should therefore query the base table IGS_AD_ROOM directly or outer-join the lookup.

ETRM lists no referenced base objects for 12.2.2 and no owner, so in a live 12.1.1 or 12.2.2 instance the view exists only if the legacy Student System schemas are installed. Availability must be verified per environment before any dependent report or interface is built.

Key Columns

• ROW_ID — surrogate primary key of the underlying room record; the safest join key to other IGS tables.
• ROOM_ID — the business identifier for the room.
• ROOM_CD — the short user-facing room code, typically used in scheduling displays.
• BUILDING_ID — foreign reference to the parent building record.
• DESCRIPTION — free-text room description.
• PRIMARY_USE_CD — the coded primary usage of the room; this is the column referenced in the PRIMARY_USE lookup join.
• PRIMARY_USE_DESC — the decoded meaning of PRIMARY_USE_CD sourced from the lookup view; the user searched term primary_use_cd maps directly to these two columns.
• CAPACITY — the seat capacity of the room, used for room-allocation and utilization analysis.
• CLOSED_IND — indicates whether the room is closed and therefore unavailable for scheduling.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, documenting who and when a room record was created or last modified.

Common Use Cases and Queries

Typical scenarios include room inventory reports, capacity analysis, and decoded usage lists for downstream scheduling or data-warehouse loads. Because PRIMARY_USE_DESC is pre-resolved, BI extracts avoid duplicating lookup joins. A representative query is:

• SELECT ROOM_CD, BUILDING_ID, DESCRIPTION, PRIMARY_USE_CD, PRIMARY_USE_DESC, CAPACITY, CLOSED_IND FROM IGS_AD_ROOM_V WHERE CLOSED_IND = 'N' AND PRIMARY_USE_CD = 'LECTURE' ORDER BY BUILDING_ID, ROOM_CD;
• SELECT PRIMARY_USE_DESC, COUNT(*), SUM(CAPACITY) FROM IGS_AD_ROOM_V GROUP BY PRIMARY_USE_DESC ORDER BY 2 DESC;

Given the obsolete status and the absence of a documented owner or implemented base objects, these queries should be validated against the specific instance before deployment.