Search Results igs_fi_pp_std_attrs




Overview
Explore in AI Chat

Overview

The IGS_FI_PP_STD_ATTRS table is a core data object within the Oracle E-Business Suite Student System (IGS) for releases 12.1.1 and 12.2.2. It functions as the central repository for the master attributes of individual student payment plans. A payment plan is a financial arrangement that allows a student to pay assessed fees in structured installments over time. This table stores the defining parameters and status of each active or historical plan, serving as the primary parent record for all associated installment and billing data. Its role is critical for managing student accounts receivable, automating billing processes, and enforcing financial holds within the institution's operational workflow.

Key Information Stored

The table's structure captures essential plan metadata. The primary identifier is STUDENT_PLAN_ID. Critical foreign key columns link the plan to other master data: PERSON_ID (HZ_PARTIES) identifies the student, and PAYMENT_PLAN_NAME (IGS_FI_PP_TEMPLATES) references the template used for creation. The PLAN_STATUS_CODE indicates the current lifecycle state (e.g., Active, Closed, Cancelled). Key date columns include PLAN_START_DATE and PLAN_END_DATE, which define the plan's validity period. Financial attributes are stored via foreign keys to FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER (IGS_CA_INST_ALL) for the fee calendar, PROCESSING_FEE_TYPE (IGS_FI_FEE_TYPE_ALL) for applicable charges, and INVOICE_ID (IGS_FI_INV_INT_ALL) for associated invoices. These columns collectively define the who, what, when, and how of a student's payment obligation structure.

Common Use Cases and Queries

A primary use case is generating reports on active payment plans for a term or student cohort. For example, to list all active plans for a specific fee calendar, a query would join IGS_FI_PP_STD_ATTRS to IGS_CA_INST_ALL and filter by PLAN_STATUS_CODE and calendar instance. Another critical scenario is troubleshooting billing or hold issues, where support personnel trace from a student's identifier (PERSON_ID) to their plan details and related installment records. A common SQL pattern involves selecting from this table and joining to IGS_FI_PP_INSTLMNTS to analyze upcoming or overdue installments. Data from this table is also essential for interfaces with external general ledger or cash management systems, where plan summaries are extracted for reconciliation.

Related Objects

The IGS_FI_PP_STD_ATTRS table maintains integral relationships with several key objects via foreign key constraints, as documented in the ETRM.

  • Parent/Dependency Tables: It references master data from HZ_PARTIES (PERSON_ID), IGS_FI_PP_TEMPLATES (PAYMENT_PLAN_NAME), IGS_CA_INST_ALL (FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER), IGS_FI_FEE_TYPE_ALL (PROCESSING_FEE_TYPE), and IGS_FI_INV_INT_ALL (INVOICE_ID).
  • Child Tables: It is the parent table for transactional data in IGS_FI_BILL_P_PLANS (via STUDENT_PLAN_ID), IGS_FI_PERSON_HOLDS (via STUDENT_PLAN_ID), and IGS_FI_PP_INSTLMNTS (via STUDENT_PLAN_ID). These tables store the generated billing schedules, financial holds triggered by the plan, and the individual installment records, respectively.

These relationships enforce data integrity and are fundamental to any data model or custom report involving student payment plans.