Search Results igs_pe_unt_requirmnt_u1

Overview

The IGS_PE_UNT_REQUIRMNT table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically in the IGS (Integrated Student Management) schema. It serves a critical function in the student encumbrance management system. The table's primary purpose is to define and track specific academic units (courses) that a student is mandated to complete as a direct consequence of an imposed encumbrance or hold. This creates a formal link between a disciplinary or administrative action and a concrete academic requirement, enabling institutions to enforce structured remediation or compliance paths for affected students.

Key Information Stored

The table stores a combination of encumbrance identifiers, unit details, and audit information. Key columns include the composite foreign key that uniquely identifies the parent encumbrance effect: PERSON_ID, ENCUMBRANCE_TYPE, PEN_START_DT, S_ENCMB_EFFECT_TYPE, PEE_START_DT, and PEE_SEQUENCE_NUMBER. The core academic data is held in UNIT_CD (the code of the required unit) and the user-searched field PUR_START_DT, which signifies the date the specific unit requirement becomes effective. The EXPIRY_DT column indicates when the requirement ceases to be in force. Standard FND "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide full auditability.

Common Use Cases and Queries

A primary use case is generating reports for academic advisors or disciplinary boards listing all unit requirements currently active for a student under an encumbrance. Another is to validate student course enrollment against mandated requirements. A common query pattern involves filtering by effective dates. For example, to find all active unit requirements for a specific student as of today:

• SELECT UNIT_CD, PUR_START_DT, EXPIRY_DT FROM IGS.IGS_PE_UNT_REQUIRMNT WHERE PERSON_ID = :person_id AND PUR_START_DT <= SYSDATE AND (EXPIRY_DT IS NULL OR EXPIRY_DT >= SYSDATE);

To investigate the specific encumbrance effect that triggered a requirement, a join to the parent person encumbrance effect table is essential, using the composite key columns defined in the unique index IGS_PE_UNT_REQUIRMNT_U1.

Related Objects

The table's structure indicates a strong dependency on a parent table defining the person encumbrance effect. While not explicitly named in the provided metadata, the composite unique index (IGS_PE_UNT_REQUIRMNT_U1) clearly defines the foreign key relationship. The joining columns are: S_ENCMB_EFFECT_TYPE, PEN_START_DT, PERSON_ID, ENCUMBRANCE_TYPE, PEE_START_DT, and PEE_SEQUENCE_NUMBER. This table is likely referenced by IGS academic planning and progression engines to check for unsatisfied encumbrance-related unit requirements. The non-unique index IGS_PE_UNT_REQUIRMNT_N1 on UNIT_CD facilitates queries searching for all students required to take a particular unit due to an encumbrance.