Search Results int_lookup_code




Overview
Explore in AI Chat

Overview

The IGF_AW_INT_EXT_MAP table is a core data structure within the Oracle E-Business Suite's Financial Aid module (IGF). Its primary function is to serve as a translation layer between the institution's internal coding structures and the standardized, federally mandated codes required for regulatory reporting and external data exchanges. This mapping is essential for ensuring compliance with U.S. Department of Education regulations, as it allows institutions to maintain their internal business logic and award definitions while accurately translating them into the specific codes (e.g., for award types, disbursement plans) mandated for submissions like the ISIR and Pell Grant processing. The table's design enforces uniqueness per award year, preventing conflicting mappings for a given period.

Key Information Stored

The table's structure is defined by a surrogate primary key and two critical unique keys that govern the mapping logic. The key columns are:

  • IXM_ID: A system-generated surrogate primary key (IGF_AW_INT_EXT_MAP_PK).
  • SYS_AWARD_YEAR: The award year context for the mapping, a fundamental partitioning element for the data.
  • INT_LOOKUP_TYPE: The internal Lookup Type (e.g., a user-defined flexfield or application lookup) being mapped.
  • INT_LOOKUP_CODE: The specific code within the internal Lookup Type.
  • EXT_LOOKUP_TYPE: The federally mandated external Lookup Type to which the internal code corresponds.
  • EXT_LOOKUP_CODE: The specific federally mandated code within the external Lookup Type.

The unique constraints (IGF_AW_INT_EXT_MAP_UK1 and UK2) ensure that, for a given award year, an internal code maps to only one external code and vice-versa, maintaining data integrity for the translation process.

Common Use Cases and Queries

This table is primarily accessed during batch processes for federal reporting and award packaging to translate institutional data. A common reporting use case is to audit or review all mappings established for the upcoming award year. A typical query would be:

SELECT sys_award_year, int_lookup_type, int_lookup_code, ext_lookup_type, ext_lookup_code FROM igf.igf_aw_int_ext_map WHERE sys_award_year = '2024-2025' ORDER BY int_lookup_type, int_lookup_code;

Another critical operational query finds the external federal code for a specific internal award type, which is necessary for populating disbursement records or ISIR corrections: SELECT ext_lookup_code FROM igf.igf_aw_int_ext_map WHERE sys_award_year = :p_award_year AND int_lookup_type = 'AWARD_TYPE' AND int_lookup_code = :p_internal_award_code; Conversely, support staff may query the table to identify which internal code is linked to a specific federal code received in an external file.

Related Objects

Based on the provided metadata, the primary documented relationship is its own primary key constraint. The table IGF_AW_INT_EXT_MAP is related to other Financial Aid tables through its key columns, particularly SYS_AWARD_YEAR, INT_LOOKUP_TYPE, and INT_LOOKUP_CODE. These columns would typically join to award definition tables, disbursement setup tables, and student award records. For example, a student's financial aid award (likely in a table such as IGF_AW_AWARD) would store an internal award type code. To process or report that award federally, the system would join via INT_LOOKUP_TYPE/CODE and SYS_AWARD_YEAR to IGF_AW_INT_EXT_MAP to retrieve the mandated external code. The unique constraints (UK1, UK2) indicate these columns are indexed for performance in these joins and validation checks.