Results for “term_4_end_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGSBV_UC_COURSE_DETAILS is a read-only base view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It exposes course detail records maintained for transmission to and from UCAS (the UK Universities and Colleges Admissions Service), presenting the intersection of UCAS course identifiers with the institution's own internal program structures. In Oracle EBS 12.1.1 and 12.2.2 the view carries a VALID status and serves as the reporting and integration layer over the UCAS Course Details table, allowing external extracts, data-loading programs, conformance reports, and ad-hoc queries to read validated course data without directly touching the underlying table. The view is defined with a WITH READ ONLY clause, so it cannot be used for DML; all maintenance is performed against the base table.

Underlying Base Objects

According to the ETRM documentation, the view text selects from a single base object: IGS_UC_CRSE_DETS, aliased as CR. No additional joined tables are documented. Every column in the view is a direct projection of a column in that base table, with aliasing applied to give business-friendly names. For example, CR.UCAS_PROGRAM_CODE is exposed as UCAS_COURSE_CODE, CR.OSS_PROGRAM_CODE as OSS_PROGRAM_CODE, and CR.OSS_LOCATION as OSS_LOCATION. Because the mapping is one-to-one, row counts and filtering behaviour of the view mirror the base table exactly, and any row-level security or indexing strategy applied to IGS_UC_CRSE_DETS governs access through the view.

Key Columns

• UCAS_COURSE_CODE (from UCAS_PROGRAM_CODE) – the UCAS-assigned course identifier used in admissions exchanges.
• OSS_PROGRAM_CODE / OSS_PROGRAM_VERSION – the internal Student System program code and version to which the UCAS course is mapped.
• OSS_LOCATION – the internal location code associated with the course; this is the column most relevant to searches for "oss_location", distinguishing the physical or administrative site at which the program is delivered.
• OSS_ATTENDANCE_TYPE / OSS_ATTENDANCE_MODE – internal attendance classification and mode of study.
• UCAS_INSTITUTE_CODE, UCAS_CAMPUS, UCAS_FACULTY – UCAS-side institution, campus and faculty identifiers.
• UCAS_COURSE_SHORT_TITLE / UCAS_COURSE_LONG_TITLE – the advertised course titles.
• TOTAL_NUMBER_OF_SEATS, MIN_ENTRY_POINTS, MAX_ENTRY_POINTS – capacity and entry requirement attributes.
• TERM_1_START_DATE through TERM_4_END_DATE – the four term start/end dates for the course.
• VACANCY_STATUS, NUMBER_OF_VACANCIES, CLEARING_UPDATED_FLAG, CLEARING_UPDATED_DATE, CLEARING_OPTIONS_FLAG – clearing and vacancy management data.
• CURRENT_VALIDITY, DEFERRED_VALIDITY, SENT_TO_UCAS_FLAG, IMPORTED_FLAG, KEYWORDS_CHANGED_FLAG – status and synchronisation flags.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – standard WHO audit columns.

Common Use Cases and Queries

Typical uses include UCAS submission extracts, reconciliation of internal programs against UCAS course codes, location-based reporting, and clearing/vacancy monitoring. A location-oriented query follows:

SELECT ucas_course_code, oss_program_code, oss_program_version, oss_location, oss_attendance_type, vacancy_status, number_of_vacancies FROM apps.igsbv_uc_course_details WHERE oss_location = :p_location AND current_validity = 'Y';

To identify courses not yet transmitted, filter on the flag: SELECT ucas_course_code, oss_program_code, oss_location FROM apps.igsbv_uc_course_details WHERE sent_to_ucas_flag = 'N'; Clearing reports can aggregate number_of_vacancies by oss_location and vacancy_status. Because the view is read-only and unfiltered, developers should always restrict results by program, location, or validity flag on large volumes.