Search Results match_order




Overview
Explore in AI Chat

Overview

IGF.IGF_AW_FSEOG_MATCH_ALL is a transactional configuration table in the Oracle E-Business Suite Financial Aid (IGF) schema. It stores the setup that governs how Federal Supplemental Educational Opportunity Grant (FSEOG) matching funds are defined and the sequence in which those funds are packaged for a specific award year. Each row associates a matching fund with an award year and assigns it a packaging order, giving financial aid administrators deterministic control over the order in which FSEOG awards draw against available funds.

The entity is scoped by award year, expressed through the CI_CAL_TYPE and CI_SEQUENCE_NUMBER columns, and by organization through ORG_ID, so the same matching fund can be configured differently across award years and operating units. The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and its indexes are stored in APPS_TS_TX_IDX, consistent with a transaction-oriented setup table.

Based on the documented foreign key relationship to IGS_CA_INST_ALL, the heuristic Data Vault classification for this object is satellite-leaning. It describes attributes of a fund-in-award-year context rather than acting as a pure hub of business keys or a pure many-to-many link, so it is best modeled as descriptive context attached to the matching fund and award year combination.

Key Information Stored

The table contains ten documented columns. The most significant include:

  • FUND_ID (NUMBER 15) — the matching fund identifier for an FSEOG fund. This is a core business key column.
  • MATCH_ORDER (NUMBER 10) — the order in which the funds are packaged, defining the priority sequence used by the packaging engine.
  • CI_CAL_TYPE (VARCHAR2 10) — the award year identifier expressed as a calendar type.
  • CI_SEQUENCE_NUMBER (NUMBER) — the award year identifier expressed as a sequence number.
  • ORG_ID (NUMBER 15) — the organizational identifier, supporting multi-org security and partitioning of the setup by operating unit.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns that track record provenance and change history.

The documented primary key is IGF_AW_FSEOG_MATCH_PK, composed of FUND_ID, CI_CAL_TYPE, and CI_SEQUENCE_NUMBER. Two unique indexes act as business-key candidates: IGF_AW_FSEOG_MATCH_ALL_U1 on (FUND_ID, CI_CAL_TYPE, CI_SEQUENCE_NUMBER), which mirrors the primary key; and IGF_AW_FSEOG_MATCH_ALL_U2 on (CI_CAL_TYPE, CI_SEQUENCE_NUMBER, MATCH_ORDER, ORG_ID), which enforces that the packaging order is unique within an award year and organization. The U2 index is the object most commonly associated with the search term "igf_aw_fseog_match_all_u2" and is the constraint that prevents two funds from occupying the same match order in the same award year and org.

Common Use Cases and Queries

Typical uses include reviewing and auditing the configured FSEOG matching funds, verifying packaging priority, and diagnosing packaging errors caused by duplicate match orders. A common query retrieves the ordered setup for a given award year and organization:

  • List funds in packaging sequence: 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 ORDER BY MATCH_ORDER;
  • Detect gaps or duplicates in match order using a HAVING COUNT check on MATCH_ORDER grouped by award year and ORG_ID.
  • Trace a specific fund's placement across award years by filtering on FUND_ID.
  • Join to award-year calendars to resolve the calendar type and sequence into a readable year label.

Reporting use cases include FSEOG packaging compliance reports, year-over-year comparison of matching fund priorities, and multi-org setup validation across operating units.

Related Objects

The documented dependency data identifies the following relationships:

  • IGS_CA_INST_ALL — referenced through CI_CAL_TYPE, providing the award year calendar instance context for the match setup.
  • APPS.IGF_AW_FSEOG_MATCH_ALL — the APPS-layer synonym/view that applications and reports query in place of the IGF base table.

In practice, fund-level detail is resolved by joining FUND_ID to the financial aid fund definition tables in the IGF schema, and organizational context is resolved through ORG_ID against the operating unit definitions used throughout EBS multi-org security.