Search Results ufi_place




Overview
Explore in AI Chat

Overview

The view IGSBV_UK_PRG_OFR_OPT_UNIT_SETS is a reporting and integration view within the Oracle E-Business Suite IGS – Student System product family. Its documented purpose is to serve as a Base View for Program Offering Option Unit Set HESA Details. HESA (the Higher Education Statistics Agency) is the statutory body responsible for the collection and publication of data about UK higher education providers; the view therefore exists to expose records that conform to HESA reporting requirements for programme offerings and the unit sets associated with them.

In the context of Oracle EBS 12.1.1 and 12.2.2, this view was historically used by customers operating the Student System module in a UK higher-education context, particularly where the institution recorded programme and unit-set data that had to be returned to HESA. The view functions as a denormalised, read-only projection over the underlying HESA programme-offering-option-unit-set entity, presenting columns using HESA-friendly aliases so that external extracts, regulatory reports, and integration interfaces can consume the data without needing to understand internal column naming.

It should be noted that the ETRM documentation marks IGS – Student System as Obsolete, and the view itself is documented as “Not implemented in this database.” Practically, this means the view exists in the data model and in historical releases but is not instantiated in every environment; availability depends on whether the HESA Student System extensions have been installed and the relevant database objects deployed.

Underlying Base Objects

The view text shows that it is defined over a single underlying object: IGS_HE_POOUS_ALL, aliased as POO. The naming convention is instructive: IGS_HE denotes the HESA-specific extension tables within the Student System schema, and POOUS corresponds to “Program Offering Option Unit Set.” The _ALL suffix indicates that the table carries a multi-organisation (multi-tenant within a single installation) column, and the view is CREATE ... WITH READ ONLY, confirming it is intended strictly for query and reporting workloads.

The ETRM metadata provided lists no documented referenced base objects, and no ownership is recorded. In practice, because the view selects directly from IGS_HE_POOUS_ALL, its row population, security, and validity are wholly inherited from that table. If IGS_HE_POOUS_ALL is absent or unpopulated in a given instance, the view either will not compile or will return no rows. There is no join, aggregation, or union in the definition; it is a straightforward column-aliasing projection.

Key Columns

The view exposes a broad set of attributes that map to HESA return fields. Significant columns include:

Common Use Cases and Queries

Typical usage centres on HESA extracts, franchise/delivery analysis, and reconciliation of programme offerings. All queries should include the organisation context where multi-org security applies, and should be filtered by reporting year where the population is large.

To isolate franchised provision, the FRANCHISING_ACTIVITY column is the principal filter:

SELECT PROGRAM_CODE,
       PROGRAM_VERSION_NUMBER,
       UNIT_SET_CODE,
       FRANCHISING_ACTIVITY,
       FUNDING_SOURCE,
       MODE_OF_STUDY
FROM   IGSBV_UK_PRG_OFR_OPT_UNIT_SETS
WHERE  FRANCHISING_ACTIVITY IS NOT NULL
ORDER BY PROGRAM_CODE, PROGRAM_VERSION_NUMBER;

A second common scenario is producing a HESA-oriented listing of all offerings with funding and credit detail:

SELECT HESA_POOUS_ID,
       PROGRAM_CODE,
       UNIT_SET_CODE,
       LEVEL_APP_TO_FUNDING_COUNCIL,
       FEE_BAND,
       YOP_CREDIT_VALUE_1,
       LEVEL_CREDIT_1
FROM   IGSBV_UK_PRG_OFR_OPT_UNIT_SETS
WHERE  FUNDABILITY_CD = :fundability_code;

A third use is reconciliation against the base table to confirm the view returns the expected population, since the view is a direct projection:

SELECT COUNT(*) FROM IGSBV_UK_PRG_OFR_OPT_UNIT_SETS;
SELECT COUNT(*) FROM IGS_HE_POOUS_ALL;

Because the view is read-only and unaggregated, it is safe for ad-hoc reporting, BI Publisher data templates, and custom HESA extract programs. Where the view is not implemented, equivalent output must be sourced directly from IGS_HE_POOUS_ALL with the same column aliases applied in the client extract.