Search Results igf_aw_fisap_ranges

Overview

The table IGF_AW_FISAP_RANGES belongs to the Oracle EBS product family IGF — Financial Aid, which is documented as obsolete in the ETRM 12.1.1 / 12.2.2 repository. The object is described as a pre-seeded table that stores the FISAP (Fiscal Operations Report and Application to Participate) income ranges. In the context of US federal student financial aid processing, FISAP income ranges define the income brackets used to categorize applicants and recipients, and the pre-seeded nature of this table indicates that the range boundaries were shipped with the product rather than maintained by end users. Because IGF is flagged obsolete, the table is retained primarily for historical data and upgrade continuity rather than active transaction processing.

From a modeling perspective, the ETRM metadata assigns a heuristic Data Vault classification of standalone, meaning no foreign key dependencies were mined from the FK structure. Under Data Vault conventions this object is best treated as a satellite-like reference or lookup table, since it holds descriptive attributes keyed by a business-code combination rather than participating in a hub or link relationship. Note that the documented schema explicitly states "Not implemented in this database" for the referenced ETRM instance, so the physical presence of this table depends on whether the IGF product was ever installed in a given environment.

Key Information Stored

The documented physical schema contains eleven columns. The most significant for querying and interpretation are:

• SEQUENCE_TXT — the primary key component in IGF_AW_FISAP_RANGES_PK. It serves as the surrogate identifier for each seeded income-range row, even though it is stored as a text value rather than a numeric sequence.
• SYS_AWD_YR — the system award year. This is the most important business discriminator, as FISAP ranges are defined per award year and change with federal regulatory updates.
• PART_SECTION — identifies the FISAP part or section to which the income range applies, separating distinct reporting segments within the filing.
• DEPENDENCY_STATUS — distinguishes dependent versus independent student categories, a fundamental split in federal need-analysis methodology.
• START_RANGE_AMT and END_RANGE_AMT — the lower and upper income boundaries that define each bracket.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS who-columns providing audit lineage for each seeded row.

The unique index IGF_AW_FISAP_RANGES_U1 covers SYS_AWD_YR, PART_SECTION, DEPENDENCY_STATUS, START_RANGE_AMT, END_RANGE_AMT, which constitutes the true business key of the table. The surrogate primary key is therefore SEQUENCE_TXT, while the business key is the five-column combination above.

Common Use Cases and Queries

Because the table is pre-seeded and obsolete, the primary use cases are historical reporting, migration validation, and upgrade impact analysis. A representative query to retrieve all ranges for a given award year is:

• SELECT SYS_AWD_YR, PART_SECTION, DEPENDENCY_STATUS, START_RANGE_AMT, END_RANGE_AMT FROM IGF_AW_FISAP_RANGES WHERE SYS_AWD_YR = :award_year ORDER BY PART_SECTION, DEPENDENCY_STATUS, START_RANGE_AMT;
• A range-membership lookup that resolves an applicant's income into its FISAP bracket using a BETWEEN clause on START_RANGE_AMT and END_RANGE_AMT, constrained by award year, part section, and dependency status.
• Data-quality validation confirming that ranges do not overlap or leave gaps within each award year, part section, and dependency status grouping.
• Comparison queries joining to prior-year extracts to detect federal boundary changes between award years.

Reporting against this table should always be filtered by SYS_AWD_YR and PART_SECTION to avoid mixing ranges from different reporting contexts.

Related Objects

The ETRM metadata identifies this object as standalone, with no documented foreign keys to or from other tables. Consequently, related objects are inferred from the shared IGF FISAP and financial-aid domain rather than from explicit FK constraints. The most significant relationships are with FISAP processing tables that consume these ranges, award-year setup or configuration tables that supply SYS_AWD_YR, and any IGF need-analysis or applicant income tables that reference PART_SECTION and DEPENDENCY_STATUS. Because no FK columns are documented, joins must be constructed on the business-key columns SYS_AWD_YR, PART_SECTION, DEPENDENCY_STATUS, and the range amount pair rather than on SEQUENCE_TXT. Environments that never installed the IGF product will not contain this table, so dependency analysis should first verify its physical existence before attempting cross-object joins.