Search Results igs_ge_ref_cd_u2

Overview

The IGS_GE_REF_CD table is a core reference data repository within the Oracle E-Business Suite (EBS) Student System (IGS). Its primary role is to store the individual, valid code values associated with specific reference code types. This table functions as a master list of coded values, enabling data integrity, standardization, and validation across various student administration modules. It is critical for maintaining a controlled vocabulary for attributes such as admission types, unit requirements, and assessment references. The metadata explicitly notes the IGS product as "Obsolete," indicating this table is part of a legacy student system architecture that may have been superseded in later EBS versions or by Oracle's Campus Solutions product.

Key Information Stored

The table's structure is designed to uniquely identify each reference code and its association with a code type. Based on the provided primary and foreign key definitions, the essential columns include:

• REFERENCE_CODE_ID: The primary key column for the table, serving as a unique system identifier for each reference code record. This surrogate key is referenced by other tables like IGS_AV_UNT_REF_CDS and IGS_AS_SUA_REF_CDS.
• REFERENCE_CD_TYPE: A foreign key column linking to the IGS_GE_REF_CD_TYPE_ALL table. This defines the category or domain to which a reference code belongs (e.g., 'ADMISSION_CATEGORY', 'UNIT_LEVEL').
• REFERENCE_CD: The actual short code or value itself (e.g., 'FRESH', 'POSTGRAD'). This column, combined with REFERENCE_CD_TYPE, forms a unique alternate key (IGS_GE_REF_CD_U2).

While the specific metadata does not list descriptive columns like MEANING or DESCRIPTION, such columns are typical in EBS reference tables to provide a human-readable explanation for the code.

Common Use Cases and Queries

This table is central to lookup operations and data validation. Common use cases include validating user input against a list of permitted codes, populating list-of-values (LOV) in application forms, and joining to transactional data for reporting. A typical query to retrieve all valid codes for a specific type would be:

SELECT reference_cd, description
FROM igs_ge_ref_cd
WHERE reference_cd_type = '&REF_CODE_TYPE'
AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE)
ORDER BY reference_cd;

For reporting, a common pattern is to join transactional data with this table to decode ID or code values into meaningful descriptions. For example, joining student unit attempt reference data would use:
SELECT sua.column1, refcd.reference_cd, refcd.description
FROM igs_as_sua_ref_cds sua_ref,
igs_ge_ref_cd refcd
WHERE sua_ref.reference_code_id = refcd.reference_code_id
AND sua_ref.column2 = :some_value;

Related Objects

The IGS_GE_REF_CD table has defined relationships with several key tables in the Student System, as documented in the foreign key metadata. These relationships are categorized as follows:

• Parent Reference:
  • IGS_GE_REF_CD_TYPE_ALL via column IGS_GE_REF_CD.REFERENCE_CD_TYPE
• Child References (Tables referencing IGS_GE_REF_CD):
  • IGS_AV_UNT_REF_CDS via REFERENCE_CODE_ID
  • IGS_AS_SUA_REF_CDS via REFERENCE_CODE_ID
  • IGS_PS_ENT_PT_REF_CD via (REFERENCE_CD_TYPE, REFERENCE_CD)
  • IGS_PS_UNITREQREF_CD via (REFERENCE_CD_TYPE, REFERENCE_CODE)
  • IGS_PS_US_REQ_REF_CD via (REFERENCE_CD_TYPE, REFERENCE_CODE)
  • IGS_PS_UNIT_REF_CD via (REFERENCE_CD_TYPE, REFERENCE_CD)
  • IGS_PS_USEC_OCUR_REF via (REFERENCE_CODE_TYPE, REFERENCE_CODE)
  • IGS_PS_USEC_REF_CD via (REFERENCE_CODE_TYPE, REFERENCE_CODE)

These relationships highlight the table's integral role in the Program Structures (IGS_PS), Assessments (IGS_AS), and Awards (IGS_AV) modules, where it provides standardized code values for various configuration and transactional records.