Search Results igs_he_code_map_val_pk

Overview

The IGS_HE_CODE_MAP_VAL table is a core data structure within the Oracle E-Business Suite Student System (IGS) module. Its primary function is to store mapping values that link Oracle Student System internal codes to external codes defined by the Higher Education Statistics Agency (HESA). This table acts as a critical translation layer, enabling the system to convert proprietary institutional data into the standardized formats required for statutory HESA reporting in the UK higher education sector. Its existence is essential for compliance, ensuring data submitted to HESA is accurate and adheres to mandated coding frameworks.

Key Information Stored

The table's design centers on a flexible mapping structure. The primary identifier is a system-generated SEQUENCE (primary key IGS_HE_CODE_MAP_VAL_PK). The most critical business key is the ASSOCIATION_CODE, which is a foreign key linking to the IGS_HE_CODE_ASSOC table that defines the specific HESA code set being mapped. The table provides ten mapping columns (MAP1 through MAP10). These columns hold the actual Oracle Student System values that correspond to a single HESA association code. This multi-column structure allows for complex one-to-many mappings where a single HESA code may be linked to multiple valid internal values or value ranges.

Common Use Cases and Queries

The primary use case is the batch processing and validation of data for HESA returns. During extraction routines, the system queries this table to translate institutional codes for fields like student domicile, mode of study, or qualification aim into the correct HESA codes. A typical query would join IGS_HE_CODE_MAP_VAL to IGS_HE_CODE_ASSOC to retrieve all valid mappings for a specific code set. For example, to find all internal program codes mapped to a particular HESA course aim, one might execute: SELECT map1, map2 FROM igs_he_code_map_val cmv, igs_he_code_assoc ca WHERE cmv.association_code = ca.association_code AND ca.hesa_code_name = 'COURSE_AIM';. Reporting use cases include auditing mapping completeness and troubleshooting data discrepancies in HESA submission files.

Related Objects

The table has a direct and fundamental relationship with the IGS_HE_CODE_ASSOC table, which defines the HESA code sets. The documented foreign key constraint explicitly links IGS_HE_CODE_MAP_VAL.ASSOCIATION_CODE to IGS_HE_CODE_ASSOC. This means every record in IGS_HE_CODE_MAP_VAL must reference a valid, pre-defined association code. The IGS_HE_CODE_ASSOC table itself likely contains the descriptive name (e.g., 'ENTRY_ROUTE') and the actual HESA code value. Therefore, to retrieve a meaningful mapping, a join between these two tables is always required. Other objects in the IGS_HE_* schema, such as submission processing programs and validation APIs, will inherently depend on and reference this mapping table.