Search Results admission_application_number




Overview
Explore in AI Chat

Overview

The view IGSBV_ST_HESA_ADMISSION_DETAIL is a base business view within the Oracle E-Business Suite IGS – Student System product family, which is documented as obsolete in release 12.1.1 and 12.2.2. Its stated purpose is to expose Student Admission Application HESA (Higher Education Statistics Agency) detail records for query and reporting purposes. The view functions as a read-only presentation layer over the underlying HESA admission detail table, joining party information to provide a denormalized, human-readable result set suitable for institutional reporting, regulatory extracts, and integration with external statutory returns.

Because it is defined with the WITH READ ONLY clause, the view is strictly a query construct; DML operations are not permitted. This design reinforces its role as a reporting and information-retrieval object rather than a transactional one. In the metadata, the view is flagged as not implemented in this database, indicating that it belongs to the deprecated or optional IGS schema and may not be present in every EBS installation.

Underlying Base Objects

According to the documented view text, the object is defined over two base objects:

  • IGS_HE_AD_DTL_ALL — the HESA Admission Detail entity, aliased as HAD. This table supplies all HESA-specific admission attributes such as nominated course, occupation, domicile, social class, and special student code.
  • HZ_PARTIES — the Trading Community Architecture (TCA) party master, aliased as PER. This supplies the party number used to identify the person associated with the admission detail.

The join condition is PER.PARTY_ID = HAD.PERSON_ID, linking the admission record to its corresponding party record. No other base objects are documented as referenced. The view documentation does not list an owner schema, and the referenced base objects entry is recorded as "none documented," so table-level dependencies should be confirmed against the actual database implementation where the view exists.

Key Columns

Common Use Cases and Queries

Typical usage involves extracting HESA admission detail for statutory returns, validating special student classifications, and reporting applicant demographic attributes. A representative query targeting the searched attribute is:

  • SELECT PERSON_NUMBER, ADMISSION_APPLICATION_NUMBER, NOMINATED_PROGRAM_CODE, SPECIAL_STUDENT_CODE FROM IGSBV_ST_HESA_ADMISSION_DETAIL WHERE SPECIAL_STUDENT_CODE IS NOT NULL;
  • Filtering by domicile or social class for equality and widening-participation reporting.
  • Joining to other IGS student views on PERSON_ID to enrich admission records with enrollment or progression data.

Given the obsolete status, new development should migrate to supported student records structures; the view remains useful only for legacy reporting and historical reconciliation.