Search Results monday_indicator

Overview

IGSBV_USEC_MEETING_SCHEDULES is a read-only view within the Oracle E-Business Suite Student System (IGS) product family. It presents the scheduling information associated with unit section occurrences, exposing the meeting pattern — the day indicators, start and end times, the physical location (building and room), and any dedicated or preferred building/room assignments — along with the effective start and end dates of each meeting schedule. In addition to the meeting detail itself, the view surfaces workflow-related attributes such as notification status, error text, and the CANCEL_FLAG and ABORT_FLAG indicators, together with standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE).

The Student System is classified as obsolete in the ETRM registry, and this object is documented as "Not implemented in this database." Notwithstanding that status, the view's metadata is significant because it defines a clean, denormalized projection of occurrence scheduling data that reporting and integration consumers can query without joining the underlying occurrence and lookup tables directly. It therefore serves as a pre-joined reporting surface for timetabling, room utilization, and schedule-cancellation analysis.

Underlying Base Objects

The view is defined over a single documented base object: IGS_PS_USEC_OCCURS_ALL. No additional referenced base objects are documented in the ETRM metadata. The view text is a straightforward projection with a WITH READ ONLY clause, meaning no DML is permitted against it. The view also performs inline lookup decoding for two attributes: the schedule status is derived through the IGS_LOOKUP_VALUES lookup by SCHEDULE_TYPE MEANING, and the preferred region code is derived through IGS_LOOKUP_VALUES by IGS_OR_LOC_REGION MEANING. These decodes are embedded in the view definition rather than exposed as separate joins, which simplifies consumption but means the lookup tables must be populated and correctly configured for the status and region descriptions to resolve.

Key Columns

• OCCURRENCE_IDENTIFIER / UNIT_SECTION_OCCURRENCE_ID / UNIT_SECTION_ID — identify the occurrence and its owning unit section, forming the primary linkage to the section offering.
• MONDAY_INDICATOR through SUNDAY_INDICATOR — one flag per weekday, indicating which days the meeting pattern applies.
• START_TIME / END_TIME — the daily meeting window.
• BUILDING_CODE / ROOM_CODE — the assigned meeting location.
• DEDICATED_BUILDING_CODE / DEDICATED_ROOM_CODE and PREFERRED_BUILDING_CODE / PREFERRED_ROOM_CODE — hard-dedicated versus preferred location assignments, with the region preference exposed via the decoded preferred region description.
• START_DATE / END_DATE — the effective date range of the meeting schedule.
• TO_BE_ANNOUNCED_INDICATOR / NO_SET_DAY_INDICATOR — flags for schedules whose details are not yet fixed.
• CANCEL_FLAG / ABORT_FLAG — indicate that the schedule was cancelled or aborted, the basis for filtering inactive meetings.
• Inst_notify / notify status / error text / STATUS_LAST_UPDATED — workflow notification and processing state.
• Scheduled status — the decoded schedule status meaning from IGS_LOOKUP_VALUES.

Common Use Cases and Queries

Typical usage centres on timetabling and occupancy reporting. To list all active meeting schedules for a section, filter the CANCEL_FLAG and ABORT_FLAG to exclude withdrawn occurrences:

• SELECT occurrence_identifier, unit_section_id, monday_indicator, wednesday_indicator, friday_indicator, start_time, end_time, building_code, room_code FROM igsbv_usec_meeting_schedules WHERE cancel_flag = 'N' AND abort_flag = 'N';
• Room utilization: aggregate by BUILDING_CODE and ROOM_CODE over a START_DATE/END_DATE window.
• Preference auditing: compare DEDICATED_* against PREFERRED_* columns where the decoded preferred region differs.
• Workflow monitoring: select rows where NOTIFY_STATUS or ERROR_TEXT is populated to identify scheduling notifications requiring attention.

Because the view is read-only and derives status text through embedded lookups, queries should treat it as a reporting convenience layer over IGS_PS_USEC_OCCURS_ALL.