Search Results oss_person_identifier




Overview
Explore in AI Chat

Overview

The IGSBV_UC_FORM_QUALIFICATIONS view is a base database view owned by the APPS schema within the Oracle E-Business Suite (EBS) IGS – Student System product family. In EBS 12.1.1 and 12.2.2, this view serves as the reporting and integration abstraction layer for individual qualifications recorded against UCAS (Universities and Colleges Admissions Service) application forms. UCAS is the United Kingdom's centralized admissions service, and the IGS Student System stores data captured through that admissions channel.

The view is classified as a "base view" (denoted by the IGSBV prefix), meaning it is intended primarily as an internal foundation upon which other views, forms, or integrations are built, rather than as an end-user-facing object. Because it is defined WITH READ ONLY, it enforces a strict read-only contract — no DML is permitted through the view — making it safe for downstream reporting, data extraction, and interface consumption. When the user searched for qualification_identifier, they were seeking the UCAS-side identifier that uniquely distinguishes each qualification record tied to an applicant.

Underlying Base Objects

Although the documented metadata lists no referenced base objects, the view text explicitly reveals its definition. The view is constructed over two underlying tables in the APPS schema:

  • IGS_UC_FORM_QUALS (aliased FO) – the driving table holding the individual qualification records, including type, awarding body, title, grade, and qualification date.
  • IGS_UC_APPLICANTS (aliased FT1) – the applicant header table, joined to provide the OSS person identifier.

The join is a simple equi-join on the UCAS application number: FO.APP_NO = FT1.APP_NO. This correlates each qualification row to its owning applicant, enabling the view to expose both form-level and person-level context in a single result set. Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) are carried through directly from the qualification table for traceability.

Key Columns

  • UCAS_APPLICANT_NUMBER – the UCAS application reference (FO.APP_NO), the join key to the applicant table.
  • QUALIFICATION_IDENTIFIER – the unique identifier of the qualification record (FO.QUAL_ID). This is the object of the user's search term and is the primary positional key within the qualification set.
  • QUALIFICATION_TYPE – categorizes the qualification (e.g., A-Level, GCSE, degree).
  • AWARDING_BODY – the institution or examination board granting the qualification.
  • TITLE – the descriptive name/subject of the qualification.
  • GRADE – the achieved grade or result.
  • QUALIFICATION_DATE – the date the qualification was awarded (FO.QUAL_DATE).
  • OSS_PERSON_IDENTIFIER – the internal person identifier from the applicant record, linking UCAS data to the institutional student record.
  • CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE – standard audit columns.

Common Use Cases and Queries

Typical scenarios include admissions reporting, data quality audits, and integration extracts feeding student records. A representative query retrieves a specific qualification by its identifier:

  • SELECT UCAS_APPLICANT_NUMBER, QUALIFICATION_IDENTIFIER, QUALIFICATION_TYPE, AWARDING_BODY, TITLE, GRADE, QUALIFICATION_DATE FROM APPS.IGSBV_UC_FORM_QUALIFICATIONS WHERE QUALIFICATION_IDENTIFIER = :qual_id;
  • Joining to IGS_UC_APPLICANTS for applicant demographics, or to OSS person tables via OSS_PERSON_IDENTIFIER, to reconcile UCAS qualifications against enrolled student records.
  • Grade-distribution and awarding-body analyses for cohort reporting, filtering by QUALIFICATION_DATE.

The read-only nature guarantees that such reporting cannot inadvertently mutate admissions data.