Results for “pen_start_dt”

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

Overview

IGS_PE_UNT_REQUIRMNT is a table within the IGS — Student System module of Oracle E-Business Suite. The ETRM documentation classifies the product as Obsolete, and the implementation note states that the table is not implemented in this database for the reference environment, meaning the object is documented for completeness but its physical presence depends on the specific deployment and patch level. In Oracle EBS 12.1.1 and 12.2.2, IGS objects formed the backbone of the Student Systems / People Enterprise data model used by higher-education institutions that deployed the Oracle Student System product line.

The table's purpose is to describe the units that a student is required to study as part of a hold or encumbrance. Functionally, it captures the intersection between a person-level encumbrance (a restriction placed against a student) and the specific academic units affected by that restriction. The heuristic Data Vault classification mined from the foreign-key structure is a link. This is a reasonable modeling suggestion: the object resolves a many-to-many association between persons/encumbrances and study units, rather than serving as a standalone business key hub or a descriptive satellite.

Key Information Stored

The primary key is IGS_PE_UNT_REQUIRMNT_PK, a composite key. A unique index, IGS_PE_UNT_REQUIRMNT_U1, carries the identical column set, confirming the composite business key. The documented metadata lists 14 columns, of which the most significant are:

• PERSON_ID — Identifies the student against whom the encumbrance and required-unit specification applies. This is the anchor searched through pen_start_dt context.
• ENCUMBRANCE_TYPE — The category of hold or restriction governing the required units.
• PEN_START_DT — The effective start date of the person encumbrance. Because this column participates in both the PK and the unique index, it defines the version of the encumbrance record in effect.
• S_ENCMB_EFFECT_TYPE — The encumbrance effect type, qualifying how the hold behaves.
• PEE_START_DT and PEE_SEQUENCE_NUMBER — Identify the specific person-encumbrance effect row, providing date and sequence discrimination.
• UNIT_CD — The code of the study unit that the student is required to complete.
• PUR_START_DT — The start date of the required-unit specification, a further temporal qualifier.
• EXPIRY_DT — The date on which the requirement lapses.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit lineage.

Common Use Cases and Queries

The dominant access pattern involves retrieving the units required for a held student as of a given date. Because PEN_START_DT is a key component, date-bounded queries are typical:

• Enumerating required units for a person and encumbrance type effective on a specific date, filtering on PEN_START_DT <= :p_date and (EXPIRY_DT IS NULL OR EXPIRY_DT > :p_date).
• Joining to IGS_PS_UNIT on UNIT_CD to retrieve unit titles, credit values, and owning organisational units for reporting.
• Joined to IGS_PE_PERSENC_EFFCT to obtain full encumbrance context for student-advisor dashboards or registrar exception reports.
• Data-migration or reconciliation extracts keyed on the composite unique index when comparing legacy holdings to 12.2.2 instances.

Related Objects

Two foreign keys are documented, each identifying a parent object:

• IGS_PE_PERSENC_EFFCT — Referenced via the composite FK columns PERSON_ID, ENCUMBRANCE_TYPE, PEN_START_DT, S_ENCMB_EFFECT_TYPE, PEE_START_DT, and PEE_SEQUENCE_NUMBER. This is the principal parent and defines the encumbrance effect to which required units attach.
• IGS_PS_UNIT — Referenced via UNIT_CD. Provides the unit master definitions behind each requirement row.

These two relationships define the table's role as a link bridging student encumbrances and study units, and they should be treated as the authoritative join paths for any query against this object.