Search Results igf_aw_fund_feeclas_uk

Overview

The table IGF_AW_FUND_FEECLAS_ALL is a core data object within the Oracle E-Business Suite (EBS) Financial Aid module (IGF). It serves as a critical junction table that establishes and manages the mapping relationship between financial aid funds and institutional fee classes. Its primary role is to define which specific fees, categorized by fee class, a particular financial aid fund is authorized to cover. This mapping is essential for the accurate and automated application of aid to student charges, ensuring compliance with fund-specific regulations and institutional policies. The table is designed with multi-org architecture, as indicated by the '_ALL' suffix and the presence of the ORG_ID column, allowing it to store data for multiple operating units within a single installation.

Key Information Stored

The table's structure is designed to enforce unique mappings and maintain referential integrity. The key columns include FCLASS_ID, which is the system-generated primary key for each unique mapping record. The FUND_ID column is a foreign key that links to the specific aid fund defined in the IGF_AW_FUND_MAST_ALL table. The FEE_CLASS column stores the code identifying the type of fee (e.g., tuition, health service, technology fee) that the fund can satisfy. The ORG_ID column identifies the operating unit, a standard EBS construct for multi-org support. The uniqueness constraint (IGF_AW_FUND_FEECLAS_UK) on the combination of FEE_CLASS, FUND_ID, and ORG_ID prevents duplicate fee class assignments for a given fund within an operating unit.

Common Use Cases and Queries

This table is central to processes that determine aid eligibility against specific cost components. A common operational use case is during the packaging or disbursement process, where the system references these mappings to calculate how much of a student's assessed fees can be paid by each awarded fund. For reporting and administrative analysis, queries often join this table to the fund master and fee setup tables. A typical SQL pattern retrieves all fee classes eligible for coverage by a specific fund: SELECT fee_class FROM igf_aw_fund_feeclas_all WHERE fund_id = :fund_id AND org_id = :org_id;. Conversely, to identify all funds that can pay a particular type of fee, one would query: SELECT fund_id FROM igf_aw_fund_feeclas_all WHERE fee_class = :fee_class AND org_id = :org_id;. This data is vital for fund utilization reports and auditing aid applications against fee assessments.

Related Objects

The table maintains a direct and critical foreign key relationship with the core fund definition table. The documented relationship is:

• Foreign Key to IGF_AW_FUND_MAST_ALL: The FUND_ID column in IGF_AW_FUND_FEECLAS_ALL references the primary key in the IGF_AW_FUND_MAST_ALL table. This ensures that every fee class mapping is associated with a valid, existing financial aid fund. Any join for reporting or data validation between fee classes and fund details would utilize this relationship: SELECT fmast.*, fclas.fee_class FROM igf_aw_fund_mast_all fmast JOIN igf_aw_fund_feeclas_all fclas ON fmast.fund_id = fclas.fund_id;. The table is also inherently related to the foundation tables defining the valid list of FEE_CLASS codes, though this specific lookup relationship is not detailed in the provided metadata.