Results for “igs_pe_fund_excl”

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

Overview

The IGS_PE_FUND_EXCL table belongs to the IGS product family — the Student System module, now classified as obsolete in Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is to store Person Hold Effect Fund Exclusion Details, meaning it records which funding sources (FUND_CODE) are excluded from encumbrance or hold-processing effects associated with a specific person's encumbrance effect record. In effect, it acts as a filtering rulebook: when the student system evaluates how a person-level hold affects fund encumbrances, the rows in this table determine which funds are exempt from that effect and over what effective date range.

From a data-modeling perspective, the provided metadata classifies this object as satellite-leaning. This is a heuristic suggestion rather than an Oracle-certified classification. The table describes attributes and validity windows that hang off a parent business entity (PERSON_ID plus the composite encumbrance-effect key), which is characteristic of satellite behavior: descriptive, time-bound detail attached to a hub or link. It is not itself a hub (no stand-alone business identity beyond the surrogate key) and not a link (it does not primarily resolve many-to-many relationships between independent entities).

Key Information Stored

The table contains 15 documented columns. The most significant are:

• FUND_EXCL_ID — the surrogate primary key, backed by unique index IGS_PE_FUND_EXCL_PK. This is the fastest, most selective access path for single-row lookups.
• PERSON_ID — the person (student or staff member) to whom the fund exclusion applies. It is also part of the foreign key to IGS_PE_PERSENC_EFFCT.
• ENCUMBRANCE_TYPE — the category of encumbrance the exclusion governs.
• FUND_CODE — the specific fund that is excluded from the hold/encumbrance effect.
• PEN_START_DT — the start date of the parent person-encumbrance-effect record.
• S_ENCMB_EFFECT_TYPE — the encumbrance effect type, part of the composite business key.
• PEE_START_DT and PEE_SEQUENCE_NUMBER — the start date and sequence of the person-encumbrance-effect row, together with S_ENCMB_EFFECT_TYPE forming the join back to the parent.
• PFE_START_DT — the start date of this fund-exclusion row itself, defining when the exclusion becomes effective.
• EXPIRY_DT — the date on which the exclusion ceases to apply.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns tracking row provenance and change history.

Two unique indexes are documented: IGS_PE_FUND_EXCL_U1 on FUND_EXCL_ID alone, and IGS_PE_FUND_EXCL_U2 on the composite of PERSON_ID, ENCUMBRANCE_TYPE, PEN_START_DT, S_ENCMB_EFFECT_TYPE, PEE_START_DT, PEE_SEQUENCE_NUMBER, FUND_CODE, PFE_START_DT. The composite index is the true business key — it enforces that a given fund exclusion for a person/effect combination is unique by effective start date, enabling date-ranged (Type 2 style) history.

Common Use Cases and Queries

Typical uses include eligibility reporting, encumbrance troubleshooting, and fund-posting exception analysis. A straightforward lookup by the searched column is:

• SELECT * FROM IGS_PE_FUND_EXCL WHERE FUND_EXCL_ID = :fund_excl_id;
• Point-in-time eligibility: WHERE PERSON_ID = :id AND :asof BETWEEN PFE_START_DT AND NVL(EXPIRY_DT, :asof) to return only exclusions active on a given date.
• Fund-level audit: group by FUND_CODE and ENCUMBRANCE_TYPE to identify which funds are most frequently excluded and for which effect types.
• Join back to the parent effect table to report the person's encumbrance context alongside each exclusion.

Related Objects

• IGS_PE_PERSENC_EFFCT — the primary parent, joined on PERSON_ID, ENCUMBRANCE_TYPE, PEN_START_DT, S_ENCMB_EFFECT_TYPE, PEE_START_DT, and PEE_SEQUENCE_NUMBER. This is the FK documented in the metadata and the dominant relationship for this table.
• Person / student core tables referenced through PERSON_ID (for example person and person-name views) supply demographic context in reports.
• Fund definition / fund code validation objects resolve FUND_CODE to a descriptive fund name for reporting.
• Encumbrance effect type lookups resolve ENCUMBRANCE_TYPE and S_ENCMB_EFFECT_TYPE to readable values.

Because the product is marked obsolete and the table is documented as "not implemented in this database," confirm its existence in any specific instance before relying on it. Where present, the foreign key to IGS_PE_PERSENC_EFFCT is the most reliable join path, and the composite unique index supports full history-aware reporting.