Search Results igs_he_code_values_pk

Overview

IGS_HE_CODE_VALUES is a reference (lookup) table in the IGS — Student System product of Oracle E-Business Suite, owned by the IGS schema. Its documented purpose is to hold the code values for each defined HESA (Higher Education Statistics Agency) code type in the system. In practice, this table acts as the value-level companion to IGS_HE_CODE_TYPES: the parent table defines the categories of HESA coding, while IGS_HE_CODE_VALUES enumerates the individual valid codes belonging to each category, together with their descriptions and an active/closed indicator.

Under a heuristic Data Vault classification mined from its foreign key structure, this object is satellite-leaning. It carries descriptive attributes (value description, audit columns, closed indicator) attached to a business key composed of CODE_TYPE and VALUE, and it references a single parent. It does not behave as a hub or a link, since it introduces no independent business entity of its own and resolves no many-to-many relationship. It is best modelled as a descriptive satellite over the HESA code-type construct, with the parent IGS_HE_CODE_TYPES supplying the hub context.

Key Information Stored

The table is documented with nine physical columns. The most significant are:

• CODE_TYPE — the HESA code category to which a value belongs; this is the foreign key column that joins to IGS_HE_CODE_TYPES.
• VALUE — the coded value itself, the abbreviation or numeric code accepted for the given type.
• VALUE_DESCRIPTION — the human-readable meaning of the code, used in list of values displays and reports.
• CLOSED_IND — indicates whether the code value is still valid for entry or has been retired from active use.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns tracking who created and last modified the row, and through which login session.

The primary key is IGS_HE_CODE_VALUES_PK, defined over the composite of (CODE_TYPE, VALUE). A separate unique index, IGS_HE_CODE_VALUES_U1, is documented over the same two columns (CODE_TYPE, VALUE), confirming that this pair is the natural business key of the table rather than a system-generated surrogate. Because the key is composite and drawn from meaningful data, the primary key and the business-key candidate coincide here; there is no separate meaningless sequence column in the documented schema.

Common Use Cases and Queries

The table is principally consumed for validation and presentation. When a user enters a HESA code on a student record, the application resolves the code against this table for the relevant CODE_TYPE. Reporting queries typically join to the parent type table to present both the category and the value description:

• List all active values for a given HESA code type: SELECT value, value_description FROM igs.igs_he_code_values WHERE code_type = :type AND NVL(closed_ind,'N') = 'N' ORDER BY value;
• Present a fully described code on a student extract: join IGS_HE_CODE_TYPES on CODE_TYPE to obtain the type description alongside VALUE_DESCRIPTION.
• Audit recently changed reference data: filter on LAST_UPDATE_DATE to identify codes added or amended during a reporting period.
• Identify retired codes still referenced on historical records, by selecting rows where CLOSED_IND is set but the code remains in use.

Because this is reference data, direct DML is normally discouraged; changes should be made through the supported HESA code maintenance functionality so that dependent validation and any cached lists of values remain consistent.

Related Objects

• IGS_HE_CODE_TYPES — the parent table; IGS_HE_CODE_VALUES.CODE_TYPE references it. This is the primary join and the defining parent-child relationship in the documented metadata.
• IGS_HE_CODE_VALUES_PK and IGS_HE_CODE_VALUES_U1 — the primary key constraint and unique index enforcing the (CODE_TYPE, VALUE) business key.
• Student and admissions base tables that capture HESA-coded attributes (for example student programme, qualification and enrolment records within the IGS schema) resolve their entered codes through this table rather than storing free text.
• HESA statutory return extracts and associated reporting views depend on this table to translate stored codes into the descriptions and formats required for submission.
• Generic Oracle EBS list-of-values and reference-data validation mechanisms reference the table by CODE_TYPE and VALUE for user-facing code selection.