Search Results igf_aw_fseog_match_all




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGF_AW_FSEOG_MATCH_ALL is a Financial Aid (IGF) transactional setup table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It is owned by the IGF schema and holds the configuration that governs how Federal Supplemental Educational Opportunity Grant (FSEOG) matching funds are identified and applied to students within a given award year. Specifically, the table stores the funds eligible to act as matching contributions and the sequence in which those funds are consumed against a student's need. Because the FSEOG program requires institutions to contribute a matching share against federal allocations, this table provides the institutional control point for determining which internal fund sources satisfy that obligation and in what priority order.

The table participates in the standard Oracle multi-org model through the ORG_ID column, meaning rows are segmented by operating unit where Multi-Org Access Control is enabled. A heuristic Data Vault classification of this object suggests a satellite-leaning profile: it holds descriptive attributes (match sequencing) attached to a business key formed by the fund and the academic calendar instance, rather than acting as a pure hub or as a many-to-many link table.

Key Information Stored

The documented physical schema contains ten columns. The most significant are described below.

  • FUND_ID — Identifies the fund record that is eligible to serve as a matching source for FSEOG awards. This is the principal descriptive attribute of the row.
  • MATCH_ORDER — Numeric sequencing that determines the order in which matching funds are applied when multiple funds qualify for the same award year. Lower values are consumed first in the standard matching logic.
  • CI_CAL_TYPE and CI_SEQUENCE_NUMBER — The calendar type and sequence number identifying the academic calendar instance (award year) to which the matching configuration applies. Together these reference IGS_CA_INST_ALL and scope the configuration to a specific year and period.
  • ORG_ID — The operating unit that owns the row, supporting multi-org data segregation and security.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Oracle who-audit columns capturing row creation and modification history.

The surrogate primary key is IGF_AW_FSEOG_MATCH_PK, defined over (FUND_ID, CI_CAL_TYPE, CI_SEQUENCE_NUMBER), guaranteeing that a fund is configured at most once per calendar instance. Two unique indexes act as business-key candidates. IGF_AW_FSEOG_MATCH_ALL_U1 mirrors the primary key columns, while IGF_AW_FSEOG_MATCH_ALL_U2 spans (CI_CAL_TYPE, CI_SEQUENCE_NUMBER, MATCH_ORDER, ORG_ID), enforcing that match order is unique per calendar instance and operating unit. Note that IGF_AW_FSEOG_MATCH_UK is documented separately over (CI_CAL_TYPE, CI_SEQUENCE_NUMBER, MATCH_ORDER), confirming that no two funds may share the same match order within a year.

Common Use Cases and Queries

Typical uses include auditing FSEOG match configuration prior to award disbursement, validating that match orders are contiguous and unique, and reporting which internal funds are committed to federal matching in a given award year.

To list the match sequence for a specific award year:

  • SELECT FUND_ID, MATCH_ORDER, ORG_ID FROM IGF.IGF_AW_FSEOG_MATCH_ALL WHERE CI_CAL_TYPE = :cal_type AND CI_SEQUENCE_NUMBER = :seq AND ORG_ID = :org_id ORDER BY MATCH_ORDER;

To detect duplicate match orders within an operating unit (a data-integrity check that should return no rows):

  • SELECT CI_CAL_TYPE, CI_SEQUENCE_NUMBER, MATCH_ORDER, ORG_ID, COUNT(*) FROM IGF.IGF_AW_FSEOG_MATCH_ALL GROUP BY CI_CAL_TYPE, CI_SEQUENCE_NUMBER, MATCH_ORDER, ORG_ID HAVING COUNT(*) > 1;

Because the table is configuration rather than transactional, queries are commonly embedded in validation reports run at the start of an award year and in reconciliation scripts comparing configured match funds against actual disbursement records.

Related Objects

The most significant related objects are:

  • IGS_CA_INST_ALL — The calendar instance table; joined on CI_CAL_TYPE and CI_SEQUENCE_NUMBER to resolve the award year. This is the documented foreign key relationship for the table.
  • IGF_AW_FSEOG_MATCH_ALL (self-referencing logic) — The unique index IGF_AW_FSEOG_MATCH_ALL_U2 and the IGF_AW_FSEOG_MATCH_UK constraint both enforce integrity against other rows in this table.
  • Fund master tables within IGF — Referenced through FUND_ID to retrieve fund descriptions and attributes for reporting.
  • FSEOG award and disbursement tables in the IGF module — Consume this configuration to determine matching amounts during award packaging and disbursement processing.
  • ORG_ID-based operating unit views — Multi-org secured views that restrict visibility of these configuration rows by operating unit.

Any extension or interface that inserts match configuration rows must respect both the primary key and the business-key unique constraints, particularly the uniqueness of MATCH_ORDER per calendar instance and operating unit.