Search Results pee_sequence_number




Overview
Explore in AI Chat

Overview

The IGS_PE_FUND_EXCL table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically in the IGS (Oracle Student Management) product family. It serves as the definitive repository for person-level fund exclusions linked to institutional holds (encumbrances). The table's primary role is to manage and track specific fund codes that are excluded from being applied to a student's account due to an active hold and its associated effect. This ensures that financial aid, billing, or other fund-related processes adhere to institutional policies and restrictions imposed by holds, maintaining data integrity within the student financial ecosystem.

Key Information Stored

The table stores a combination of unique identifiers, hold information, and fund exclusion details. The primary key, FUND_EXCL_ID, is a system-generated unique identifier for each exclusion record. The table's structure links a person (PERSON_ID) to a specific hold instance via the ENCUMBRANCE_TYPE and PEN_START_DT columns. It further drills down to a particular effect of that hold using S_ENCMB_EFFECT_TYPE, PEE_START_DT, and PEE_SEQUENCE_NUMBER. The core business data is the FUND_CODE, which identifies the specific fund being excluded, along with the effective date range for this exclusion defined by PFE_START_DT and EXPIRY_DT. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are present for auditing.

Common Use Cases and Queries

A primary use case is validating fund eligibility during financial transactions, such as applying a payment or a charge. A process would query this table to check if a given fund code is excluded for a student under any active hold effect. Reporting use cases include generating lists of students with active fund exclusions for audit purposes or analyzing the impact of specific hold types. A typical query to find all active fund exclusions for a person would be:

  • SELECT FUND_CODE, ENCUMBRANCE_TYPE, PFE_START_DT, EXPIRY_DT FROM IGS.IGS_PE_FUND_EXCL WHERE PERSON_ID = :person_id AND (EXPIRY_DT IS NULL OR EXPIRY_DT >= SYSDATE);

Another common pattern involves joining to person and hold tables to create a comprehensive report, using the unique constraint on person and hold effect columns (IGS_PE_FUND_EXCL_U2) as a reliable join condition.

Related Objects

Based on the provided dependency information, the IGS_PE_FUND_EXCL table is referenced by an object within the APPS schema named IGS_PE_FUND_EXCL. This is typically a public synonym, granting global access to the underlying IGS table. The metadata indicates no foreign key dependencies from this table, but its unique constraints imply strong logical relationships. The PERSON_ID column logically relates to a person master table (e.g., IGS_PE_PERSON). The combination of ENCUMBRANCE_TYPE, PEN_START_DT, S_ENCMB_EFFECT_TYPE, PEE_START_DT, and PEE_SEQUENCE_NUMBER forms a composite foreign key to a person encumbrance effects table (e.g., IGS_PE_PERSENC_EFFCT), establishing the critical link between a fund exclusion and the specific hold effect that mandates it.