Search Results due_amount

Overview

IGSFV_PAY_PLAN_INSTALLMENTS is an Oracle E-Business Suite (EBS) read-only view owned by the APPS schema and registered as a VALID object within the IGS – Student System product. Its stated purpose is to hold information about student payment plan installments, consolidating installment schedules, due dates, monetary amounts, and student/party identification into a single queryable structure. The view is defined with a WITH READ ONLY clause, meaning it cannot be used as the target of DML; it exists exclusively for reporting, inquiry, and integration retrieval.

Because the view flattens installment-level detail from the payment plan installation tables and joins it with student plan attributes and trading community party data, it is well suited to concurrent programs, Oracle Reports, BI Publisher data templates, and custom SQL that must present a complete picture of a student's installment obligations without requiring the developer to reconstruct the multi-table join manually. Users searching on the "due_amount" concept will find that the view exposes the column DUE_AMT, which represents the amount due for an individual installment line.

Underlying Base Objects

The view text is defined as a join across three base objects:

• IGS_FI_PP_INSTLMNTS PP — the payment plan installment table, aliased PP, supplying installment identifiers, line number, due day, due month code, due year, due date, installment amount, due amount, penalty flag, and audit columns. This is the driving table and the source of the DUE_AMT column.
• IGS_FI_PP_STD_ATTRS STD — the student payment plan attributes table, joined on PP.STUDENT_PLAN_ID = STD.STUDENT_PLAN_ID. It contributes PERSON_ID, payment plan name, and plan start and end dates.
• HZ_PARTIES HZ — the Oracle Trading Community Architecture party table, joined on HZ.PARTY_ID = STD.PERSON_ID. It supplies PARTY_NUMBER and PARTY_NAME for the student or responsible party.

The join therefore links installment detail to plan-level attributes and then to party identity. Because the documented metadata lists no additional referenced base objects, dependencies are limited to these three tables.

Key Columns

• INSTALLMENT_ID / STUDENT_PLAN_ID / INSTALLMENT_LINE_NUM — primary identifier of the installment and its parent student plan, plus the line sequence within the plan.
• DUE_DAY, "_LA:DUE_MONTH", DUE_YEAR, DUE_DATE — the scheduled due timing of the installment. The DUE_MONTH column carries a descriptive flexfield-style lookup label referencing IGS_LOOKUP_VALUES with lookup type VS_CA_MONTH, exposing the month MEANING.
• INSTALLMENT_AMT — the expected amount for the installment line.
• DUE_AMT — the amount due for the installment, the column most directly associated with the "due_amount" search term.
• PENALTY_FLAG — indicates whether the installment is subject to penalty treatment.
• PERSON_ID, PARTY_NUMBER, PARTY_NAME — identification of the student or party responsible for the plan.
• PAYMENT_PLAN_NAME, PLAN_START_DATE, PLAN_END_DATE — plan-level descriptive and validity attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical scenarios include outstanding-installment reporting, due-date aging, penalty monitoring, and student-facing plan statements. The following query lists upcoming installment balances for a specific party:

SELECT party_number, party_name, payment_plan_name, installment_line_num, due_date, installment_amt, due_amt, penalty_flag FROM apps.igsfv_pay_plan_installments WHERE due_amt > 0 AND party_number = :p_party_number ORDER BY due_date, installment_line_num;

A second common pattern aggregates total due amounts by student plan:

SELECT student_plan_id, payment_plan_name, SUM(due_amt) total_due FROM apps.igsfv_pay_plan_installments GROUP BY student_plan_id, payment_plan_name;

Because the view is read-only and pre-joined, it removes the need to replicate the installment-to-plan-to-party join logic in every report and provides a stable reporting interface across EBS 12.1.1 and 12.2.2.