Results for “igs_pr_stdnt_pr_fnd”

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

Overview

IGS_PR_STDNT_PR_FND is a satellite table within the Oracle E-Business Suite IGS (Student System) product family. Its documented purpose is to store the exclude fund codes associated with a particular Student Progression Outcome (SPO) record. In functional terms, the table captures the funding sources that are explicitly excluded from a student's progression outcome determination, thereby supporting the business rule that certain awards or funding streams may not be applied toward a given outcome.

The ETRM metadata classifies this object, using heuristic Data Vault modeling, as satellite-leaning. This is a reasonable modeling suggestion: the table hangs off IGS_PR_STDNT_PR_OU_ALL via a composite foreign key and carries descriptive attributes (the FUND_CODE value plus standard audit columns) rather than defining its own independent business entity. It should therefore be understood as a dependent child, not as a hub or link in its own right.

Importantly, the ETRM documentation states that this object is Not implemented in this database, and the product is flagged as Obsolete in the 12.1.1 / 12.2.2 documentation set. This means it appears in the historical data model but is not physically present in a standard installation, and any reference to it in custom code or reports should be treated as legacy.

Key Information Stored

The table contains nine documented columns. The most important are the four that form the primary key and carry the business meaning of the record:

• PERSON_ID — identifies the student (person) to whom the progression outcome belongs. Also participates in the foreign key to IGS_PR_STDNT_PR_OU_ALL.
• COURSE_CD — the course code associated with the progression outcome record.
• SPO_SEQUENCE_NUMBER — the sequence number distinguishing individual Student Progression Outcome records for the same person and course.
• FUND_CODE — the exclude fund code itself. This is the attribute the user searched for, and it is the payload of the satellite: the value that records which funding source is excluded.

The remaining columns are the standard EBS audit fields: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. The unique index IGS_PR_STDNT_PR_FND_PK is defined on (PERSON_ID, COURSE_CD, SPO_SEQUENCE_NUMBER, FUND_CODE), making that composite the business-key candidate. No separate surrogate key column is documented; the primary key is the natural composite key.

Common Use Cases and Queries

Because the table is obsolete and not implemented, practical usage is largely limited to historical reporting, data migration reconciliation, and interpreting legacy customizations. Typical scenarios include identifying all fund codes excluded for a given student progression outcome, and determining whether a specific FUND_CODE has been excluded for a person/course combination.

A representative query joining the parent table on the documented foreign key columns:

• SELECT f.PERSON_ID, f.COURSE_CD, f.SPO_SEQUENCE_NUMBER, f.FUND_CODE FROM IGS_PR_STDNT_PR_FND f WHERE f.PERSON_ID = :person_id AND f.COURSE_CD = :course_cd;
• SELECT o.*, f.FUND_CODE FROM IGS_PR_STDNT_PR_OU_ALL o, IGS_PR_STDNT_PR_FND f WHERE o.PERSON_ID = f.PERSON_ID AND o.COURSE_CD = f.COURSE_CD AND o.SPO_SEQUENCE_NUMBER = f.SPO_SEQUENCE_NUMBER;

Reporting use cases center on exclusion analysis and audit trails, using LAST_UPDATE_DATE to track when an exclusion was last modified.

Related Objects

The most significant related object is the parent of the documented foreign key relationship:

• IGS_PR_STDNT_PR_OU_ALL — the Student Progression Outcome table. The foreign key maps PERSON_ID, COURSE_CD, and SPO_SEQUENCE_NUMBER from IGS_PR_STDNT_PR_FND to the corresponding columns in the parent table. This is the sole foreign key relationship documented in the ETRM metadata.
• IGS_PR_STDNT_PR_FND_PK — the primary key constraint/index, the anchor for any indexed lookup on the composite key.

Given the limited documented relationships, no additional dependent views or APIs are confirmed in the metadata. Any broader integration should be verified against the specific 12.1.1 or 12.2.2 instance, since the object is marked obsolete and not implemented.