Search Results hesa_unit_cc_id




Overview
Explore in AI Chat

Overview

IGSBV_UNIT_HESA_COST_CENTRES is a base business view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. Its stated purpose, per the ETRM documentation, is to allow queries on Unit HESA Cost Center Details. The view presents a flattened, read-only projection of the Higher Education Statistics Agency (HESA) cost centre assignments associated with academic units, exposing both unit identification attributes and the corresponding cost centre, subject code, and proportional weighting. Because HESA returns in the United Kingdom require institutions to report teaching activity apportioned across cost centres and subject categories, this view provides the reporting layer through which that apportionment data is surfaced for extraction, institutional reporting, and downstream integration. It is designated a "base business view," indicating it is intended as a foundation object referenced by other reporting views and extracts rather than as an end-user data-entry form.

Underlying Base Objects

The view is defined over a single underlying base table, IGS_HE_UNT_OU_CC, aliased as UCC. The view definition has no joins, unions, or aggregations; it is a direct column-mapping projection that renames columns for business consumption and applies a WITH READ ONLY clause. The documented base object list in the metadata is empty, but the view text explicitly references IGS_HE_UNT_OU_CC. The table name suggests the entity stores Higher Education unit-to-organizational-unit cost centre relationships, with one row per cost centre / subject allocation for a given unit and version. Because the view is read-only and carries no INSTEAD OF triggers, it cannot be used to insert or update HESA cost centre records; maintenance is performed against the base table through the associated Student System maintenance forms or APIs.

Key Columns

  • HESA_UNIT_CC_ID — Surrogate primary key of the underlying cost centre allocation record, renamed from HESA_UNIT_CC_ID in the base table.
  • UNIT_CODE — The academic unit code (UCC.UNIT_CD), identifying the unit to which the cost centre allocation belongs.
  • UNIT_VERSION_NUMBER — The version of the unit record, supporting versioned curricula and historical reporting.
  • ORG_UNIT_CODE — The organizational unit code (UCC.ORG_UNIT_CD) tied to the allocation.
  • UNIT_COST_CENTRE — The HESA cost centre value (UCC.COST_CENTRE) assigned to the unit.
  • UNIT_SUBJ — The subject code (UCC.SUBJECT) associated with the cost centre allocation. This is the column most directly relevant to the search term "unit_subj."
  • UNIT_COST_CENTRE_SUBJ_PROP — The proportion of activity attributed to the cost centre / subject combination (UCC.PROPORTION), enabling weighted reporting.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard Oracle audit columns inherited from the base table.

Common Use Cases and Queries

Typical usage includes HESA statutory returns, costing and funding analysis, faculty-level cost distribution reporting, and data extracts feeding institutional data warehouses. A frequent query pattern retrieves all cost centre and subject allocations for a specified unit and version. For example:

SELECT unit_code, unit_version_number, unit_cost_centre, unit_subj, unit_cost_centre_subj_prop FROM apps.igsbv_unit_hesa_cost_centres WHERE unit_code = :p_unit_code AND unit_version_number = :p_version ORDER BY unit_cost_centre, unit_subj;

A second common pattern aggregates proportional weights by cost centre to validate that the sum of proportions for a unit equals 1 (or 100%), which is a standard reconciliation check before submitting HESA data:

SELECT unit_code, unit_version_number, unit_cost_centre, SUM(unit_cost_centre_subj_prop) FROM apps.igsbv_unit_hesa_cost_centres WHERE unit_code = :p_unit_code GROUP BY unit_code, unit_version_number, unit_cost_centre;

Because the view is read-only and unaggregated, it is well suited to being embedded in custom reports, OBIEE/BI Publisher data models, and SQL*Loader-based extracts. All access should be granted through the APPS schema, and queries should filter on UNIT_CODE and UNIT_VERSION_NUMBER to avoid full scans of large institutional data sets.