Search Results waiver_percent_alloc

Overview

The IGS_FI_WAIVER_PGMS table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Student Management (Campus Solutions) or Financial Aid modules. It serves as the master repository for defining and storing all fee waiver programs configured in the system. A waiver program is a rule set that allows for the reduction or forgiveness of student charges. The table's role is to centrally define the parameters of these programs, including their applicability to specific academic periods and fee types, the method of calculation, status, and associated financial components. This definition drives the operational logic for applying waivers to student accounts.

Key Information Stored

The table's columns define the comprehensive attributes of a waiver program. Key columns include the composite primary key (FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, WAIVER_NAME) which uniquely identifies a program within a specific fee calendar instance. The TARGET_FEE_TYPE indicates the primary student charge to which the waiver applies. The WAIVER_METHOD_CODE dictates whether waivers are created manually ('Manual') or automatically via a system rule ('Computation Rule'). For rule-based waivers, the RULE_FEE_TYPE column is critical, as it specifies the source fee type used by the computation engine to determine the waiver amount. Other essential attributes include the WAIVER_CRITERIA_CODE ('Fee Balance' or 'Computed Amount'), WAIVER_PERCENT_ALLOC for percentage-based calculations, and links to related financial objects like the ADJUSTMENT_FEE_TYPE and CREDIT_TYPE_ID.

Common Use Cases and Queries

This table is central to fee waiver administration and reporting. Common operational scenarios include auditing active waiver programs for a term, troubleshooting waiver computation issues, and generating reports on available financial concessions. A typical query involves joining to fee type and calendar tables to get descriptive information. For example, to find all active, computation-based waiver programs for a specific fee calendar that use a particular RULE_FEE_TYPE:

• SELECT waiver_name, waiver_desc, target_fee_type, rule_fee_type, waiver_percent_alloc FROM igs.igs_fi_waiver_pgms WHERE fee_cal_type = :p_cal_type AND fee_ci_sequence_number = :p_ci_seq AND waiver_status_code = 'Active' AND waiver_method_code = 'Computation Rule' AND rule_fee_type = :p_rule_fee_type;

Another common pattern is to analyze the relationship between target and rule fee types across all programs to understand the financial data flow within the waiver engine.

Related Objects

The IGS_FI_WAIVER_PGMS table has defined relationships with several other key tables, primarily through foreign key constraints. It references master data tables to ensure integrity: IGS_CA_INST_ALL (for the fee calendar instance), IGS_FI_CR_TYPES_ALL (for the credit type), and IGS_FI_FEE_TYPE_ALL (for the ADJUSTMENT_FEE_TYPE, RULE_FEE_TYPE, and TARGET_FEE_TYPE). Crucially, it is referenced by child tables that store the execution details of these programs, such as IGS_FI_WAV_STD_PGMS, which likely stores student-specific waiver program assignments or instances, and IGS_FI_WAV_PR_PREQS, which presumably defines prerequisites for a waiver program. These relationships form the backbone of the waiver processing data model.