Search Results igf_gr_alt_amts




Overview

IGF_GR_ALT_AMTS is a Financial Aid module table owned by the IGF schema in Oracle E-Business Suite. It stores the Alternate Pell Amount that applies to a given combination of cost of attendance (COA) range, expected family contribution (EFC) range, and alternate expense range. In practice, this table functions as the lookup repository that the Financial Aid Pell processing logic consults when the standard Pell award schedule does not directly apply, allowing institutions to derive a Pell disbursement amount from ranges rather than from a single point value.

The table is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and its physical schema is identical across the two releases, with 15 documented columns. From a data-modeling perspective, the metadata's heuristic Data Vault classification places this object as standalone, meaning it exhibits no foreign-key dependencies on other tables in the mined structure. A modeling suggestion consistent with that classification is to treat IGF_GR_ALT_AMTS as an independent reference or lookup entity rather than as a hub, link, or satellite within a Data Vault model.

Key Information Stored

The table is keyed by a single-column surrogate primary key, IGF_GR_ALT_AMTS_PK, defined on SEQUENCE_TXT. Two unique indexes establish business-key candidates:

The most significant non-key column is PELL_AMOUNT, which holds the alternate Pell award value returned when a student's cost of attendance, expected family contribution, and alternate expenses all fall within the ranges defined on that row. SYS_AWD_YR scopes each row to a specific system award year, while ENROLLMENT_STAT_CODE distinguishes full-time, part-time, and other enrollment categories so that separate schedules can coexist. The paired range columns (COA_RANGE_START/COA_RANGE_END, EFC_RANGE_START/EFC_RANGE_END, EXP_RANGE_START/EXP_RANGE_END) define the interval boundaries against which student data is matched. Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — provide audit tracking.

Common Use Cases and Queries

The primary use case is Pell award determination for students whose calculated COA, EFC, and alternate expenses require a range-based lookup rather than a fixed scheduled amount. A representative query retrieves the alternate amount for a specific aid year, enrollment status, and student profile:

  • SELECT sequence_txt, pell_amount FROM igf.igf_gr_alt_amts WHERE sys_awd_yr = :aid_year AND enrollment_stat_code = :status AND :coa BETWEEN coa_range_start AND coa_range_end AND :efc BETWEEN efc_range_start AND efc_range_end AND :expenses BETWEEN exp_range_start AND exp_range_end;

Reporting scenarios include auditing configured range schedules for a given award year, verifying that no gaps or overlaps exist in the U2 key combination, and reconciling awarded Pell amounts against the configured PELL_AMOUNT values. Administrative extract queries selecting SYS_AWD_YR, ENROLLMENT_STAT_CODE, all six range columns, and PELL_AMOUNT support both regulatory review and institution-specific packaging analysis.

Related Objects

The mined relationship data classifies IGF_GR_ALT_AMTS as standalone, so no foreign-key dependencies are documented against other IGF tables. The logical relationships implied by its columns are:

  • Award year and Pell configuration tables in the IGF schema, joined on SYS_AWD_YR, supplying the system award year context.
  • Enrollment status reference tables, joined on ENROLLMENT_STAT_CODE, resolving the enrollment category codes used in the U2 business key.
  • Student financial aid record tables holding calculated COA, EFC, and alternate expense amounts, which supply the bind values matched against the range columns.
  • Award disbursement and packaging tables in the Financial Aid module that consume PELL_AMOUNT as an input to award calculation.
  • The IGF_GR_ALT_AMTS_PK and IGF_GR_ALT_AMTS_U1/U2 indexes, which are the only co-located objects formally documented alongside the table.

Because the FK structure is empty, consumers should rely on column-level joins and application logic rather than declared referential integrity when tracing dependencies.