Search Results new_he_entrant_code




Overview
Explore in AI Chat

Overview

The view APPS.IGSBV_ST_UNIT_SET_ATT_HESA_DET is a base business view within the Oracle E-Business Suite Student System (IGS) product family. It exposes Student Unit Set Attempt HESA (Higher Education Statistics Agency) detail records, providing a consolidated, query-ready representation of the statutory data elements that UK higher education institutions must report to HESA. In Oracle EBS 12.1.1 and 12.2.2, this view functions as an abstraction layer over the underlying attempt-level storage, allowing reporting tools, extracts, and integration interfaces to retrieve HESA-relevant attributes without directly joining the constituent base tables.

The view carries the IGSBV_ prefix, the naming convention Oracle reserves for base views in the Student System. Such views are commonly referenced by Oracle-delivered concurrent programs, OBIEE/XML Publisher reports, and custom extract routines used for statutory returns. Because HESA returns are period-driven and reconciliation-sensitive, the view is intended to present a stable column set that maps internal codes to recognizable HESA field semantics.

Underlying Base Objects

The ETRM metadata for this object does not document explicit referenced base objects. The view text, however, derives its columns from a Student Unit Set Attempt source (aliased SUSA) joined to the person/party table (aliased PER) to expose PERSON_NUMBER from PARTY_NUMBER. The SUSA prefix corresponds to the Student Unit Set Attempt entity that holds the HESA detail attributes, keyed in part by HESA_EN_SUSA_ID and PERSON_ID.

In the broader IGS data model, Student Unit Set Attempt records link a student's enrolment to the specific unit sets attempted in a period, with module/unit occurrences and versions resolved through related tables. The view flattens these attempt-level attributes into a single row per attempt, joining to the party table purely to surface the human-readable person number rather than the internal PERSON_ID.

Key Columns

Common Use Cases and Queries

Typical use is HESA return preparation, credit achievement reconciliation, and funding analysis. A representative query filters by person or programme:

SELECT PERSON_NUMBER, PROGRAM_CODE, UNIT_SET_CODE,
       CREDIT_LEVEL_ACHIEVED1, CREDIT_LEVEL_ACHIEVED2,
       CREDIT_PTS_ACHIEVED1, CALCULATED_FTE, FTE_INTENSITY
FROM   APPS.IGSBV_ST_UNIT_SET_ATT_HESA_DET
WHERE  PERSON_NUMBER = :p_person_number;

For credit-level analysis across attempts, aggregate the achieved credit columns grouped by programme and level. Analysts searching for credit_level_achieved4 should note that the documented excerpt exposes achieved credit levels for the first and second positions (CREDIT_LEVEL_ACHIEVED1, CREDIT_LEVEL_ACHIEVED2); where a fourth achieved level is required, the column set continues in the truncated portion of the view definition and should be validated directly against the deployed view in the target instance using ALL_VIEWS / DBA_VIEWS.