Search Results teaching_qual_sought_sector




Overview
Explore in AI Chat

Overview

IGS_HE_ST_PROG is a reporting view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product. It exposes Higher Education Statistics Agency (HESA) program-level data held within the institution's student records, presenting the columns required for the statutory HESA returns that UK higher education institutions submit annually. HESA returns drive funding allocations, regulatory reporting and published performance statistics, so the accuracy and traceability of the data surfaced by this view is of direct operational significance.

Functionally, the view acts as a filtered presentation layer over the underlying transactional table. It is not a stored object in its own right; it is defined by SQL that selects from IGS_HE_ST_PROG_ALL and applies a multi-tenant filter based on the operating unit (ORG_ID) derived from the session's CLIENT_INFO. In Oracle EBS 12.1.1 and 12.2.2 this pattern is the standard mechanism by which multi-org secured tables are surfaced to reports, concurrent programs and integration extracts without the caller needing to know the ORG_ID explicitly. The view's status is documented as VALID, indicating it compiles cleanly against the referenced object.

Underlying Base Objects

The documented view text references a single base object: IGS_HE_ST_PROG_ALL, the HESA program details table. The "_ALL" suffix is the conventional EBS multi-org naming pattern denoting a table that stores rows for all operating units, with each row carrying an ORG_ID. IGS_HE_ST_PROG therefore represents the operating-unit-specific slice of that table, resolving only those rows whose ORG_ID matches the operating unit associated with the current session.

The filter is implemented through a DECODE on the first ten characters of USERENV('CLIENT_INFO'). When CLIENT_INFO is blank, the expression evaluates to NULL and the predicate compares NULL to NULL; when an ORG_ID is present it is extracted and matched against the row's ORG_ID. The ROWID of the base table row is also exposed as ROW_ID, providing a stable handle for the underlying physical record. No further base tables, lookups or describing views are documented as referenced objects, so the view is essentially a secured projection of a single table.

Key Columns

Common Use Cases and Queries

Typical usage is in concurrent programs, BI Publisher reports and extracts that must reflect only the current operating unit's HESA programme data. A representative query is:

SELECT course_cd, version_number, fee_band, fundability, teach_period_start_dt FROM igs_he_st_prog WHERE fundability = 'Y';

Because the ORG_ID predicate is embedded in the view definition, such queries automatically respect whatever operating unit context the session carries, removing the need for callers to add their own multi-org filter. Developers integrating with the view should nevertheless be aware that in a session without a populated CLIENT_INFO the filter resolves to NULL, potentially returning all accessible rows rather than a single organisation's.