Search Results igs_fi_wav_pr_preqs_pk

Overview

The IGS_FI_WAV_PR_PREQS table is a core data structure within the Oracle E-Business Suite Student System (IGS) module. It functions as a relationship table designed to manage the hierarchical dependencies between different fee waiver programs. Specifically, it stores the prerequisite rules that define which waiver programs (the subordinate or "sub" programs) must be completed or satisfied before a student can be eligible for a higher-level waiver program (the superior or "sup" program) within a defined academic fee period. This table is essential for enforcing complex, multi-tiered fee waiver policies and ensuring proper sequencing in the application of financial concessions.

Key Information Stored

The table's structure centers on defining a prerequisite link between two waiver programs for a specific calendar instance. The key columns include:

• WAIVER_RELATION_ID: The system-generated primary key (PK) uniquely identifying each prerequisite rule.
• FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER: Together, these identify the academic calendar (or fee period) to which this specific prerequisite relationship applies.
• SUB_WAIVER_NAME: The name of the prerequisite (subordinate) waiver program that must be satisfied first.
• SUP_WAIVER_NAME: The name of the superior waiver program that requires the prerequisite.

The unique key constraint (U1) on FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, SUB_WAIVER_NAME, and SUP_WAIVER_NAME ensures that no duplicate prerequisite relationships are defined for the same fee period.

Common Use Cases and Queries

This table is primarily accessed during processes that validate a student's eligibility for a fee waiver. A common operational use case is when the system checks if all prerequisites for a target waiver program are met before approving an application. For reporting and administration, queries often focus on mapping the waiver hierarchy. A typical SQL pattern to list all prerequisite relationships for a given fee period would be:

SELECT sub_waiver_name AS prerequisite, sup_waiver_name AS target_waiver
FROM igs.igs_fi_wav_pr_preqs
WHERE fee_cal_type = :p_cal_type
AND fee_ci_sequence_number = :p_sequence_num
ORDER BY sup_waiver_name;

Another critical use case is impact analysis during a waiver program setup or modification, where administrators need to identify all superior programs that depend on a specific sub-waiver to understand the downstream effects of a change.

Related Objects

The IGS_FI_WAV_PR_PREQS table has a direct and exclusive relationship with the IGS_FI_WAIVER_PGMS table, which is the master table for all defined waiver programs. This is evidenced by two foreign key constraints:

• The combination of FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, and SUP_WAIVER_NAME references a valid record in IGS_FI_WAIVER_PGMS, identifying the superior waiver program.
• The combination of FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, and SUB_WAIVER_NAME also references a valid record in IGS_FI_WAIVER_PGMS, identifying the prerequisite waiver program.

This design ensures referential integrity, meaning a prerequisite rule cannot be created for a waiver program that does not exist for the specified fee period. Any application logic, API, or user interface managing waiver program prerequisites will interact with this table, and it is likely referenced by various Student System packages and views responsible for fee assessment and waiver processing.