Results for “igs_he_prog_ou_cc_u1”

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

Overview

The IGS.IGS_HE_PROG_OU_CC table is a transactional table within the Oracle E-Business Suite higher education (HESA) module, owned by the IGS schema. It was introduced to replace the legacy cost center table at the program level, extending cost center recording so that users may capture organizational unit details alongside cost center details for a specific program and version combination. This aligns with HESA statutory reporting requirements, where institutions must attribute teaching and funding proportions across organizational units and cost centers per program.

The table is stored in the APPS_TS_TX_DATA tablespace with PCT Free 10, while its associated indexes reside in APPS_TS_TX_IDX. The ETRM metadata classifies the object as a standalone table, meaning it holds no foreign key references to other database objects and is not referenced by declared foreign keys. Under a heuristic Data Vault modeling perspective, IGS_HE_PROG_OU_CC is best treated as a satellite-style structure: it records descriptive attributes (cost center, subject, proportion) attached to a business key composed of COURSE_CD, VERSION_NUMBER, ORG_UNIT_CD, COST_CENTRE, and SUBJECT, with HESA_PROG_CC_ID serving as the surrogate primary key.

Key Information Stored

The table contains twelve documented columns. The most significant are:

• HESA_PROG_CC_ID — NUMBER, the unique record identifier and the surrogate primary key enforced by the IGS_HE_PROG_OU_CC_PK unique index.
• COURSE_CD — VARCHAR2(10), the program code identifying the academic program.
• VERSION_NUMBER — NUMBER, the program version number, enabling multiple effective versions of the same program.
• ORG_UNIT_CD — VARCHAR2(30), the organizational unit code to which the program/version allocation applies.
• COST_CENTRE — VARCHAR2(30), the cost center associated with the allocation.
• SUBJECT — VARCHAR2(30), the subject classification linked to the record.
• PROPORTION — NUMBER, the proportion attributed to the combination of program, version, org unit, cost center, and subject.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing record creation and modification history.

The unique index IGS_HE_PROG_OU_CC_U1 on (COURSE_CD, VERSION_NUMBER, ORG_UNIT_CD, COST_CENTRE, SUBJECT) is the principal business-key candidate, guaranteeing that each program/version/org-unit/cost-center/subject combination appears only once. The distinction between the surrogate key and this composite business key is important when designing interfaces or ETL mappings into the table.

Common Use Cases and Queries

Typical use cases include HESA return preparation, internal financial allocation analysis, and reconciliation between cost centers and organizational units at the program level. A common retrieval pattern joins the table to program and version references to obtain cost center allocations for a given course:

• Select all allocations for a program version: SELECT COURSE_CD, VERSION_NUMBER, ORG_UNIT_CD, COST_CENTRE, SUBJECT, PROPORTION FROM IGS.IGS_HE_PROG_OU_CC WHERE COURSE_CD = :course AND VERSION_NUMBER = :version;
• Aggregate proportion by cost center for a reporting period or program set.
• Detect duplicate or missing business-key combinations by grouping on the U1 columns and comparing against HESA return expectations.
• Audit trail queries against CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to trace record maintenance.

Because the table is standalone, queries do not require mandatory joins, though reporting solutions typically join to program, organizational unit, and cost center reference tables through the descriptive columns rather than declared foreign keys.

Related Objects

The ETRM metadata states that IGS.IGS_HE_PROG_OU_CC references no database objects and is referenced only by the APPS synonym IGS_HE_PROG_OU_CC. Consequently, relationships to other objects are logical rather than enforced by foreign keys. The most significant related objects are:

• APPS.IGS_HE_PROG_OU_CC — the APPS synonym through which the table is accessed by application code and reports.
• IGS.IGS_HE_PROG_CC — the legacy program-level cost center table this object was introduced to replace; migration or comparison queries typically align on COURSE_CD and VERSION_NUMBER.
• Program reference objects (IGS program/version tables) — joined through COURSE_CD and VERSION_NUMBER to obtain program titles and status.
• Organizational unit reference objects — joined through ORG_UNIT_CD.
• Cost center reference objects (IGS/FND cost center definitions) — joined through COST_CENTRE.
• Subject reference objects — joined through SUBJECT for HESA subject classification reporting.
• HESA return extract concurrent programs — consume this table to populate statutory returns.

Because referential integrity is not enforced at the database level, data-quality checks joining these logical reference objects are recommended before any HESA or financial reporting submission.