Search Results primary_use

Overview

The view APPS.IGS_AD_ROOM_V is a reporting and integration construct within the Oracle E-Business Suite Student System (the IGS module family). It exposes room (physical space) records drawn from the institutional room master, joined to the lookup subsystem so that the coded value held on the base table is presented alongside its human-readable meaning. Specifically, the view denormalizes IGS_AD_ROOM by resolving primary_use_cd against IGS_LOOKUPS_VIEW for the lookup type PRIMARY_USE. This results in a self-documenting row in which the primary-use code and its description appear together, removing the need for downstream consumers to perform their own lookup joins.

Because the view is owned by APPS, it is available to any report, concurrent program, or integration that queries under the standard EBS naming convention. The user search term primary_use maps directly to two columns exposed here — the stored code (primary_use_cd) and the derived description (primary_use_desc). The view carries no documented base objects in the ETRM metadata beyond those appearing in its SELECT text, and it is not documented as an editioned or materialized object.

Underlying Base Objects

Two objects are referenced in the view definition:

• IGS_AD_ROOM — the room master table, aliased as rm. All descriptive and auditable columns (room code, building, capacity, closed indicator, and WHO columns) originate here. It is the driving table in the join.
• IGS_LOOKUPS_VIEW — the lookup view, aliased as lkup. Only the rows matching lookup type PRIMARY_USE participate in the join.

The join predicate is rm.primary_use_cd = lkup.lookup_code, with the constant filter lkup.lookup_type = 'PRIMARY_USE'. Consequently, the view returns only rooms whose primary_use_cd has an active, matching lookup entry; rooms lacking a valid lookup code are silently excluded. This implicit inner-join behavior is a critical behavioral characteristic for anyone using the view as an extract source.

Key Columns

• ROW_ID — surrogate identifier for the room row, used as a stable technical key.
• ROOM_ID — the business identifier of the room.
• ROOM_CD — the room code or short name by which the room is commonly referenced.
• BUILDING_ID — foreign reference to the building in which the room is located.
• DESCRIPTION — free-text description of the room.
• PRIMARY_USE_CD — the coded primary use of the room, sourced from IGS_AD_ROOM.
• PRIMARY_USE_DESC — the meaning of the primary-use code, resolved from IGS_LOOKUPS_VIEW; this is the column users typically search on.
• CAPACITY — the seating or occupancy capacity of the room.
• CLOSED_IND — indicator of whether the room is closed for scheduling or use.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit (WHO) columns reflecting row provenance and change tracking.

Common Use Cases and Queries

Typical usages include room inventory reports, capacity and utilization analysis, integrations feeding scheduling or timetabling systems, and ad-hoc extracts filtered by primary use. Because the view has already resolved the lookup, reports avoid a manual join and can group directly on the description.

Rooms by primary use:

SELECT primary_use_cd, primary_use_desc, COUNT(*) room_count
FROM   apps.igs_ad_room_v
GROUP  BY primary_use_cd, primary_use_desc;

Locating open rooms above a capacity threshold:

SELECT room_cd, building_id, primary_use_desc, capacity
FROM   apps.igs_ad_room_v
WHERE  closed_ind = 'N'
AND    capacity >= 30
ORDER  BY capacity DESC;

Audit extract of recently changed rooms:

SELECT room_cd, primary_use_desc, last_updated_by, last_update_date
FROM   apps.igs_ad_room_v
WHERE  last_update_date >= TRUNC(SYSDATE) - 30;

Note that any room whose primary_use_cd is null or lacks a PRIMARY_USE lookup will not appear; queries requiring a complete inventory should source IGS_AD_ROOM directly and outer-join the lookup.