Results for “ucas_applicant_number”

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

Overview

IGSBV_UC_APPLICANT_STATISTICS is a base database view belonging to the IGS — Student System product family in Oracle E-Business Suite. Its stated purpose is to expose applicant statistical data required for HESA (Higher Education Statistics Agency) reporting. In the UK higher education sector, HESA returns require institutions to submit standardized demographic, socio-economic, and background attributes for each applicant and student. This view serves as a consolidated source for those attributes as captured at the UCAS application stage.

The view is documented in ETRM 12.2.2 with the note "Not implemented in this database," indicating that the object is defined in the application data model but may not be deployed in every environment. In Oracle EBS 12.1.1 and 12.2.2, IGS objects are part of the obsolete Student System module, which was progressively superseded by Oracle Student Cloud. The view nonetheless remains referenced in legacy reporting and HESA extract logic where historical data must be retrieved.

Because it is a view rather than a table, it stores no data of its own. It presents a read-only projection of applicant statistics, declared with the WITH READ ONLY clause, which prevents DML operations and enforces its use strictly as a query and reporting interface.

Underlying Base Objects

The view is defined over a single base table, IGS_UC_APP_STATS, aliased as AP in the view text. No other tables, joins, or subqueries appear in the definition, so the view is a straightforward column-level projection and rename of that table. ETRM documents no referenced base objects beyond this, and the implementation metadata reiterates that the object is not implemented in the reference database.

The dependency is therefore one-to-one: every row and every queried column in IGSBV_UC_APPLICANT_STATISTICS originates from IGS_UC_APP_STATS. Filtering, aggregation, or joining with related applicant, person, or programme tables must be performed by the calling query, since the view adds no relational logic of its own.

Key Columns

The view exposes 28 columns. The naming convention prefixes many HESA-specific attributes with IVSTARH_ or IVSTARX_, reflecting the HESA field identifiers used for applicant statistical returns.

• APPLICANT_STAT_IDENTIFIER — Primary key of the underlying statistics record, sourced from AP.APP_STAT_ID.
• UCAS_APPLICANT_NUMBER — The UCAS applicant number (AP.APP_NO), the external identifier used to correlate with UCAS data.
• APPLICANT_IDENTIFIER — Internal applicant identifier (AP.APP_ID), generally the join key to the wider applicant model. This column is directly relevant to searches on "applicant_identifier".
• IVSTARH_ / IVSTARX_ attribute pairs — Ethnic code, social class, POCC (parental occupation classification) code and text, POCC education change date, last education institution, education leave date, LEA, socio-economic code, dependants, married status, occupational background, and religion.
• SENT_TO_HESA — Flag indicating whether the record has been transmitted to HESA.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical usage centers on HESA submission preparation, applicant demographic analysis, and reconciliation between internal applicant records and UCAS identifiers. A common query resolves an applicant through the internal identifier and inspects whether the statistical record has been sent:

• Retrieve all statistics for a known applicant: SELECT * FROM IGSBV_UC_APPLICANT_STATISTICS WHERE APPLICANT_IDENTIFIER = :p_app_id;
• Identify records pending HESA transmission: SELECT APPLICANT_IDENTIFIER, UCAS_APPLICANT_NUMBER FROM IGSBV_UC_APPLICANT_STATISTICS WHERE SENT_TO_HESA = 'N';
• Audit recent changes: SELECT APPLICANT_STATISTICS_IDENTIFIER, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM IGSBV_UC_APPLICANT_STATISTICS WHERE LAST_UPDATE_DATE >= :p_since;
• Report demographic breakdowns by joining APPLICANT_IDENTIFIER to applicant and person tables for institution-level HESA returns.

Because the view is read-only and single-table, performance depends almost entirely on indexes and constraints defined on IGS_UC_APP_STATS. Queries should filter on APPLICANT_IDENTIFIER, UCAS_APPLICANT_NUMBER, or SENT_TO_HESA to avoid full scans on large applicant populations.