Search Results igs_ps_fee_trg




Overview
Explore in AI Chat

Overview

The IGS_PS_FEE_TRG table is a core data entity within the Oracle E-Business Suite Student System (IGS) module. It defines program-based fee triggers, which are critical rules used during the automated fee assessment process. This table establishes the linkage between specific academic programs (courses) and applicable fee types, allowing the system to determine when a particular program-based fee should be charged to a student. Its role is to store the conditional logic that, when a student's enrollment matches the defined criteria, triggers the assessment of a fee associated with a specific fee calendar and category. This functionality is essential for managing complex tuition and fee structures in higher education institutions.

Key Information Stored

The table stores the combination of attributes that constitute a unique fee trigger rule for a program. The primary key columns define the core rule: FEE_CAT, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, FEE_TYPE, COURSE_CD, and SEQUENCE_NUMBER. These columns identify the specific fee calendar instance and fee category/type being triggered, along with the precise academic program (course) and a sequence to allow multiple rules. Additional key columns refine the trigger conditions, including ATTENDANCE_MODE (e.g., full-time, part-time), ATTENDANCE_TYPE (e.g., on-campus, distance), LOCATION_CD (campus location), and CAL_TYPE (the academic calendar type for the program). The FEE_TRIGGER_GROUP_NUMBER column allows for grouping related triggers for processing logic.

Common Use Cases and Queries

The primary use case is the batch fee assessment engine, which queries this table to identify all program-based fees applicable to a student's enrolled course, attendance pattern, location, and calendar. Administrators may query it to audit or report on fee rules. A common reporting query would join this table to course and fee definition tables to list all fees triggered by a specific program. For troubleshooting, one might query for triggers related to a specific fee type to understand why it is being assessed. A sample SQL pattern to find all fee triggers for a course would be: SELECT * FROM igs.igs_ps_fee_trg WHERE course_cd = '<COURSE_CODE>' ORDER BY fee_cat, fee_type; Another pattern validates triggers by joining to the referenced foreign key tables to ensure data integrity: SELECT t.* FROM igs_ps_fee_trg t WHERE NOT EXISTS (SELECT 'x' FROM igs_ps_course c WHERE c.course_cd = t.course_cd);

Related Objects

The IGS_PS_FEE_TRG table maintains integral relationships with several foundational tables in the Student System, as documented by its foreign keys. Its primary relationship is with IGS_PS_COURSE via the COURSE_CD column, linking the trigger to the academic program. For fee definition, it references IGS_FI_F_CAT_FEE_LBL_ALL and IGS_FI_FEE_TRG_GRP using the composite key of FEE_CAT, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, and FEE_TYPE. To define student attendance conditions, it references IGS_EN_ATD_MODE_ALL (ATTENDANCE_MODE) and IGS_EN_ATD_TYPE_ALL (ATTENDANCE_TYPE). The location condition is tied to IGS_AD_LOCATION_ALL (LOCATION_CD), and the program calendar condition references IGS_CA_TYPE (CAL_TYPE). These relationships ensure the trigger is validated against existing configuration data.