Search Results notify_status

Overview

The view IGS_PS_USEC_OCCURS belongs to the IGS (Student System) product family within Oracle E-Business Suite. It exposes scheduling occurrence data for unit section occurrences — that is, the concrete meeting pattern of a scheduled class section, including which days of the week it meets, its start and end times, and the physical or preferred location at which it is held. In ETRM documentation for release 12.2.2 the view is flagged under the "IGS - Student System (Obsolete)" classification and is recorded as "Not implemented in this database." This means the definition is retained for historical and referential purposes but the object is not deployed in a standard 12.2.2 instance. The same obsolescence caveat applies to 12.1.1, where IGS scheduling functionality had already been de-emphasised in favour of successor student-system architectures.

Despite its obsolete status, the view remains relevant to organisations that have retained legacy IGS data, or that are migrating records out of IGS into a replacement scheduling or student-records platform. Its primary role is reporting and integration: it flattens the occurrence header and its scheduling attributes into a single queryable row.

Underlying Base Objects

The view text is defined as a straightforward projection over a single base table, aliased USO. Based on the column set and the IGS naming convention, this is the unit section occurrence table that stores one record per scheduled occurrence of a unit section. No joins, aggregations, or sub-queries are present in the documented view text, so the relationship between view and base object is one-to-one by row. The view inherits the ROWID of the base row as ROW_ID, which preserves the ability to reference the underlying record for updates performed through the view where such DML is permitted.

Because ETRM lists no additional referenced base objects, the view should be treated as a denormalised access layer over that single occurrence table rather than as a joined reporting construct. Organisations still running IGS will typically query it directly against the occurrence table, while those on pure 12.2.2 instances will find it absent and must rely on the legacy table definition for historical extraction.

Key Columns

• UNIT_SECTION_OCCURRENCE_ID and UOO_ID — surrogate and occurrence identifiers that uniquely tie a row to a specific unit section occurrence.
• MONDAY through SUNDAY — day-of-week flags describing the recurrence pattern of the meeting.
• START_TIME and END_TIME — the daily meeting window.
• START_DATE and END_DATE — the effective date range over which the occurrence applies.
• BUILDING_CODE and ROOM_CODE — the actual assigned location, duplicated as SCHEDULED_BUILDING_CODE and SCHEDULED_ROOM_CODE.
• DEDICATED_* and PREFERRED_* — location preferences and dedicated allocations used during scheduling algorithms.
• SCHEDULE_STATUS and STATUS_LAST_UPDATED — the scheduling lifecycle state and its timestamp.
• INSTRUCTOR_ID — the assigned instructor for the occurrence.
• TO_BE_ANNOUNCED and INST_NOTIFY_IND — flags indicating an unconfirmed location and instructor notification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the standard EBS descriptive flexfield segment set.
• ORG_ID — the multi-org operating unit context.
• Audit/concurrent columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, ERROR_TEXT, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include producing timetable and room-utilisation reports, validating that no two occurrences of the same section overlap in time, and exporting occurrence data during migration away from IGS. The following query retrieves the weekly meeting pattern for a given unit section occurrence:

SELECT uso.row_id,
       uso.unit_section_occurrence_id,
       uso.start_date,
       uso.end_date,
       uso.start_time,
       uso.end_time,
       uso.monday, uso.tuesday, uso.wednesday,
       uso.thursday, uso.friday, uso.saturday, uso.sunday,
       uso.building_code,
       uso.room_code,
       uso.instructor_id,
       uso.schedule_status
FROM   igs_ps_usec_occurs uso
WHERE  uso.unit_section_occurrence_id = :occurrence_id
ORDER  BY uso.start_date, uso.start_time;

A room-utilisation extract over a date range can be built by filtering on BUILDING_CODE and ROOM_CODE together with the START_DATE/END_DATE bounds, while an instructor load report would group by INSTRUCTOR_ID and sum the scheduled duration derived from START_TIME and END_TIME. Because the object is documented as not implemented in 12.2.2, any query against it on that release will fail with an object-not-found error; such statements are valid only against environments where the legacy IGS schema has been preserved.