Search Results igf_aw_tp_instmt_v

Overview

IGF_AW_TP_INSTMT_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the IGF (Financial Aid) product family. In the ETRM documentation for releases 12.1.1 and 12.2.2, the view is flagged as obsolete; the source document reference FA125_3160568_CS_DP1.doc carries an explicit "Obsolete" designation. Despite that status, the view remains VALID in the data dictionary and continues to expose a joined, denormalized projection of the award disbursement installment rule data.

The view presents Term Payment (TP) installment configuration alongside the corresponding Loan Disbursement (LD) calendar instance. Rather than requiring a caller to resolve calendar identifiers manually, the view surfaces both the LD and TP calendar type, sequence number, alternate code, and start/end dates in a single row. This makes it a convenience layer for reporting and integration scenarios where payment schedules must be correlated against the academic or disbursement calendar. It is typical of the views used to drive inquiry screens, concurrent report extracts, and interfaces that pass disbursement timing rules to downstream financial systems.

Underlying Base Objects

The view is defined over three documented base objects joined on calendar identity:

• IGF_AW_TP_INSTMT FINST — the driving table holding the term payment installment rule, including the LD and TP calendar references, the offset days, the payment percentage, and the minimum credit points.
• IGS_CA_INST LD_CAL — the calendar instance resolved for the loan disbursement (LD) calendar type and sequence number.
• IGS_CA_INST TP_CAL — the calendar instance resolved for the term payment (TP) calendar type and sequence number.

The join predicates require that FINST.LD_CAL_TYPE equals LD_CAL.CAL_TYPE and FINST.LD_SEQUENCE_NUMBER equals LD_CAL.SEQUENCE_NUMBER, with a parallel pair of predicates linking FINST.TP_CAL_TYPE and FINST.TP_SEQUENCE_NUMBER to TP_CAL. Because a single row must resolve both calendar instances, records whose calendar identifiers do not exist in IGS_CA_INST are silently excluded from the result set. No base objects beyond these three are documented for this view.

Key Columns

The projection exposes identifier, rule, and audit columns:

• ROW_ID, FUND_ID, FINST_ID — primary and foreign key identifiers for the installment rule record and its owning fund.
• LD_CAL_TYPE, LD_SEQUENCE_NUMBER, LD_ALTERNATE_CODE, LD_START_DATE, LD_END_DATE — the loan disbursement calendar instance attributes. Note that the underlying column names START_DT and END_DT are aliased to LD_START_DATE and LD_END_DATE in the view header.
• TP_CAL_TYPE, TP_SEQUENCE_NUMBER, TP_ALTERNATE_CODE, TP_START_DT, TP_END_DT — the term payment calendar instance attributes.
• TP_OFFSET_DA, TP_PERCT, MIN_CREDIT_PTS — the operative rule values: the offset in days, the payment percentage, and the minimum credit points threshold.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns for the installment rule row.

Common Use Cases and Queries

Typical usage centers on validating disbursement schedules against calendar dates and on exporting rule configurations for reconciliation. A representative query retrieves active installment rules for a fund with both calendar windows resolved:

SELECT fund_id, finst_id, tp_perct, tp_offset_da, min_credit_pts, ld_alternate_code, ld_start_date, ld_end_date, tp_alternate_code, tp_start_dt, tp_end_dt FROM igf_aw_tp_instmt_v WHERE fund_id = :fund_id ORDER BY tp_start_dt;

A second pattern compares the two calendar windows to detect misconfigured offsets where the term payment window falls outside the loan disbursement window, which is a frequent cause of disbursement failures in financial aid processing. Because the view is documented as obsolete, new development should target the underlying base tables directly, and any existing dependent report or interface should be inventoried before the view is removed in a future release.