Search Results hesa_st_uv_cc_id




Overview
Explore in AI Chat

Overview

The IGS.IGS_HE_ST_UV_CC_ALL table is a table-level data object owned by the IGS schema in Oracle E-Business Suite. It is documented as obsolete and is described as holding HESA (Higher Education Statistics Agency) UK statistics unit cost centre details. The object is marked with the FND Design Data identifier IGS.IGS_HE_ST_UV_CC_ALL and has a status of VALID, though its obsolete designation indicates it is retained for legacy reporting and historical extract purposes rather than active transactional processing within the UK higher education statutory returns subsystem.

The table is physically stored in the APPS_TS_TX_DATA tablespace with a PCT Free value of 10. Its primary key, IGS_HE_ST_UV_CC_ALL_PK, is defined on the surrogate column HESA_ST_UV_CC_ID. Heuristic Data Vault classification mined from the foreign key structure suggests a satellite-leaning role: the table records attributes and proportions associated with a business entity (unit versions) rather than acting as a pure hub or link.

Key Information Stored

The table contains twelve documented columns. The most significant are described below.

  • HESA_ST_UV_CC_ID — Sequence-generated surrogate identifier for each record; serves as the primary key and is the sole column of unique index IGS_HE_ST_UV_CC_ALL_U1.
  • ORG_ID — Multi-org identifier (length 15) supporting operating unit partitioning.
  • UNIT_CD — Unit code (VARCHAR2 length 10); part of the business-key candidate in unique index IGS_HE_ST_UV_CC_ALL_U2 and the FK column referencing IGS_PS_UNIT_VER_ALL.UNIT_CD.
  • VERSION_NUMBER — Unit version number; combined with UNIT_CD, COST_CENTRE, and SUBJECT in index U2.
  • COST_CENTRE — Cost centre code (VARCHAR2 length 30); a business-key candidate column.
  • SUBJECT — Subject code (VARCHAR2 length 30); the fourth column of the U2 composite business key.
  • PROPORTION — Numeric value recording the proportion contributed by this cost centre towards the unit; this is the principal measured fact of the satellite.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing row provenance and change metadata.

The surrogate key (HESA_ST_UV_CC_ID) is distinct from the documented business keys: index U2 on (UNIT_CD, VERSION_NUMBER, COST_CENTRE, SUBJECT) enforces uniqueness of the real-world cost-centre allocation grain.

Common Use Cases and Queries

Because the object is obsolete, its principal contemporary use is historical reconciliation and audit of HESA unit cost centre apportionment. Reporting scenarios typically join the table to unit version records and aggregate proportions by cost centre or subject.

A representative query retrieves all rows for a given unit version:

SELECT c.UNIT_CD, c.VERSION_NUMBER, c.COST_CENTRE,
       c.SUBJECT, c.PROPORTION
  FROM IGS.IGS_HE_ST_UV_CC_ALL c
 WHERE c.UNIT_CD = :unit_cd
   AND c.VERSION_NUMBER = :version;

A second pattern validates that proportions sum to the expected total for each unit version, supporting data-quality checks prior to statutory submission:

SELECT UNIT_CD, VERSION_NUMBER, SUM(PROPORTION)
  FROM IGS.IGS_HE_ST_UV_CC_ALL
 GROUP BY UNIT_CD, VERSION_NUMBER
HAVING SUM(PROPORTION) != 1;

Extract queries filtering on the composite business key can rely on index U2 to locate specific cost centre and subject combinations efficiently.

Related Objects

The following objects are significant in relation to this table.

  • IGS.IGS_PS_UNIT_VER_ALL — Parent entity referenced by the foreign key on UNIT_CD; supplies unit version context.
  • APPS.IGS_HE_ST_UV_CC_ALL — The APPS synonym or view layer exposing the table to application code; listed as a dependent object.
  • Indexes IGS_HE_ST_UV_CC_ALL_U1 (on HESA_ST_UV_CC_ID) and IGS_HE_ST_UV_CC_ALL_U2 (on UNIT_CD, VERSION_NUMBER, COST_CENTRE, SUBJECT), both unique and held in the APPS_TS_TX_IDX tablespace, function as dependent schema objects.

Per the documented dependency information, the table does not itself reference any database object beyond its FK to the unit version table, and it is referenced only through the APPS layer.