Search Results igs_pe_pers_encumb_v




Overview
Explore in AI Chat

Overview

The view IGS_PE_PERS_ENCUMB_V belongs to the IGS product family — the Oracle Student System module set. Within the ETRM documentation it is classified as IGS - Student System (Obsolete), and the metadata records it as "Not implemented in this database." Its purpose is to present person-level encumbrances (holds, blocks, or restrictions placed against an individual) together with the descriptive attributes needed for reporting: who the encumbrance applies to, who authorised it, the authorising responsibility, its validity window, and any external reference. The view is a denormalised, read-oriented projection rather than a base transactional entity.

For users searching on person_number, this view is significant because it exposes the person number twice: once for the encumbered person and once for the authorising person. This makes it directly usable in reports that need to identify people by their human-readable student or person identifier rather than by internal PERSON_ID surrogate keys.

Underlying Base Objects

The view text joins a single base table with four supporting objects:

No referenced base objects were separately documented in the ETRM metadata, so the joins above are derived from the published view text. The outer joins make the view tolerant of missing authorisers, responsibilities, or external reference lookups.

Key Columns

Common Use Cases and Queries

Typical uses include institutional reporting on active student holds, auditing who authorised each encumbrance, and integration extracts that publish encumbrance data keyed by person number.

SELECT person_number,
       encumbrance_type,
       start_dt,
       expiry_dt,
       authorising_person_number,
       auth_resp_name
FROM   igs_pe_pers_encumb_v
WHERE  person_number = :p_person_number
AND    TRUNC(SYSDATE) BETWEEN start_dt AND NVL(expiry_dt, TRUNC(SYSDATE));

Because the module is flagged obsolete and the view is recorded as not implemented in the documented database, any code depending on it should be reviewed against the target 12.1.1 or 12.2.2 instance before deployment.