Search Results unit_subject




Overview

IGSFV_UNIT_STAT_COST_CENTRES is an APPS-owned read-only view within the IGS (Student System) product family of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. Its stated purpose is to present "Full View for UK Statistics Unit Cost Center Details," meaning it consolidates the cost-centre and subject attribution data that UK higher-education institutions must report against taught units for statutory returns such as HESA. The view joins unit cost-centre allocations to the corresponding unit version definitions, so that each statistical record carries both the numeric cost-centre values required for reporting and the human-readable descriptive text needed by institutional users and downstream extracts.

The view is declared WITH READ ONLY, confirming that it is a reporting and integration artifact only; no DML is permitted against it. Its status is VALID, and its role is to shield consumers from having to replicate the multi-table join logic required to resolve cost-centre codes, subject codes, and unit identifiers into presentable form.

Underlying Base Objects

The view is defined over two base tables and augmented by two correlated scalar subqueries. The ETRM metadata lists no separately documented referenced base objects, but the embedded view text identifies them precisely:

  • IGS_HE_ST_UV_CC_ALL — aliased UCC. This holds the UK statistics unit cost-centre allocations, keyed by HESA statistics identifier, unit code, version number, cost centre, subject, and proportion.
  • IGS_PS_UNIT_VER_ALL — aliased UV. This supplies unit version descriptive attributes, including title, short title, and abbreviation.
  • IGS_HE_CODE_VALUES — accessed via a correlated subquery to translate the cost-centre code into its description using CODE_TYPE = 'OSS_COSTCN'.
  • IGS_PS_FLD_OF_STUDY_ALL — accessed via a correlated subquery to translate the subject code into its description.

The join condition is an equi-join on both UNIT_CD and VERSION_NUMBER, ensuring that cost-centre rows are matched to the correct version of the unit rather than to the unit as a whole. Because the view resolves code values through lookups rather than storing them, any change to the underlying code-value or field-of-study descriptions is reflected immediately at query time.

Key Columns

Common Use Cases and Queries

Typical uses include UK statutory returns preparation, unit costing analysis, and reconciliation of cost-centre apportionment across unit versions. A common pattern is to filter by unit abbreviation or to list decoded cost-centre and subject descriptions for a reporting period.

SELECT unit_code
     , unit_title
     , unit_abbreviation
     , unit_version_number
     , unit_cost_centre_desc
     , unit_subject_desc
     , unit_cost_centre_subj_prop
FROM   apps.igsfv_unit_stat_cost_centres
WHERE  unit_abbreviation LIKE '%&abbrev%'
ORDER BY unit_code, unit_version_number;

A second pattern aggregates apportionment by cost centre to verify that proportions balance to one per unit version:

SELECT unit_code
     , unit_version_number
     , SUM(unit_cost_centre_subj_prop) total_proportion
FROM   apps.igsfv_unit_stat_cost_centres
GROUP BY unit_code, unit_version_number
HAVING SUM(unit_cost_centre_subj_prop) <> 1;

Because the view is read-only and resolves descriptions dynamically, it is well suited to ad-hoc inquiry, BI Publisher extracts, and interface feeds requiring both coded and descriptive cost-centre data.