Results for “unit_set_code”

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

Overview

IGSBV_UK_PRG_OFR_OPT_ORG_UNITS is a United Kingdom Higher Education Statistics Agency (HESA) reporting base view belonging to the IGS (Student System) product family. In Oracle EBS 12.1.1 and 12.2.2, the IGS module is documented by ETRM as obsolete; nevertheless the object remains catalogued because existing installations that were upgraded from earlier releases may still carry the underlying schema and its dependent views. The view exposes organization unit allocation data for a program offering option unit set — that is, the distribution of a unit set across the organizational units that deliver or own it, expressed as a proportion of the total.

The view is read-only by construction. Its definition terminates in a WITH READ ONLY clause, which guarantees that no DML can be issued against it and that consumers such as HESA returns, extracts, and integration interfaces treat it purely as a projection of stored data. The view presents no derived or calculated values; every column is a straight pass-through of a column in the base table, with several columns renamed to a more readable English form.

Underlying Base Objects

ETRM documentation identifies a single underlying base object: IGS_HE_POOUS_OU_ALL. The _ALL suffix indicates a multi-organization (multi-org) table, which in R12 is partitioned by ORG_ID. The view does not expose ORG_ID; consequently, any query against the view returns rows for every organization the querying responsibility is permitted to see under the active Multi-Org security profile. The view's FROM clause references the table directly, without joins, filters, or subqueries, so row counts and cardinality are identical to the base table.

The documented ETRM metadata records no additional referenced base objects, and the base view carries no reference to a program, unit set, or organization master view. Any descriptive attributes (program titles, unit set names, organization names) must be obtained by joining this view to the corresponding master views or tables outside its definition.

Key Columns

• HESA_POOUS_OU_ID — The unique surrogate identifier of the organization unit allocation record. The ETRM column list documents this identifier, and the view text aliases it to the same name. Users searching for the string hesa_poous_ou_id are most likely looking for this primary key, which is the correct join key to related HESA detail views and extract tables.
• PROGRAM_CODE (source COURSE_CD) — The course/program code. Note the deliberate renaming: the source column retains legacy "COURSE" terminology, while the view presents it under the HESA "PROGRAM" convention.
• PROGRAM_VERSION_NUMBER (source CRV_VERSION_NUMBER) — The version of the program record to which the allocation applies.
• CALENDAR_TYPE and LOCATION_CODE (source LOCATION_CD) — The calendar and delivery location context for the offering.
• ATTENDANCE_MODE and ATTENDANCE_TYPE — HESA attendance classifications for the offering.
• UNIT_SET_CODE (source UNIT_SET_CD) and UNIT_SET_VERSION_NUMBER (source US_VERSION_NUMBER) — The unit set and its version with which the organization allocation is associated.
• ORGANIZATION_UNIT_CODE (source ORGANIZATION_UNIT) — The code of the organizational unit involved in delivering or owning the unit set.
• ORGANIZATION_UNIT_PROP (source PROPORTION) — The proportion attributable to that organization unit. Typical HESA practice is that proportions across a given unit set sum to 1 (or 100%), and this column is the value reported in the corresponding HESA return field.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit columns, passed through unchanged; useful for incremental extracts and troubleshooting.

Common Use Cases and Queries

The principal use case is the production of HESA organization unit returns for program offering option unit sets, together with data extracts feeding a data warehouse or a downstream reporting platform. Because the view is read-only and unjoined, it is typically used as the driving query for such extracts.

A basic extract confirming the identifier and its organization allocation:

• SELECT hesa_poous_ou_id, program_code, program_version_number, unit_set_code, unit_set_version_number, organization_unit_code, organization_unit_prop FROM igsbv_uk_prg_ofr_opt_org_units;

A targeted lookup by the identifier the user searched on:

• SELECT program_code, calendar_type, location_code, organization_unit_code, organization_unit_prop FROM igsbv_uk_prg_ofr_opt_org_units WHERE hesa_poous_ou_id = :p_id;

An incremental extract for a reporting period, using the audit columns:

• SELECT hesa_poous_ou_id, program_code, unit_set_code, organization_unit_code, organization_unit_prop, last_update_date FROM igsbv_uk_prg_ofr_opt_org_units WHERE last_update_date >= :p_since;

Where proportion validation is required, the view can be aggregated by unit set to confirm that allocations reconcile to the expected total, and rows can be joined on HESA_POOUS_OU_ID to other HESA organization detail views that share the same key. Implementers should note the "Not implemented in this database" designation in the ETRM record: on a target instance where the IGS schema is absent, these queries will fail with an invalid object reference, and equivalent data must be sourced from whichever product now owns the program offering organization allocation.