Search Results igs_pe_unt_requirmnt
Overview
The IGS_PE_UNT_REQUIRMNT table is a core data object within the Oracle E-Business Suite Student System (IGS) for releases 12.1.1 and 12.2.2. It functions as a detailed repository for academic encumbrance or hold requirements. Specifically, it describes the individual course units (subjects) that a student is mandated to complete as a condition of a specific encumbrance placed on their academic record. This table enables the system to track and enforce precise, unit-level study requirements that must be satisfied for a student to have a hold released, linking high-level encumbrance conditions to the granular curriculum.
Key Information Stored
The table's structure centers on uniquely identifying a student's encumbrance and the required unit within that context. Its primary key is a composite of several columns, ensuring a unique requirement per encumbrance effect. Critical columns include PERSON_ID (the student), ENCUMBRANCE_TYPE and PEN_START_DT (identifying the specific hold), and S_ENCMB_EFFECT_TYPE, PEE_START_DT, and PEE_SEQUENCE_NUMBER (identifying the particular effect or condition of that hold). The UNIT_CD column stores the code of the mandated unit of study, linked to the IGS_PS_UNIT table. The PUR_START_DT column is also part of the primary key, likely indicating the effective start date of this specific unit requirement.
Common Use Cases and Queries
This table is primarily accessed for administrative reporting and process automation related to student academic standing. Common use cases include generating a list of all outstanding unit requirements for students under an academic probation hold, verifying completion of encumbrance conditions during degree audit or clearance processes, and data feeds for academic advising dashboards. A typical query would join to person and encumbrance header tables to retrieve a student's required units.
- Sample Query: To find all required units for a specific student's encumbrance:
SELECT req.unit_cd, u.unit_name FROM igs_pe_unt_requirmnt req JOIN igs_ps_unit u ON req.unit_cd = u.unit_cd WHERE req.person_id = :person_id AND req.encumbrance_type = :enc_type; - Reporting Use Case: Creating an "Encumbrance Requirements Audit" report that maps students, their hold types, and the specific unit mandates that remain incomplete.
Related Objects
The IGS_PE_UNT_REQUIRMNT table maintains defined foreign key relationships with two key tables in the Student System, as documented in the ETRM metadata:
- IGS_PE_PERSENC_EFFCT: This is the parent table for encumbrance effects. The relationship is enforced via the columns PERSON_ID, ENCUMBRANCE_TYPE, PEN_START_DT, S_ENCMB_EFFECT_TYPE, PEE_START_DT, and PEE_SEQUENCE_NUMBER. Each unit requirement must be associated with a valid encumbrance effect record.
- IGS_PS_UNIT: This is the master table for academic units. The relationship is through the UNIT_CD column, ensuring that any unit specified as a requirement exists in the institution's curriculum catalog.
These relationships ensure referential integrity, meaning a unit requirement cannot exist without a corresponding encumbrance effect and a valid unit definition.
-
Table: IGS_PE_UNT_REQUIRMNT
12.2.2
product: IGS - Student System (Obsolete) , description: Describes units that are required to be studied by the student as part of a hold , implementation_dba_data: Not implemented in this database ,
-
Table: IGS_PS_UNIT
12.2.2
product: IGS - Student System (Obsolete) , description: This attribute describes the code allocated to a unit offered by the university. , implementation_dba_data: Not implemented in this database ,
-
Table: IGS_PE_PERSENC_EFFCT
12.2.2
product: IGS - Student System (Obsolete) , description: This entity describes the effects which are imposed on a person (or one or their courses) as part on an encumbrance. eg. course exclusion, suppression of transcript. , implementation_dba_data: Not implemented in this database ,