Results for “igf_sp_stdnt_rel”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view IGF_SP_STDNT_REL belongs to the IGF (Financial Aid) product family within Oracle E-Business Suite. In the ETRM 12.2.2 documentation, IGF is explicitly flagged as Obsolete, and the view itself is recorded as Not implemented in this database. The description characterizes it as an "MO VIEW based on IGF_SP_STDNT_ALL table," indicating that it was originally built as a Multi-Org (MO) reporting view intended to expose sponsor–student relationship data. The view name references the concept of a relationship between a sponsor and a student (SP / STDNT / REL), and it was designed to present that relationship data in a form suitable for inquiry, reporting, and integration within the financial aid subsystem.

Because the object is documented as obsolete and unimplemented, it should be understood primarily as a legacy artifact. Its structure nonetheless reflects the multi-org security pattern commonly used across EBS 12.1.1 and 12.2.2 reporting views.

Underlying Base Objects

The documented base object for this view is IGF_SP_STDNT_ALL, and the view text in the ETRM metadata confirms that the FROM clause selects from IGF_SP_STDNT_REL_ALL SPSTD. The aliased "_ALL" table represents the multi-org enabled base table, while the view applies an ORG_ID predicate to restrict rows to the operating unit of the current session. The _REL_ALL table serves as the physical store of sponsor–student relationship records, and the view exposes those rows through the standard MO security filter without any joins to additional objects. The metadata notes "Referenced base objects: none documented" for the documented view metadata entry, but the view text itself unambiguously identifies IGF_SP_STDNT_REL_ALL (described as based on IGF_SP_STDNT_ALL) as the sole source. No lookup or foreign-key joins are embedded in the view definition; all descriptive values must be resolved externally through other tables.

Key Columns

The view exposes a set of columns that map directly to the base table, with ROWID retained as ROW_ID:

• ROW_ID — The physical row identifier of the underlying record, used for direct addressing and update operations.
• SPNSR_STDNT_ID — Surrogate identifier for the sponsor–student relationship record, likely the primary key of the base table.
• FUND_ID — Identifier of the financial aid fund associated with the relationship.
• BASE_ID — Identifier linking the record to a base (award/base) definition.
• PERSON_ID — The person (typically the student) associated with the relationship.
• LD_CAL_TYPE, LD_SEQUENCE_NUMBER — Calendar type and sequence number identifying the academic period to which the relationship applies.
• TOT_SPNSR_AMOUNT — Total sponsor amount recorded for the relationship.
• MIN_CREDIT_POINTS, MIN_ATTENDANCE_TYPE — Minimum credit points and attendance type thresholds governing eligibility.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns.
• ORG_ID — The operating unit identifier used by the multi-org security predicate.

The multi-org filter uses USERENV('CLIENT_INFO'), decoded through SUBSTRB and TO_NUMBER, defaulting to -99 when no operating unit context is set. This matches the classic EBS 11i/12.1 MO view pattern and remains consistent in 12.2.2.

Common Use Cases and Queries

In environments where the object exists, the view is queried to retrieve sponsor–student relationships visible to the current operating unit. A typical query is:

• SELECT spnsr_stdnt_id, person_id, fund_id, tot_spnsr_amount FROM igf_sp_stdnt_rel WHERE org_id = :org_id;
• Reconciliation of sponsor amounts: SELECT fund_id, SUM(tot_spnsr_amount) FROM igf_sp_stdnt_rel GROUP BY fund_id;
• Filtering by academic period: SELECT * FROM igf_sp_stdnt_rel WHERE ld_cal_type = :cal AND ld_sequence_number = :seq;

Because the view carries no descriptive joins, reports frequently combine it with person, fund, and calendar tables to produce user-facing output. In current 12.1.1 and 12.2.2 installations the object is normally absent, since IGF is obsolete; queries against it will fail unless a legacy implementation was retained. As a result, it is generally referenced for historical understanding of financial aid data models rather than for new development, and any integration should target supported replacements instead. The view remains valuable as documentation of the original multi-org sponsor–student relationship design.