Search Results class_day

Overview

IGS_SS_USEC_OCCURENCES_V is a Self-Service Web view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IGS.IGS_SS_USEC_OCCURENCES_V. It is classified as a Web view "designed to simplify access from Oracle Self-Service Web Applications," and its documented purpose is to store Unit Section Occurrences — that is, the scheduled meetings that make up a teaching unit section within the Student System (IGS) product family.

The view exposes scheduling detail for occurrences of unit section offerings, including the day, time, physical venue, and assigned instructor for each occurrence, together with the occurrence's validity window (START_DATE and END_DATE). Because it is a Self-Service Web view, it is intended to be queried directly by web-based reporting and integration consumers rather than being maintained as a base table in its own right. The view carries a VALID status in the ETRM repository. No dependent database objects are documented, so it is a terminal (read-only) reporting object with no downstream database dependencies.

Underlying Base Objects

The view is defined over the following documented base objects:

• IGS_PS_USEC_OCCURS — the core table of unit section occurrence records, supplying UNIT_SECTION_OCCURRENCE_ID, UOO_ID, CLASS_DAY, CLASS_TIME, START_DATE, and END_DATE.
• IGS_AD_LOCATION — the location reference table, supplying LOCATION_CD and LOCATION_DESCRIPTION.
• IGS_AD_BUILDING — the building reference table, supplying BUILDING_ID, BUILDING_CD, and BUILDING_DESCRIPTION.
• IGS_AD_ROOM — the room reference table, supplying ROOM_ID, ROOM_CD, and ROOM_DESCRIPTION.
• HZ_PARTIES — the Trading Community Architecture party table, supplying the instructor's surname, given names, and person title, which the view concatenates into INSTRUCTOR_NAME.

The view therefore denormalises the scheduling record on IGS_PS_USEC_OCCURS by resolving location, building, and room identifiers into their descriptive attributes, and by resolving the instructor party identifier into a human-readable name. Note that the view is not referenced by any database object, confirming it is a leaf-level reporting construct.

Key Columns

• UNIT_SECTION_OCCURRENCE_ID (NUMBER, 10) — primary identifier for the unit section occurrence.
• UOO_ID (NUMBER) — identifier of the parent Unit Offering Option to which the occurrence belongs.
• CLASS_DAY (VARCHAR2, 21) — the day on which the class occurrence is scheduled.
• CLASS_TIME (VARCHAR2, 15) — the scheduled class time, exposed as a character string rather than a date or timestamp. This is the column most commonly surfaced in timetable and class-schedule queries.
• LOCATION_CD / LOCATION_DESCRIPTION — the location code and its description.
• BUILDING_ID / BUILDING_CD / BUILDING_DESCRIPTION — building identifier, code, and description for the venue.
• ROOM_ID / ROOM_CD / ROOM_DESCRIPTION — room identifier, code, and description within the building.
• INSTRUCTOR_ID (NUMBER, 15) — party identifier of the assigned instructor.
• SURNAME / GIVEN_NAMES / PERSON_TITLE / INSTRUCTOR_NAME — name components and the formatted instructor name (length 365).
• START_DATE / END_DATE — the effective date range of the occurrence.

Common Use Cases and Queries

Typical consumers include self-service timetable pages, class-schedule reports, and interfaces that publish teaching schedules. A search on class_time maps directly to the CLASS_TIME column, so the most frequent query pattern filters or orders by that column.

To retrieve all occurrences for a given day, ordered by start time:

SELECT UOO_ID, CLASS_DAY, CLASS_TIME, ROOM_CD,
       BUILDING_CD, INSTRUCTOR_NAME, START_DATE, END_DATE
FROM   APPS.IGS_SS_USEC_OCCURENCES_V
WHERE  CLASS_DAY = :p_day
ORDER BY CLASS_TIME;

To list occurrences at a specific venue:

SELECT UNIT_SECTION_OCCURRENCE_ID, CLASS_DAY, CLASS_TIME,
       LOCATION_DESCRIPTION, BUILDING_DESCRIPTION, ROOM_DESCRIPTION
FROM   APPS.IGS_SS_USEC_OCCURENCES_V
WHERE  BUILDING_CD = :p_building
AND    ROOM_CD     = :p_room;

To find all occurrences assigned to an instructor within a date window:

SELECT UOO_ID, CLASS_DAY, CLASS_TIME, ROOM_CD,
       START_DATE, END_DATE
FROM   APPS.IGS_SS_USEC_OCCURENCES_V
WHERE  INSTRUCTOR_ID = :p_person_id
AND    :p_eff_date BETWEEN START_DATE AND END_DATE;

Because CLASS_TIME is stored as VARCHAR2, lexical comparisons on that column are only reliable when the stored format is consistently zero-padded; date-window filtering should always use START_DATE and END_DATE, which are true DATE columns.