Results for “award_body”

9 results




Overview
Explore in AI Chat

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

Overview

IGS_UC_FORM_QUALS is a table in the IGS (Student System) product schema of Oracle E-Business Suite, holding individual form qualifications imported from UCAS (Universities and Colleges Admissions Service). Each row represents a single qualification entry declared by an applicant on a UCAS application form, captured at the point of import into the EBS student records environment. The table is therefore a staging and reference repository for externally sourced admissions data rather than a transactional processing table, and it supports the visibility of applicant-declared academic achievement within the institution's admissions and student administration workflows.

From a Data Vault modeling perspective, the repository records a heuristic classification of standalone, reflecting that no foreign key relationships were mined from the physical schema. This classification is offered as a modeling suggestion: the table is best treated as an independent satellite-like structure keyed by applicant and qualification, with no enforced parent-child dependencies to other IGS objects at the database level.

Key Information Stored

The documented physical schema for ETRM 12.1.1 comprises twelve columns. The primary key is defined by the constraint IGS_UC_FORM_QUALS_PK, which is composed of the composite business key (APP_NO, QUAL_ID) rather than a single surrogate identifier — an important distinction when writing joins or de-duplication logic.

  • APP_NO — the UCAS application number; the first component of the composite primary key and the primary business-key candidate linking the qualification back to an applicant.
  • QUAL_ID — the qualification identifier; the second component of the composite primary key, uniquely distinguishing each qualification row within an application.
  • QUAL_TYPE — the classification or category of the qualification as reported on the UCAS form.
  • AWARD_BODY — the awarding or examining body responsible for the qualification.
  • TITLE — the descriptive title of the qualification as recorded on the imported form.
  • GRADE — the grade or result achieved for the qualification.
  • QUAL_DATE — the date associated with the qualification, typically the date of award or examination.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns tracking record creation and subsequent modification.

No unique indexes beyond the primary key constraint are documented in the available metadata. The composite key (APP_NO, QUAL_ID) is therefore the sole documented uniqueness guarantee.

Common Use Cases and Queries

Typical reporting scenarios center on admissions analysis: reviewing the qualifications declared by applicants, validating entry requirements, and reconciling imported UCAS data against institutional records. Because the table is standalone at the schema level, joins to applicant data are performed on the business key rather than a foreign key. For example, retrieving all qualifications for a given application:

  • SELECT app_no, qual_id, qual_type, award_body, title, grade, qual_date FROM igs.igs_uc_form_quals WHERE app_no = :application_number;
  • Aggregation by awarding body or qualification type to assess applicant cohorts: SELECT award_body, qual_type, COUNT(*) FROM igs.igs_uc_form_quals GROUP BY award_body, qual_type;
  • Grade distribution reporting for admissions selectivity analysis: SELECT qual_type, grade, COUNT(*) FROM igs.igs_uc_form_quals GROUP BY qual_type, grade ORDER BY qual_type;

Audit reconciliation queries are also common, using CREATION_DATE and LAST_UPDATE_DATE to identify recently imported or amended records.

Related Objects

The documented metadata states that the Data Vault classification is standalone and provides no foreign key relationships. Consequently, related objects must be inferred from the business key and the IGS/UCAS integration context rather than from enforced constraints. The most significant associations are:

  • UCAS application import tables (IGS_UC_* family) — sibling staging tables populated by the same import process, joined on APP_NO.
  • IGS_UC_FORM_CHOICES — holds the course choices associated with a UCAS application, joined on APP_NO.
  • IGS_UC_APPLICANTS / applicant staging objects — the parent applicant record, joined on APP_NO.
  • Student and admissions entities in the IGS schema — downstream records populated from imported UCAS data.

Because no FK constraints are documented, integrators should treat APP_NO as the governing join column and validate its consistency explicitly in any cross-object query.