Results for “sent_to_ucas_flag”

17 results




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

Overview

IGSFV_UC_COURSE_DETAILS is an Oracle EBS 12.1.1 / 12.2.2 view owned by the APPS schema within the IGS – Student System product (also referred to as Oracle Student System, or OSS). It is described in the ETRM metadata as the "Full View for UCAS Course Details Table." UCAS (Universities and Colleges Admissions Service) is the UK central admissions body, and this view consolidates the institution's course data in the form used for UCAS submission and reporting. The view joins UCAS course records with program, system, and lookup descriptors so that a single query returns both the identifier values held on the course record and the human-readable descriptions required by UCAS returns.

The view's status is VALID, confirming it is compiled and usable, and its naming convention (IGSFV_ prefix) is typical of the IGS "full view" family, which exposes the entire column list of the underlying entity. It functions primarily as a reporting and integration layer rather than a data-entry object; the base tables hold the authoritative data, and the view presents a denormalised projection for extraction, validation, and UCAS file generation.

Underlying Base Objects

The ETRM metadata lists no referenced base objects for this view, but the documented view text reveals the aliases used in its SELECT statement: CR, DE, CO, VE, TY, and MO. These follow standard Student System table alias conventions, where CR denotes the UCAS course details table (APPS.IGS_UC_CRS_DTLS), CO the UCAS institution table, DE the UCAS system definition table, VE the program version table (IGS_PS_VER), and TY and MO the UCAS/system lookup tables supplying the attendance type and attendance mode descriptions respectively. The view reads these tables in a single join, so all exposed columns are derived directly from the base tables with no aggregation. Because the join is not documented in the ETRM excerpt, consumers should treat the underlying table names as inferred from the column aliases and from standard Student System data modelling rather than as formally documented fact.

Key Columns

Common Use Cases and Queries

The view is typically used to produce UCAS extracts, to reconcile internal program definitions against UCAS codes, and to verify that the correct OSS_PROGRAM_SHORT_TITLE is aligned with each UCAS course before submission.

SELECT ucas_course_code,
       oss_program_code,
       oss_program_short_title,
       ucas_course_short_title,
       vacancy_status,
       number_of_vacancies
FROM   apps.igsfv_uc_course_details
WHERE  sent_to_ucas_flag = 'Y'
ORDER  BY ucas_course_code;

A second common pattern retrieves clearing-relevant courses by their vacancy status and description:

SELECT ucas_course_code,
       oss_program_short_title,
       clearing_options_flag,
       number_of_vacancies,
       oss_attendance_mode_desc
FROM   apps.igsfv_uc_course_details
WHERE  clearing_options_flag = 'Y'
AND    number_of_vacancies > 0;

Because the view applies no filters, all course records are returned; callers should always constrain on the relevant status or code columns when building UCAS extracts or reconciliation reports.