Search Results igs_pe_pers_prefs_all




Overview
Explore in AI Chat

Overview

IGS_PE_PERS_PREFS_ALL is a transactional preference table within the Oracle E-Business Suite Student System (IGS) product family. It stores per-person preferences that govern how the institution processes student records across the enrolment, admissions, and enquiry cycles. The documented description identifies one of its primary responsibilities as recording "Record Enrolments Session Details," meaning the table captures default academic calendar, sequence, and category selections that drive enrolment session behaviour for each person record.

The table resides in the IGS schema and is classified as VALID in the ETRM repository. It contains 23 columns and is indexed by a single unique constraint, IGS_PE_PERS_PREFS_U1, on PERSON_ID. The primary key constraint is IGS_PE_PERS_PREFS_PK, also defined on PERSON_ID, which enforces a one-row-per-person cardinality.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. This is consistent with the table's design: PERSON_ID acts as the business key inherited from the party hub, while the descriptive preference columns represent changing descriptive attributes over time. A Data Vault implementation would typically model this as a satellite hanging off the HZ_PARTIES hub.

Key Information Stored

The table is oriented around a small number of functional preference groups, each keyed to an academic construct.

The DBA-relevant distinction here is that PERSON_ID is both the surrogate primary key and the unique business-key candidate — no separate hidden sequence identifier exists to decouple the surrogate from the business key.

Common Use Cases and Queries

Typical use cases include verifying that a person has enrolment preferences captured before allowing enrolment activity, reporting on default admissions calendar assignments, and auditing which users have customised printer preferences.

  • Retrieve the full preference record for a given person:

    SELECT * FROM igs.igs_pe_pers_prefs_all WHERE person_id = :p_person_id;

  • Identify persons with a specific enrolment method or category:

    SELECT person_id, enr_acad_cal_type, enr_enrolment_cat FROM igs.igs_pe_pers_prefs_all WHERE enr_enrolment_cat = :p_cat;

  • Audit recent preference changes using the WHO columns:

    SELECT person_id, last_updated_by, last_update_date FROM igs.igs_pe_pers_prefs_all WHERE last_update_date >= :p_from_date;

These queries are commonly embedded in concurrent programs, OAF pages, and custom PL/SQL packages that support the enrolment and admissions functional flows.

Related Objects

The FK graph is explicitly narrow: the only documented foreign key is IGS_PE_PERS_PREFS_ALL.PERSON_ID referencing HZ_PARTIES. This establishes the table as a dependent child of the party model.

  • HZ_PARTIES — Parent of the sole documented foreign key; joined on PERSON_ID to obtain party number, name, and party type.
  • IGS_PE_PERS_PREFS_PK — The primary key constraint enforcing uniqueness of PERSON_ID.
  • IGS_PE_PERS_PREFS_U1 — The unique index on PERSON_ID that acts as the business-key candidate.
  • IGS academic calendar and calendar instance tables — Referenced implicitly by the ENR_, ADM_, and ENQ_ academic calendar type and sequence columns.
  • IGS enrolment, admissions, and enquiry processing APIs — Consume these preference rows to determine session defaults during student transaction processing.

Because the object carries only one documented FK, downstream dependencies are represented mainly through the academic calendar and category values stored within its columns rather than through additional foreign key constraints.