Search Results igs_he_code_types_pk

Overview

The IGS_HE_CODE_TYPES table is a reference (code type) definition table within the IGS — Student System product of Oracle E-Business Suite. Its documented purpose is to determine all the Code Types defined for use in the HESA (Higher Education Statistics Agency) system. This makes it the master catalog of HESA code categories — each row defines a distinct type of coded value that may subsequently be assigned one or more valid code entries. It is owned by the IGS schema and holds a status of VALID in both EBS 12.1.1 and 12.2.2.

Under the heuristic Data Vault classification mined from the foreign-key structure, this table is hub-leaning. In Data Vault modeling terms, CODE_TYPE behaves as a business key hub: it is the stable, unique identifier around which descriptive attributes and downstream dependent tables (the satellites and links) are organized. Analysts building a Data Vault or dimensional layer should treat CODE_TYPE as the natural business key and consider the surrounding descriptive columns as hub attributes rather than transactional facts.

Key Information Stored

The table comprises eight documented columns. The most significant are:

• CODE_TYPE — The core identifier of a HESA code type. It is both the primary key (via IGS_HE_CODE_TYPES_PK) and the business-key candidate exposed through the unique index IGS_HE_CODE_TYPES_U1. This column is the join point to dependent tables.
• DISPLAY_TITLE — The user-facing label presented for the code type, typically shown in List of Values (LOV) pickers and inquiry screens.
• DESCRIPTION — A fuller narrative explanation of what the code type represents and how it should be used.
• CREATED_BY, CREATION_DATE — Standard EBS audit columns capturing who created the definition and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording the most recent modification and the session that performed it.

The primary key IGS_HE_CODE_TYPES_PK is defined on CODE_TYPE. Because CODE_TYPE is also the sole column of the unique index IGS_HE_CODE_TYPES_U1, the surrogate and business key effectively coincide — there is no separate system-generated surrogate identifier documented here.

Common Use Cases and Queries

Because this is a reference table, the most frequent operations are lookups for validation and reporting. A typical query to retrieve all defined HESA code types is:

• SELECT code_type, display_title, description FROM igs.igs_he_code_types ORDER BY code_type;

A validation pattern checks that a supplied code type exists before insert into a dependent table:

• SELECT COUNT(*) FROM igs.igs_he_code_types WHERE code_type = :p_code_type;

A relational query lists each code type alongside its associated values, joining on CODE_TYPE to IGS_HE_CODE_VALUES. Reporting use cases include populating LOVs and flexfields, driving HESA statutory returns, and auditing reference data lineage for regulatory submissions. Because the table is low-volume and rarely changes, it is often extracted in full into a data warehouse as a conformed dimension.

Related Objects

The documented foreign-key relationship shows that the most significant dependent object is:

• IGS_HE_CODE_VALUES — Its CODE_TYPE column holds a foreign key referencing IGS_HE_CODE_TYPES.CODE_TYPE. This child table stores the individual valid coded values permitted for each code type, forming the classic parent/child reference pair.

Beyond the FK structure, the table typically interacts with HESA-related setup and student records screens that consume these code types for validation, and with reporting extracts that join it to the values table. Indexes IGS_HE_CODE_TYPES_PK and IGS_HE_CODE_TYPES_U1 both support the CODE_TYPE lookup path used by these dependent joins.