Results for “applicant_ucas_number”

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

Overview

IGSBV_UC_APPLICANT_CHOICES is a base view owned by the APPS schema in the Oracle E-Business Suite IGS (Student System) product. It is registered in ETRM as a VALID database view with the description "Base View for Applicant Choices." Its purpose is to present a flattened, business-friendly projection of university applicant choice records, primarily those originating from the UCAS (Universities and Colleges Admissions Service) admissions interface. An applicant "choice" represents a single course-and-institution selection made by an applicant during an admissions cycle.

The view sits at the reporting and integration layer of the Student System. Downstream functions — including admissions review, decision tracking, offer management, and exporting records to the OSS (Online Student System) via the UCAS interface — consume this view rather than querying the underlying staging columns directly. Because it exposes both UCAS-specific attributes and OSS-facing equivalents side by side, it functions as a convenient single source for reconciliation and status reporting.

Underlying Base Objects

The documented view text is a straightforward SELECT with only column aliasing, no joins. Every field is sourced from a single alias, AP, whose real table name is not exposed by the excerpted metadata, but which holds the raw applicant-choice staging columns. ETRM lists no referenced base objects, meaning the dependency is implied through the column mapping rather than formally enumerated in the metadata. In practice, the AP alias corresponds to the applicant choices staging table used by the UCAS import programs, and all exported fields come from that one relation. No aggregation, filtering, or outer joins are applied, so the view returns one row per applicant choice record exactly as stored.

Key Columns

• APPLICANT_CHOICE_ID — renamed from APP_CHOICE_ID; the unique identifier for the choice line.
• APPLICANT_ID — renamed from APP_ID; the applicant identifier and the term the user searched for. It links each choice back to its owning applicant.
• APPLICANT_UCAS_NUMBER (APP_NO) and APPLICANT_CHOICE_NUMBER (CHOICE_NO) — the UCAS applicant and choice sequence numbers.
• UCAS_CYCLE, UCAS_INSTITUTE_CODE, UCAS_PROGRAM_CODE, OSS_PROGRAM_CODE, OSS_PROGRAM_VERSION — cycle and program identification, giving both UCAS and OSS representations.
• UCAS_CAMPUS, OSS_LOCATION, UCAS_FACULTY, ENTRY_YEAR, ENTRY_MONTH, POINT_OF_ENTRY — delivery location and entry details.
• DECISION, DECISION_DATE, DECISION_NUMBER, REPLY, CONDITION_CATEGORY, CONDITION_CODE, SUMMARY_OF_CONDITIONS — admissions decision and offer-condition tracking.
• OFFERED_COURSE, OFFERED_CAMPUS, OFFERED_ENTRY_YEAR/MONTH/POINT, OFFERED_TEXT — the offer issued to the applicant.
• EXPORT_TO_OSS_STATUS, EXPORT_PROCESS_ERROR_CODE, ADM_IMPORT_PROCESS_BATCH_ID — interface control fields indicating whether the choice has been exported and any resulting error.
• CHOICE_CANCELLED_FLAG, HOME_FLAG, DEFERRED_FLAG, WITHDRAWAL_REASON — status flags and withdrawal information.

Common Use Cases and Queries

Typical uses include extracting all choices for a given applicant, monitoring failed UCAS-to-OSS exports, and producing admissions-cycle reports.

SELECT APPLICANT_ID, APPLICANT_CHOICE_ID, APPLICANT_UCAS_NUMBER,
       OSS_PROGRAM_CODE, DECISION, DECISION_DATE, EXPORT_TO_OSS_STATUS
FROM   APPS.IGSBV_UC_APPLICANT_CHOICES
WHERE  APPLICANT_ID = :p_applicant_id;

SELECT APPLICANT_UCAS_NUMBER, APPLICANT_CHOICE_NUMBER,
       EXPORT_PROCESS_ERROR_CODE, ADM_IMPORT_PROCESS_BATCH_ID
FROM   APPS.IGSBV_UC_APPLICANT_CHOICES
WHERE  EXPORT_TO_OSS_STATUS = 'E';

Because the view is unfiltered, callers should supply their own predicates on APPLICANT_ID, UCAS_CYCLE, or the export status columns to limit result sets. It is also suitable as a reporting source joined to applicant and program tables on APPLICANT_ID and OSS_PROGRAM_CODE respectively.