Search Results igs_fi_pp_templates

Overview

The IGS_FI_PP_TEMPLATES table is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS) module, specifically designed for managing financial arrangements. Its primary role is to serve as a master repository for payment plan templates. These templates define the standard structure, terms, and conditions for installment-based payment schedules that can be applied to student fees and charges. As a master template, it allows for the consistent creation of individual student payment plans, ensuring uniformity in payment calculations, due dates, and associated processing rules across the institution. It is critical to note that the provided ETRM metadata explicitly labels the IGS - Student System as "Obsolete," indicating this table belongs to a legacy component of Oracle EBS 12.1.1 and 12.2.2, which may have been superseded by newer functionality in later releases or different product lines.

Key Information Stored

The table's central purpose is to define the attributes of a payment plan template. The primary key, PAYMENT_PLAN_NAME, uniquely identifies each template. Based on the foreign key relationships documented, a critical column is PROCESSING_FEE_TYPE. This column links to the IGS_FI_FEE_TYPE_ALL table, allowing the template to specify a particular fee type (e.g., a late payment fee or a plan setup fee) that is automatically processed or applied in conjunction with the payment plan. While the full column list is not provided in the excerpt, a table of this nature would typically store additional configuration details such as the plan's validity dates, the number of installments, calculation methods, grace period rules, and status indicators.

Common Use Cases and Queries

The primary use case is the administration and assignment of standardized payment schedules for student financial obligations. Administrators would create and maintain templates in this table, which are then used to generate specific plans for students. Common reporting and query scenarios include listing all active payment plan templates or analyzing template usage. A fundamental query would join the template to its related fee type for descriptive reporting.

SELECT ppt.payment_plan_name,
       ppt.description,
       ft.fee_type
FROM   igs_fi_pp_templates ppt,
       igs_fi_fee_type_all ft
WHERE  ppt.processing_fee_type = ft.fee_type
AND    SYSDATE BETWEEN ppt.start_date AND NVL(ppt.end_date, SYSDATE);

Another critical query would identify all student payment plan instances derived from a specific template by joining to the child IGS_FI_PP_STD_ATTRS table, which stores the student-specific application of the master template.

Related Objects

• IGS_FI_FEE_TYPE_ALL: A foreign key relationship exists via the PROCESSING_FEE_TYPE column. This links the payment plan template to a specific type of fee for automated processing.
• IGS_FI_PP_STD_ATTRS: This is a primary child table. It stores the individual student payment plan attributes that are instantiated based on a master template defined in IGS_FI_PP_TEMPLATES. The foreign key is PAYMENT_PLAN_NAME.
• IGS_FI_PP_TMPL_LNS: This is another primary child table. It likely stores the detailed installment lines (amounts, due dates, percentages) that constitute the schedule defined within the master payment plan template. The foreign key is PAYMENT_PLAN_NAME.