Search Results igf_sp_unit_all_u2




Overview

The IGF_SP_UNIT_ALL table is a core data structure within the Oracle E-Business Suite (EBS) Student Financials module, specifically for versions 12.1.1 and 12.2.2. As documented, its primary role is to hold "pays only unit details for a pays only program." In the context of institutional financial management, a "pays only" program typically refers to a sponsorship or billing arrangement where a third party (e.g., an employer or government agency) is responsible for paying student fees for specific courses or units. This table stores the permissible units and their associated financial caps under such programs, enabling the system to validate charges and manage sponsor liabilities accurately.

Key Information Stored

The table's columns store essential configuration and transactional data for sponsored units. The primary business keys are FEE_CLS_PRG_ID, which links to the parent sponsorship program, and UNIT_CD, which identifies the specific academic unit. The VERSION_NUMBER allows for maintaining historical changes to unit definitions within a program. The critical financial attribute is MAX_AMOUNT, which defines the maximum sponsor amount payable for that unit. Standard EBS audit columns (CREATED_BY, CREATION_DATE, etc.) track record history, and the ORG_ID column supports multi-org architecture by segregating data by operating unit. The table is enforced with two unique constraints: one on the surrogate key (FEE_CLS_UNIT_ID) and another on the business key combination of FEE_CLS_PRG_ID, UNIT_CD, and VERSION_NUMBER.

Common Use Cases and Queries

This table is central to processes involving sponsored student fees. Common use cases include validating if a student's enrolled unit is covered under their sponsorship program during charge assessment, determining the sponsor's financial liability cap for reporting, and maintaining the catalog of units approved for a given sponsor program. A typical query to retrieve all units for a specific program, including their financial limits, would be:

  • SELECT UNIT_CD, VERSION_NUMBER, MAX_AMOUNT FROM IGF.IGF_SP_UNIT_ALL WHERE FEE_CLS_PRG_ID = :program_id ORDER BY UNIT_CD;

For reporting on sponsor program configurations, a join to the parent program table (likely keyed on FEE_CLS_PRG_ID) is standard. Integration and data migration scripts often reference this table to populate or verify sponsored unit rules.

Related Objects

Based on the provided dependency metadata, the IGF_SP_UNIT_ALL table is referenced by the APPS synonym of the same name (APPS.IGF_SP_UNIT_ALL), which is the standard access point for EBS application code and reports. The documentation indicates it does not reference other objects but is referenced by others. The key relationship is a foreign key from the parent "pays only program" table (the specific name is not listed but is logically keyed on FEE_CLS_PRG_ID) to the FEE_CLS_PRG_ID column in this table. This establishes a one-to-many relationship where one program can have many associated units. The unique constraint IGF_SP_UNIT_ALL_U2 on (FEE_CLS_PRG_ID, UNIT_CD, VERSION_NUMBER) is critical for maintaining data integrity within this relationship.