Search Results igf_sp_std_prg_all

Overview

The table IGF_SP_STD_PRG_ALL is a core data object within the Oracle E-Business Suite (EBS) Financial Aid module (IGF). It serves as a master repository for student-level "pays only" program details, which are directly linked to specific tuition fee classes. In the context of financial aid administration, a "pays only" arrangement typically refers to a financial obligation or program where the student is responsible for payment, often outside of standard aid packages. This table is critical for defining and managing the relationship between a student's fee class and the specific academic program (course and version) for which the pays-only terms apply. Its role is to establish a precise link between a financial structure (fee class) and an academic curriculum, enabling accurate assessment and tracking of student financial responsibilities.

Key Information Stored

The table's structure is designed to enforce data integrity and define unique program assignments within a fee class. The primary key is the system-generated identifier, FEE_CLS_PRG_ID, which uniquely identifies each record. The table's unique key constraint highlights the critical business rule: for a given fee class (FEE_CLS_ID), the combination of a specific academic course (COURSE_CD) and its version (VERSION_NUMBER) must be unique. This prevents duplicate program definitions within the same financial context. Therefore, the most significant columns are:

• FEE_CLS_PRG_ID: The unique system identifier for the pays-only program record.
• FEE_CLS_ID: Foreign key linking to the parent student fee class (IGF_SP_STD_FC_ALL).
• COURSE_CD: The code identifying the academic course associated with the pays-only program.
• VERSION_NUMBER: The version of the specified academic course.

Common Use Cases and Queries

This table is central to queries that need to list or report on all academic programs tied to a student's specific pays-only fee class. A common operational use case is validating program setup during financial aid packaging or when generating student invoices. For reporting, it enables analysis of which courses and versions are most frequently associated with student-pays arrangements. A fundamental query pattern involves joining to the parent fee class table to get student and fee class context, and potentially to course catalog tables for descriptive information.

-- Example: Retrieve all pays-only programs for a specific fee class
SELECT prg.fee_cls_prg_id,
       prg.course_cd,
       prg.version_number
FROM   igf_sp_std_prg_all prg
WHERE  prg.fee_cls_id = :p_fee_cls_id
ORDER BY prg.course_cd;

Another critical use case involves data integrity checks, such as identifying fee classes that have no associated programs or validating the uniqueness of course-version combinations per the UK constraint.

Related Objects

The table exists within a defined hierarchy of financial aid tables, with explicit foreign key relationships as documented in the ETRM.

• Parent Table (Referenced by IGF_SP_STD_PRG_ALL):
  • IGF_SP_STD_FC_ALL: The student fee class table. The column IGF_SP_STD_PRG_ALL.FEE_CLS_ID is a foreign key to this table, establishing that every pays-only program must belong to a valid, pre-existing fee class.
• Child Table (References IGF_SP_STD_PRG_ALL):
  • IGF_SP_STD_UNIT_ALL: The student unit details table. It references this program table via the column IGF_SP_STD_UNIT_ALL.FEE_CLS_PRG_ID. This relationship indicates that individual unit records (likely representing credit units or billing units) are granularly assigned to a specific pays-only program record.

This structure shows a clear data flow: Fee Class (IGF_SP_STD_FC_ALL) → Program Details (IGF_SP_STD_PRG_ALL) → Unit Details (IGF_SP_STD_UNIT_ALL).