Search Results spnsr_stdnt_id




Overview
Explore in AI Chat

Overview

The table IGF.IGF_SP_STD_FC_ALL is a core data object within the Oracle EBS (Release 12.1.1 / 12.2.2) Grants Management module, specifically under the sponsor student funding schema (IGF). Its primary functional role is to store "pays only fee class details" for a given sponsor-student relationship. In the context of sponsored programs, a sponsor may agree to cover only specific categories of educational fees rather than all charges. This table serves as the definitive repository for such restricted fee arrangements. Each record links a sponsor-student relationship to one or more fee classes (e.g., Tuition, Books) along with associated percentage caps and maximum amount limits. The table is designed to support line-level detail for fee allocations, making it critical for calculating sponsor liability on student accounts.

Key Information Stored

The table contains several mandatory and business-critical columns, as documented in the ETRM metadata.

  • FEE_CLS_ID (NUMBER(15), Mandatory): The primary key, a system-generated unique sequence from IGF_SP_STD_FC_S. This is the unique identifier for each fee class record.
  • SPNSR_STDNT_ID (NUMBER(15), Mandatory): A foreign key to the sponsor-student relationship (IGF_SP_STDNT_REL_ALL). This column establishes which sponsor-student arrangement the fee class constraints apply to. It is also part of the unique index IGF_SP_STD_FC_ALL_U2.
  • FEE_CLASS (VARCHAR2(30), Mandatory): A system-defined lookup value that identifies the specific category of fees the sponsor will pay. Valid values include TUITION, COURSE, STUDENT, INSTITUTION, HOUSING, and BOOKS.
  • FEE_PERCENT (NUMBER): The percentage of eligible fee charges within the specified fee class that the sponsor will cover. This allows for partial sponsorship.
  • MAX_AMOUNT (NUMBER): A ceiling on the amount the sponsor will pay for that fee class, preventing over-liability even if the percentage calculation yields a higher value.
  • ORG_ID (NUMBER(15)): Multi-org operating unit identifier, enabling support for multi-tenant setups.
  • Standard Who Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): Standard Oracle EBS audit columns tracking user and timestamps for record creation and modification.

Common Use Cases and Queries

This table is heavily used in sponsor billing and student accounts receivable processes. Practical scenarios include determining a sponsor’s financial responsibility for a specific student term, calculating pro-rated allocations, and generating reports for sponsor invoicing.

Sample Query Pattern: Retrieve all fee classes and their percentage/amount limits for a given sponsor-student relationship.

SELECT 
    FC.FEE_CLASS,
    FC.FEE_PERCENT,
    FC.MAX_AMOUNT
FROM 
    IGF.IGF_SP_STD_FC_ALL FC
WHERE 
    FC.SPNSR_STDNT_ID = :p_spnsr_stdnt_id
ORDER BY 
    FC.FEE_CLASS;

Reporting Use Case: Combine with sponsor-student relationship and sponsor master data to produce a "Sponsor Coverage Report" per student, showing the breakdown of fee classes with coverage limits and actual charges.

Related Objects

Based on the ETRM relationship data and primary/foreign key documentation, the following direct dependencies exist:

  • Primary Key: IGF_SP_STD_FC_ALL_PK on column FEE_CLS_ID.
  • Foreign Key (Referenced Table): IGF_SP_STDNT_REL_ALL — The column SPNSR_STDNT_ID in this table points to the sponsor-student relationship record in IGF_SP_STDNT_REL_ALL. This is a mandatory parent-child link; a sponsor-student relationship must exist before fee class details can be defined.
  • Foreign Key (Referencing Table): IGF_SP_STD_PRG_ALL — The column FEE_CLS_ID in IGF_SP_STD_PRG_ALL references this table. This indicates that each fee class defined here can be linked to one or more sponsor student program records, potentially driving which program-specific fee schedules apply.
  • Unique Indexes:
    • IGF_SP_STD_FC_ALL_U1 — Unique on FEE_CLS_ID
    • IGF_SP_STD_FC_ALL_U2 — Unique on (SPNSR_STDNT_ID, FEE_CLASS), enforcing that a sponsor-student relationship can have only one record per fee class.

No other database objects were documented as referencing this table, though application-level dependencies (e.g., Forms, Reports) are typical but not captured in this metadata.