Search Results uso_end_date

Overview

IGS_PS_USEC_OCCURS_FULL_V is a reporting view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It presents a consolidated, denormalized picture of unit section occurrences — the individual scheduled meetings that make up a teachable unit section (class) in an academic calendar. In ETRM terms, the view joins occurrence scheduling records with unit section version data, building and room lookups, and a schedule status lookup so that a single row carries the section identity, calendar dates, day-of-week pattern, time-of-day, location, and scheduling status.

Its role is primarily read-only reporting and integration. Functional users and developers query it for timetable and room-utilization reporting, enrollment-related extracts, and downstream integrations (for example, publishing class schedules to a portal or a third-party calendar). Because the view exposes APPS-owned base tables and pre-resolves lookups such as building/room descriptions and the schedule status meaning, it removes much of the join complexity that a direct query against the underlying IGS tables would require.

Underlying Base Objects

The documented view text references the following aliased sources, all resolved through the APPS schema:

• USO — the unit section occurrence table (IGS_PS_USEC_OCCURS), supplying occurrence-level scheduling attributes including the day flags, START_DATE/END_DATE, START_TIME/END_TIME, BUILDING_CODE, ROOM_CODE, INSTRUCTOR_ID, SCHEDULE_STATUS, TO_BE_ANNOUNCED, ERROR_TEXT, and the ATTRIBUTE1 through ATTRIBUTE18 descriptive flexfield columns.
• UOOV — the unit section occurrence version source, supplying unit identity and descriptive attributes: UNIT_CD, VERSION_NUMBER, US_STATUS_DESC, UNIT_SECTION_STATUS, TITLE, CALL_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER, ALTERNATE_CODE, CAL_START_DT, CAL_END_DT, UNIT_CLASS, UNIT_MODE, LOCATION_CD, LOCATION_DESCRIPTION, and the section start/end dates.
• BLD — the building lookup, joined on BUILDING_CODE to return BUILDING_DESCRIPTION.
• ROM — the room lookup, joined on ROOM_CODE to return ROOM_DESCRIPTION.
• LKUP — the schedule status lookup, joined on SCHEDULE_STATUS to return MEANING as SCHEDULE_STATUS_DESC.

The view is therefore a five-way join pivoting on the occurrence row, with USO as the driving table. The SURNAME and PERSON_NUMBER columns are returned as hard-coded NULL values, indicating that instructor name resolution is not performed within this view.

Key Columns

• UNIT_SECTION_OCCURRENCE_ID / UOO_ID — primary identifiers for the occurrence record.
• UNIT_CD, VERSION_NUMBER, CALL_NUMBER — locate the parent unit section and its catalog call number.
• CAL_TYPE — the calendar type, distinguishing teaching periods such as standard terms from exam or other calendars.
• MONDAY … SUNDAY — day-of-week flags indicating the recurring meeting pattern of the occurrence.
• USO_START_DATE / USO_END_DATE and START_TIME / END_TIME — the effective date range and daily time window of the occurrence.
• BUILDING_CODE / BUILDING_DESCRIPTION and ROOM_CODE / ROOM_DESCRIPTION — resolved physical location.
• SCHEDULE_STATUS and SCHEDULE_STATUS_DESC — the schedule state code and its lookup meaning. Because the user search term was schedule_type, note that this view does not expose a column literally named SCHEDULE_TYPE — the closest scheduling classification columns are SCHEDULE_STATUS (with its description) and CAL_TYPE.
• INSTRUCTOR_ID, TO_BE_ANNOUNCED, ERROR_TEXT — assignment and scheduling-exception indicators.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–18 — descriptive flexfield storage carried from the occurrence table.

Common Use Cases and Queries

Typical scenarios include producing a weekly timetable for a calendar, checking room bookings and clashes, and auditing occurrences awaiting a schedule status change.

• List scheduled occurrences for a calendar type with location detail:

SELECT unit_cd, call_number, cal_type, cal_start_dt, cal_end_dt,
       uso_start_date, uso_end_date, start_time, end_time,
       building_description, room_description, schedule_status_desc
FROM   apps.igs_ps_usec_occurs_full_v
WHERE  cal_type = :p_cal_type
AND    schedule_status_desc IS NOT NULL;

• Find Monday occurrences not yet scheduled (announced but unplaced):

SELECT unit_cd, title, call_number, instructor_id, error_text
FROM   apps.igs_ps_usec_occurs_full_v
WHERE  monday = 'Y'
AND    to_be_announced = 'Y'
AND    usuario_start_date >= TRUNC(SYSDATE);

• Room utilization within a date range:

SELECT building_code, room_code, COUNT(*) occurrences
FROM   apps.igs_ps_usec_occurs_full_v
WHERE  uso_start_date BETWEEN :p_from AND :p_to
GROUP  BY building_code, room_code
ORDER  BY occurrences DESC;

Queries should generally filter by calendar or date range, as the view returns all occurrence rows in the APPS schema and can be large in production.