Search Results igf_sp_std_unit_all

Overview

The table IGF_SP_STD_UNIT_ALL is a data object within the Oracle E-Business Suite (EBS) module for Financial Aid, specifically the IGF module, which is documented as obsolete. This table serves as a core repository for managing unit-level details within a "student pays only" program. Its primary role is to define and store the specific academic units (e.g., courses, credits) that are associated with a given pays-only fee classification program, enabling the system to calculate and assess charges at a granular level for students enrolled in such programs. The presence of the '_ALL' suffix indicates the table is designed to support a multi-org architecture, storing data for multiple operating units.

Key Information Stored

The table's structure centers on uniquely identifying a unit within a specific program. The documented columns forming its primary and unique keys are critical. The FEE_CLS_UNIT_ID column serves as the primary unique identifier for each row. The combination of FEE_CLS_PRG_ID, UNIT_CD, and VERSION_NUMBER forms a separate unique key, ensuring that within a specific pays-only program (FEE_CLS_PRG_ID), a given unit code (UNIT_CD) is uniquely defined per version. This design supports version control for unit definitions within a program over time. While other descriptive columns for the unit are not detailed in the provided metadata, they would typically include data such as unit description, charge amount, effective dates, and status.

Common Use Cases and Queries

This table is central to operations involving the setup and inquiry of pays-only program structures. A common use case is the administrative setup of a new academic term, where a financial aid officer defines which specific course units are billable under a particular pays-only program. For reporting and validation, queries often join this table to its parent program table to list all units for a program or to verify unit details for a student's enrollment. A sample query to retrieve all active units for a specific program would be:

• SELECT unit.unit_cd FROM igf_sp_std_unit_all unit, igf_sp_std_prg_all prg WHERE unit.fee_cls_prg_id = prg.fee_cls_prg_id AND prg.program_cd = '&PROGRAM_CODE' AND SYSDATE BETWEEN unit.start_date AND unit.end_date;

Another critical use case is during the batch process of generating student charges, where the system references this table to determine the correct unit-based fees to apply.

Related Objects

The primary documented relationship for IGF_SP_STD_UNIT_ALL is with its parent table, IGF_SP_STD_PRG_ALL. This foreign key relationship is fundamental to the data model.

• IGF_SP_STD_PRG_ALL: This is the parent table that holds the header definition for the student pays-only program. The relationship is enforced by the foreign key where IGF_SP_STD_UNIT_ALL.FEE_CLS_PRG_ID references a corresponding FEE_CLS_PRG_ID in IGF_SP_STD_PRG_ALL. Any unit detail record must be associated with a valid, pre-existing program record in this parent table.

Given the table's purpose, it is also logically related to student enrollment and transactional fee tables (e.g., IGF_AW_FEE_CLS_STD) which would consume the unit definitions to calculate actual charges, though these specific relationships are not detailed in the provided excerpt.