Results for “igs_ad_room”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGS_AD_ROOM view is a reporting and integration object within the Oracle E-Business Suite Student System (IGS) module. In the context of Oracle EBS 12.1.1 and 12.2.2, this view exposes room-level facility data maintained by the academic scheduling and admissions infrastructure. It presents a secure, organization-filtered projection of room records, allowing downstream forms, concurrent programs, and reports to retrieve room definitions without querying the underlying base table directly.

The view is important because it enforces Oracle's multi-organization (Multi-Org) access control at the database layer. Rather than requiring every consumer to replicate org-isolation logic, the view embeds a predicate that restricts rows to the operating unit identified by the session's client information. This design is consistent with other IGS "security" views that expose _ALL tables in a controlled manner.

It should be noted that the metadata classifies the IGS Student System as obsolete, and the view is documented as "Not implemented in this database" in the ETRM reference. This means the view may not exist in every instance, and its presence depends on whether the Student System product was licensed and installed. In typical EBS deployments focused on financials, supply chain, or HR, IGS_AD_ROOM will be absent.

Underlying Base Objects

The view is defined over a single documented base object: IGS_AD_ROOM_ALL. The _ALL suffix indicates that the table stores room records across all operating units, with each row tagged by an ORG_ID. The view applies a WHERE clause that filters this table against the current session's organization context, effectively converting the multi-org table into an operating-unit-specific result set.

The filtering logic uses USERENV('CLIENT_INFO') to obtain the client identifier established by the Multi-Org initialization routine. The value is parsed via SUBSTRB and DECODE to handle blank or null client information, and the comparison uses NVL with a sentinel value of -99 so that sessions without an assigned organization still return a deterministic set rather than failing. The view also exposes ROWID as ROW_ID, which is a common EBS pattern enabling the view to support updateable, row-identified access.

Key Columns

• ROW_ID — The base table ROWID, exposed for row-level addressing and updateability.
• ORG_ID — The operating unit identifier that governs Multi-Org security partitioning.
• ROOM_ID — The unique surrogate primary key for a room record.
• BUILDING_ID — Foreign key linking the room to its parent building.
• ROOM_CD — The user-facing room code used in scheduling and reporting.
• DESCRIPTION — A descriptive name or label for the room.
• PRIMARY_USE_CD — A code indicating the room's primary function (for example, lecture, laboratory, or examination).
• CAPACITY — The maximum occupancy or seating capacity of the room.
• CLOSED_IND — A flag indicating whether the room is currently closed or unavailable.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each record and when.

Common Use Cases and Queries

The view is typically consumed by academic scheduling processes, room-booking validations, and reporting on facility utilization. A representative query retrieves active rooms for the current operating unit:

• SELECT room_id, room_cd, description, capacity FROM igs_ad_room WHERE closed_ind = 'N' ORDER BY room_cd;
• SELECT building_id, COUNT(*) FROM igs_ad_room GROUP BY building_id;
• SELECT room_cd, capacity FROM igs_ad_room WHERE capacity >= :required_capacity;

Because the view performs org filtering automatically, no additional ORG_ID predicate is required when the session's client information is correctly initialized by Multi-Org. In integration scenarios, the view can be used to extract room master data for loading into external scheduling systems or data warehouses, with the audit columns supporting incremental extract logic based on LAST_UPDATE_DATE. Administrators should confirm the object exists in their instance before relying on it, given its obsolete classification.