Search Results installment_method_flag




Overview

The IGS_FI_PP_TEMPLATES table is a core master data repository within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Financials (IGS) module. It serves as the definitive source for storing template definitions for institutional payment plans. These templates provide a reusable framework for structuring installment-based payment schedules, which can be applied to students or other entities. The table's role is to define the rules, parameters, and financial terms of a payment plan, such as installment frequency, due dates, and associated fees, enabling consistent and automated billing processes across the institution.

Key Information Stored

The table's columns define the complete configuration of a payment plan template. The primary key, PAYMENT_PLAN_NAME, uniquely identifies each template. Critical business rule columns include INSTALLMENT_PERIOD_CODE (e.g., Monthly, Quarterly), DUE_DAY_OF_MONTH, and DUE_END_OF_MONTH_FLAG, which collectively determine installment due dates. Financial parameters are captured in BASE_AMT (the total plan amount), PROCESSING_FEE_TYPE, and PROCESSING_FEE_AMT. The CLOSED_FLAG indicates whether the template is active for use, while INSTALLMENT_METHOD_FLAG governs how payments are allocated. Standard Oracle EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit trails.

Common Use Cases and Queries

Primary use cases include the administration of payment plan templates, reporting on available plan structures, and supporting data validation during the assignment of a plan to a student. A common reporting requirement is to list all active templates. The following query pattern, based on the provided ETRM excerpt, is fundamental for data extraction and integration tasks:

  • Retrieving all template details: SELECT PAYMENT_PLAN_NAME, PAYMENT_PLAN_DESC, CLOSED_FLAG, INSTALLMENT_PERIOD_CODE, BASE_AMT FROM IGS.IGS_FI_PP_TEMPLATES;
  • Finding active templates for a specific installment period: SELECT PAYMENT_PLAN_NAME, PAYMENT_PLAN_DESC FROM IGS.IGS_FI_PP_TEMPLATES WHERE CLOSED_FLAG = 'N' AND INSTALLMENT_PERIOD_CODE = 'MONTHLY';
  • Validating the existence of a specific template, a key step when the user searches by PAYMENT_PLAN_NAME: SELECT * FROM IGS.IGS_FI_PP_TEMPLATES WHERE PAYMENT_PLAN_NAME = '<plan_name>';

Related Objects

According to the provided dependency information, the IGS_FI_PP_TEMPLATES table does not reference other objects but is referenced by other database objects within the IGS schema. This indicates it functions as a parent or master table. While the specific child tables are not listed in the excerpt, in a typical Oracle EBS Financials setup, this template table would be referenced by transactional tables that create specific payment plan instances for students or customers. These child tables would likely store a foreign key to PAYMENT_PLAN_NAME to inherit the template's rules. The existence of a unique primary key index (IGS_FI_PP_TEMPLATES_PK on PAYMENT_PLAN_NAME) enforces data integrity for these relationships.