Search Results dedicated_room_description

Overview

IGS_PS_USEC_OCCURS_V is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It belongs to the Student Systems / Student Records family of products (the IGS_PS_* namespace), which supports scheduling of unit section occurrences and their associated room and building resources. The view exposes occurrence-level scheduling records together with decoded, human-readable descriptions of buildings and rooms drawn from auxiliary reference tables.

The object is a denormalized convenience view rather than a table; it presents a flattened, join-enriched row set that application reports, concurrent programs, and external integrations can query without manually resolving the multiple building and room lookups. It is particularly relevant when reporting on the physical location of scheduled classes and examinations, since it resolves three distinct location concepts — scheduled, dedicated, and preferred — each with separate building and room codes and their corresponding descriptions. This is the key driver for the search term "dedicated_room_description", which is one of the decoded room description columns returned by the view.

Underlying Base Objects

The ETRM metadata provided does not document any referenced base objects for this view, though the view text itself reveals its principal source through column prefixes and join aliases. The primary driving table is the unit section occurrence table, aliased uso (consistent with the IGS_PS_USC_OCCURRENCES naming convention), which supplies occurrence identity, day-of-week flags, times, status, attributes, and WHO/audit columns.

Three building reference aliases (bld1, bld2, bld3) and three room reference aliases (rom1, rom2, rom3) supply descriptions for the scheduled, dedicated, and preferred location sets respectively. A lookup alias (lkup) resolves the schedule status code into a meaningful description. Because the metadata lists no documented base objects, the precise table names should be confirmed against the live data dictionary, but the functional dependency on the occurrence table, building reference, room reference, and lookup tables is evident from the view definition.

Key Columns

• unit_section_occurrence_id, uoo_id, row_id — primary identifiers and the ROWID used for row-level addressing.
• monday through sunday — day-of-week scheduling flags for the occurrence.
• start_time, end_time — the scheduled time window for the occurrence.
• building_code, building_desc, room_code, room_desc — the primary assigned location.
• scheduled_building_code, scheduled_building_desc, scheduled_room_code, scheduled_room_desc — the originally scheduled location.
• dedicated_building_code, dedicated_building_desc, dedicated_room_code, dedicated_room_description — the dedicated (reserved) location, including the description column named in the user's search.
• preferred_building_code, preferred_building_desc, preferred_room_code, preferred_room_desc — the preferred location for the occurrence.
• schedule_status, schedule_status_desc — status code and its decoded meaning.
• instructor_id, surname, person_number — instructor reference columns (surname and person_number are returned as NULL placeholders in the view text).
• attribute_category through attribute20 — descriptive flexfield columns.
• error_text, status_last_updated — scheduling error messaging and status audit information.
• request_id, program, and the WHO columns — audit and concurrent program tracking.

Common Use Cases and Queries

Typical uses include timetable generation, room utilization reports, examination scheduling, and integration extracts feeding downstream timetabling systems. A common pattern is to report the dedicated room description alongside the scheduled location for a given occurrence.

SELECT unit_section_occurrence_id,
       scheduled_room_desc,
       dedicated_room_description,
       preferred_room_desc,
       schedule_status_desc
FROM   apps.igs_ps_usec_occurs_v
WHERE  dedicated_room_code IS NOT NULL;

For day-of-week filtering, callers constrain on the relevant day column:

SELECT unit_section_occurrence_id, room_desc, start_time, end_time
FROM   apps.igs_ps_usec_occurs_v
WHERE  monday = 'Y'
AND    building_code = :p_building;

Because the view exposes ROWID-based addressing and WHO/audit columns, it supports both reporting and controlled update/integration scenarios. As with all APPS public views, access should be granted through the appropriate responsibility rather than direct grants, and consumers should validate available columns against their specific 12.1.1 or 12.2.2 instance, given the limited base-object documentation in the ETRM metadata.