Search Results igsfv_usec_meeting_schedules




Overview

The view APPS.IGSFV_USEC_MEETING_SCHEDULES is a reporting and integration layer within the Oracle E-Business Suite Student System (product code IGS). It presents unit section meeting schedule information, exposing each occurrence of a scheduled class meeting together with its day-of-week indicators, start and end times, assigned location (building and room), dedicated room/building, preferred room/building, and the effective start and end dates of the schedule. The view is defined in the APPS schema and holds a VALID status in the ETRM 12.2.2 dictionary.

Its role is to flatten the normalized occurrence data held in the base occurrence table into a form suitable for reporting, enrollment-related display, and downstream integration. Descriptive attributes for buildings and rooms are resolved inline through outer joins, removing the need for consumers to perform additional lookups. In the context of the searched term no_set_day_indicator, the view exposes the column NO_SET_DAY_INDICATOR (aliased from USO.NO_SET_DAY_IND), which flags meeting occurrences that have no fixed set day assigned. This indicator complements the seven day-of-week columns and allows reporting logic to distinguish schedules defined by explicit weekday versus those without a defined meeting day.

Underlying Base Objects

The view is defined over one primary base table and six outer-joined reference tables:

  • IGS_PS_USEC_OCCURS_ALL (alias USO) — the driving table, holding unit section occurrence records including day indicators, times, room/building codes, and status fields.
  • IGS_AD_BUILDING_ALL (aliases BLD1, BLD2, BLD3) — resolves descriptions for the assigned, dedicated, and preferred buildings respectively.
  • IGS_AD_ROOM_ALL (aliases ROM1, ROM2, ROM3) — resolves descriptions for the assigned, dedicated, and preferred rooms respectively.

All joins to the building and room tables are outer joins (indicated by the (+) operator), so an occurrence row is returned even when its building or room code is null or unmatched. The ETRM metadata lists no separately documented base objects, but the view SQL clearly identifies the tables above as its direct dependencies. Because _ALL tables are involved, the view honors multi-org (operating unit) security as applied to those base entities.

Key Columns

Common Use Cases and Queries

Typical consumers use the view to list meeting schedules for a unit section, to identify occurrences without an assigned day, and to report location utilization. The following query returns schedules for a given unit section, highlighting the no-set-day flag:

SELECT occurrence_identifier,
       unit_section_id,
       monday_indicator,
       tuesday_indicator,
       wednesday_indicator,
       thursday_indicator,
       friday_indicator,
       start_time,
       end_time,
       building_description,
       room_description,
       no_set_day_indicator
FROM   apps.igsfv_usec_meeting_schedules
WHERE  unit_section_id = :p_unit_section_id
AND    cancel_flag = 'N';

To isolate occurrences that carry no fixed meeting day, filter on the searched column: WHERE no_set_day_indicator = 'Y'. Additional filters on to_be_announced_indicator support reporting of locations pending confirmation, while start_date and end_date constrain schedules to a term window. A sample query returns schedules with their room and building descriptions:

SELECT occurrence_identifier,
       building_description,
       room_description,
       start_date,
       end_date
FROM   apps.igsfv_usec_meeting_schedules
WHERE  start_date >= :p_term_start
AND    end_date   <= :p_term_end
AND    abort_flag = 'N';

Because building and room descriptions are resolved within the view, these queries avoid secondary joins and remain suitable for concurrent programs, OAF/Forms data sources, and integration extracts.