Search Results igf_aw_tp_instmt

Overview

The view IGF_AW_TP_INSTMT belongs to the Oracle Financial Aid (IGF) product family within Oracle E-Business Suite, and is owned by the APPS schema. Its documented ETRM metadata classifies it as a VALID database view whose defining specification is recorded in the internal document FA125_3160568_CS_DP1.doc, which the metadata itself marks as Obsolete. Despite this designation, the view remains present and valid in the data dictionary for both the 12.1.1 and 12.2.2 releases.

Functionally, IGF_AW_TP_INSTMT is a reporting and integration view over the Financial Aid award disbursement instrumentation data. The "TP" naming convention in the IGF schema typically denotes third-party or disbursement-related processing entities, while "INSTMT" refers to instrument records that associate a financial aid fund with the calendar and sequence context used to schedule or track disbursement. The view's principal role is to expose organization-secured rows of the underlying instrumentation data to responsibility-level queries, reports, and concurrent programs, enforcing multi-org security through its WHERE predicate rather than duplicating the data.

Underlying Base Objects

The view is defined exclusively over a single underlying object: IGF_AW_TP_INSTMT_ALL, aliased as AINSTMT in the view text. The _ALL suffix indicates that the base table stores rows across all operating units, and the view exists to filter that combined dataset to the operating unit (ORG_ID) of the current session. No additional tables, joins, or synonyms are documented as referenced base objects in the ETRM metadata.

The filtering logic uses the historical multi-org security pattern based on USERENV('CLIENT_INFO'). The view compares the row's ORG_ID to the operating unit captured in the first ten characters of the client information string. Values are normalized with NVL, defaulting to -99 where no operating unit is present, so that rows belonging to the global or unrestricted context remain visible. Because the view selects AINSTMT.ROWID directly, it is updatable in principle, but the multi-org security predicate makes it most appropriate for query and reporting access.

Key Columns

• ROW_ID — The ROWID of the underlying IGF_AW_TP_INSTMT_ALL row, used as a direct row locator.
• FINST_ID — Identifier of the financial aid instrument to which the record belongs.
• LD_CAL_TYPE and LD_SEQUENCE_NUMBER — The load or lead calendar type and sequence that anchor the instrumentation record in the academic calendar.
• FUND_ID — The financial aid fund associated with the instrument.
• TP_CAL_TYPE and TP_SEQUENCE_NUMBER — The third-party or disbursement calendar type and sequence number.
• TP_OFFSET_DA — The offset in days applied when deriving the disbursement date from the reference calendar.
• TP_PERCT — The percentage of the award amount attributable to the third-party or disbursement event.
• MIN_CREDIT_PTS — Minimum credit points used as an eligibility threshold for the instrument.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ORG_ID — The operating unit that owns the row; this column drives the view's multi-org security filter.

Common Use Cases and Queries

Because the view automatically restricts rows to the caller's operating unit, it is typically queried in place of the _ALL table whenever session-level org security is required. Typical uses include award disbursement reports, validation of third-party instrument percentages, and reconciliation of funds against calendar-based disbursement schedules.

A basic listing scoped to the current operating unit:

• SELECT fund_id, finst_id, tp_cal_type, tp_sequence_number, tp_offset_da, tp_perct, min_credit_pts FROM igf_aw_tp_instmt WHERE finst_id = :finst_id;

Joining to fund and calendar reference data to resolve descriptive detail:

• SELECT i.fund_id, i.tp_cal_type, i.tp_offset_da, i.tp_perct FROM igf_aw_tp_instmt i WHERE i.org_id = :org_id AND i.ld_cal_type = :ld_cal_type ORDER BY i.tp_sequence_number;

Auditing recent changes to instrumentation records for a fund:

• SELECT finst_id, fund_id, last_updated_by, last_update_date FROM igf_aw_tp_instmt WHERE fund_id = :fund_id AND last_update_date >= :cutoff_date;

Given the obsolete status of the source specification, implementers should confirm the object's continued presence and behavior against the target instance before embedding it in custom reports, and should prefer supported public APIs or documented interfaces where available.