Search Results inst_notify_ind




Overview
Explore in AI Chat

Overview

IGSBV_USEC_MEETING_SCHEDULES is a read-only Oracle EBS view owned by the APPS schema and defined over the student records subsystem that underpins Oracle's Student Information / Student Systems product line. The view presents unit section occurrence scheduling data in a fully denormalised, flattened form intended for reporting, integration, and downstream consumption. Its name indicates its primary purpose: exposing the day-of-week, time-slot, and room allocation attributes of a scheduled meeting so that external processes can render, compare, or transmit "meeting notice" style output without joining multiple base tables. A user searching for a term such as "Meeting Notice 16-9-2026" is searching for the specific occurrence or scheduling record that corresponds to that calendar date; the view provides the column set from which that answer is constructed.

Underlying Base Objects

The documented definition is a single-table projection. The view selects from IGS_PS_USEC_OCCURS_ALL, an occurrence table belonging to the IGS (student systems) table family, qualified with WITH READ ONLY. No additional joins, unions, or subqueries are present in the view text, so the view is effectively a column-renamed and partially decoded layer over that one base object. Because the base table is an _ALL variant, it is expected to expose all records without the organisational unit filtering typically imposed by _V or security-checked variants; consumers must therefore apply their own institution or operating-unit predicates. The ETRM metadata records no additional referenced base objects beyond the single occurrence table. Several columns are supplied not from stored data but from literal lookup-resolution expressions embedded in the SELECT list, which are evaluated at query time.

Key Columns

Common Use Cases and Queries

Typical uses include producing meeting notices, timetables, and room-utilisation reports, and feeding scheduling data into external calendars. To locate a schedule effective on a specific date, filter on the date range and the relevant weekday indicator.

SELECT occurrence_identifier, start_time, end_time, building_code, room_code
FROM apps.igsbv_usec_meeting_schedules
WHERE start_date <= TO_DATE('16-09-2026','DD-MM-YYYY')
  AND NVL(end_date, TO_DATE('31-12-4712','DD-MM-YYYY')) >= TO_DATE('16-09-2026','DD-MM-YYYY')
  AND wednesday_indicator = 'Y';

Because 16 September 2026 falls on a Wednesday, the Wednesday indicator is the correct filter for that date. A second common pattern is retrieving all occurrence records for a unit section, ordering by start time, to build a consolidated timetable or to detect room conflicts across BUILDING_CODE and ROOM_CODE within overlapping START_TIME and END_TIME windows. All queries should observe the read-only nature of the view and apply explicit operating-unit constraints, since the underlying _ALL table is not restricted by row-level security.