Search Results igs_he_st_uv_cc_all




Overview
Explore in AI Chat

Overview

The IGS_HE_ST_UV_CC_ALL table is a core data structure within the Oracle E-Business Suite Student System (IGS) module. It is specifically designed to support statutory reporting requirements for the United Kingdom's Higher Education Statistics Agency (HESA). The table's primary function is to store and manage unit cost center details, which are essential for mapping academic units to specific financial cost centers for the purpose of generating HESA-compliant statistical returns. This linkage between the academic unit structure and financial costing is critical for institutions to meet their mandatory UK government reporting obligations within the Oracle EBS framework, versions 12.1.1 and 12.2.2.

Key Information Stored

The table stores the relationship between a unit offering and its associated cost center for HESA reporting. While the full column list is not detailed in the provided metadata, the documented primary and foreign keys reveal its core structure. The primary key column, HESA_ST_UV_CC_ID, uniquely identifies each record. The table's essential foreign key relationship is established through the UNIT_CD and VERSION_NUMBER columns, which link directly to the IGS_PS_UNIT_VER_ALL table. This connection anchors the HESA cost center data to a specific version of an academic unit. Additional columns in the table would typically store the applicable cost center code, effective dates, and other control attributes necessary for accurate and auditable statutory reporting.

Common Use Cases and Queries

The primary use case for this table is the extraction of data for the annual HESA student and staff returns. Reports and interfaces will query this table to determine the correct financial cost center to associate with a student's unit enrollment or a staff member's teaching activity. A typical query pattern involves joining this table to the unit version and student unit attempt or staff assignment tables. For example, to list all units with their assigned HESA cost centers, a query would be: SELECT uv.unit_cd, uv.version_number, cc.cost_center_code FROM igs_ps_unit_ver_all uv, igs_he_st_uv_cc_all cc WHERE uv.unit_cd = cc.unit_cd AND uv.version_number = cc.version_number AND SYSDATE BETWEEN cc.start_date AND NVL(cc.end_date, SYSDATE);. Data integrity checks are another common scenario, such as identifying unit versions missing a required HESA cost center mapping.

Related Objects

The table has defined dependencies within the Student System schema, as per the provided relationship data.

  • Primary Key: IGS_HE_ST_UV_CC_ALL_PK on column HESA_ST_UV_CC_ID.
  • Foreign Key (References): The table has a critical foreign key relationship to the IGS_PS_UNIT_VER_ALL table. This relationship ensures that every cost center record is associated with a valid academic unit version. The join is performed on the composite key: IGS_HE_ST_UV_CC_ALL.UNIT_CD = IGS_PS_UNIT_VER_ALL.UNIT_CD and IGS_HE_ST_UV_CC_ALL.VERSION_NUMBER = IGS_PS_UNIT_VER_ALL.VERSION_NUMBER.

This table is likely referenced by HESA-specific extract programs, views, and interfaces within the IGS product family to assemble the complete data set for UK statutory submissions.