Results for “igs_pe_fund_source”

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

Overview

The IGS_PE_FUND_SOURCE table resides in the IGS schema and belongs to the Oracle E-Business Suite IGS – Student System product family, delivered under the ETRM 12.1.1 physical schema and carried forward into 12.2.2. It stores details of a person's funding source information — the financial sponsors, agencies, employers, or government bodies that underwrite a student's tuition, fees, or related charges. Each row associates a funding source record with a party held in the Trading Community Architecture (TCA) via PERSON_ID, allowing Student System transactions such as billing, receivables, and financial aid disbursement to attribute balances to the correct sponsor.

From a Data Vault modeling perspective, the heuristic classification of this table is satellite-leaning. This suggests the table behaves primarily as a descriptive satellite keyed to a hub or link (the person/party), rather than as an independent hub of its own. Analysts designing a warehouse layer may treat FUND_SOURCE_ID as the driving surrogate while resolving PERSON_ID to the party hub.

Key Information Stored

The documented schema exposes 13 columns. The most significant include:

• FUND_SOURCE_ID — surrogate primary key, enforced by the IGS_PE_FUND_SOURCE_PK constraint and additionally backed by the unique index IGS_PE_FUND_SOURCE_U1. Because a unique index also exists on this column, it is documented as the business-key candidate as well as the technical key.
• PERSON_ID — foreign key to HZ_PARTIES, tying the funding source to a TCA party record. This is the principal integration point between IGS funding data and the shared party model.
• FUND_SOURCE_CODE — a coded identifier used for classification and lookup of the funding type.
• NAME — the descriptive name of the funding source sponsor or program.
• AMOUNT — the monetary value associated with the funding source, used in billing and aid calculations.
• RELATIONSHIP_CODE — captures how the funding source relates to the person (for example, employer or agency relationship).
• DOCUMENT_IND — a flag indicating document-related status for the funding arrangement.
• NOTES — free-text supplementary information recorded by administrative staff.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS WHO-column audit attributes tracking row provenance and change history.

Common Use Cases and Queries

Typical reporting scenarios include identifying all funding sources tied to a student or party, aggregating sponsored amounts, and reconciling funding data against deliverable records. A representative join to the party model follows:

• SELECT f.FUND_SOURCE_ID, f.NAME, f.AMOUNT, p.PARTY_NAME FROM IGS_PE_FUND_SOURCE f, HZ_PARTIES p WHERE f.PERSON_ID = p.PARTY_ID;
• Filtering by FUND_SOURCE_CODE to group sponsors by category.
• Auditing recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because the unique index mirrors the primary key column, lookups by FUND_SOURCE_ID are index-driven and efficient.

Related Objects

The following objects are most significant in the relationship graph:

• HZ_PARTIES — referenced through IGS_PE_FUND_SOURCE.PERSON_ID, the only documented outward foreign key.
• AMS_DELIVERABLES_ALL_B — references this table via FUND_SOURCE_ID, linking funding sources to deliverable records in the marketing/advanced module.
• The IGS_PE_FUND_SOURCE_PK constraint and IGS_PE_FUND_SOURCE_U1 unique index, which enforce key integrity.

Together these relationships position IGS_PE_FUND_SOURCE as a focal reference point connecting student funding to both the TCA party hub and downstream deliverable tracking.