Search Results igs_he_code_types_u1




Overview
Explore in AI Chat

Overview

The table IGS.IGS_HE_CODE_TYPES is a seed-data reference table within the IGS (Intelligent Grants System / Higher Education Statistics) schema of Oracle E-Business Suite. In the context of release 12.1.1 and 12.2.2, it functions as the master catalogue of all Code Types defined for use in the HESA (Higher Education Statistics Agency) reporting framework. Each row defines a distinct classification category — such as a student characteristic, qualification type, or institution attribute — that is subsequently populated with allowable values in the companion values table. The object resides in the APPS_TS_SEED tablespace, confirming its role as seeded setup data rather than transactional data, and carries the FND Design Data reference IGS.IGS_HE_CODE_TYPES. From a Data Vault modeling perspective, the heuristic classification of this object is hub-leaning, meaning it behaves as a business-key registry whose primary key uniquely identifies each code type and from which dependent satellite-style attributes (titles and descriptions) and downstream link tables (the code values) radiate.

Key Information Stored

The table comprises eight documented columns, anchored by a single-column primary key and a redundant unique index that reinforces the business key.

  • CODE_TYPE (VARCHAR2(30), mandatory): The business key and primary key (IGS_HE_CODE_TYPES_PK). It holds the internal name of the code classification defined in the HESA system. This column is also carried by the unique index IGS_HE_CODE_TYPES_U1, which the user searched for directly — it is a NORMAL, UNIQUE index on CODE_TYPE in the APPS_TS_SEED tablespace.
  • DISPLAY_TITLE (VARCHAR2(80)): The human-readable title presented for the code type in forms, lists of values, and reports.
  • DESCRIPTION (VARCHAR2(240)): A longer free-text explanation of what the code type represents, useful for documentation and user assistance.
  • WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide the standard Oracle EBS audit trail recording which user created or last modified each seed row and when.

No surrogate numeric key is documented; CODE_TYPE serves simultaneously as business key and primary key, which is characteristic of a hub entity in Data Vault terms. The unique index IGS_HE_CODE_TYPES_U1 is functionally equivalent to the primary key constraint and can be relied upon for direct single-row lookups by code name.

Common Use Cases and Queries

Typical usage involves validating a code type before inserting dependent values, driving HESA submission extracts, and generating administrative reports of configured classifications. A direct lookup by the business key is the most frequent access path:

  • SELECT display_title, description FROM igs.igs_he_code_types WHERE code_type = :p_code_type;
  • Reporting all configured types: SELECT code_type, display_title FROM igs.igs_he_code_types ORDER BY code_type;
  • Audit and change tracking: filter on last_update_date to identify recently reseeded or patched code types after applying a HESA-related patch.
  • Dependency analysis before loaders: join to IGS_HE_CODE_VALUES to confirm every code type has at least one allowable value.

Because the table is a seed object, direct DML should be avoided in production; inserts and updates should arrive via patching or supported concurrent programs.

Related Objects

The most significant dependent object is IGS.IGS_HE_CODE_VALUES, which references this table through the CODE_TYPE column (a foreign key to IGS_HE_CODE_TYPES.CODE_TYPE). The join pattern is:

  • IGS_HE_CODE_VALUES.CODE_TYPE → IGS_HE_CODE_TYPES.CODE_TYPE (master-detail relationship between code type and its allowed values).
  • IGS.IGS_HE_CODE_TYPES itself is exposed as an APPS-synonymed object and does not reference any other database object, making it a root master table.
  • The unique index IGS_HE_CODE_TYPES_U1 and primary key IGS_HE_CODE_TYPES_PK are the principal access structures referenced by any code performing validation lookups.

Any HESA reporting module, validation routine, or grants setup form that consumes code values will transitively depend on this table through its relationship with IGS_HE_CODE_VALUES.