Search Results igs_pe_pers_prefs_u1

Overview

IGS.IGS_PE_PERS_PREFS_ALL is a transactional table in the Oracle E-Business Suite Student System (OSS) schema IGS, delivered under FND Design Data object IGS.IGS_PE_PERS_PREFS_ALL. It stores user-level defaults and "last used" preferences captured during the two principal student data-entry flows: the record enrollments process and the direct admissions process, along with an enquiry flow. Rather than representing a business entity in its own right, the row is a persistent snapshot of the context that a user last worked with, allowing the OSS forms to pre-populate academic calendar types, calendar instances, admission and enrolment categories, and enrollment methods on subsequent visits.

The table is described in the ETRM metadata as being satellite-leaning in a Data Vault heuristic classification. This is a modeling suggestion only: the object's grain is one row per person, keyed by a single primary key, and it is functionally dependent on the person rather than describing an independent relationship or event. In Data Vault terms it behaves like a satellite attached to a person hub (the equivalent of HZ_PARTIES). The status is VALID in the documented 12.1.1 physical schema, and it resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10.

Key Information Stored

All documented columns number 23. The most operationally significant are listed here, grouped by function:

• PERSON_ID — the mandatory surrogate primary key, described as "identifier that uniquely identifies a person". It is the single-column target of both the primary key IGS_PE_PERS_PREFS_PK and the unique index IGS_PE_PERS_PREFS_U1, making it the only documented business-key candidate; there is no composite alternate key.
• Record enrollments preferences: ENR_ACAD_CAL_TYPE, ENR_ACAD_SEQUENCE_NUMBER, ENR_ENROLMENT_CAT, and ENR_ENR_METHOD_TYPE hold the last academic calendar type and sequence number, enrollment category, and enrollment method used in the record enrollments flow.
• Direct admissions preferences: ADM_ACAD_CAL_TYPE, ADM_ACAD_CI_SEQUENCE_NUMBER, ADM_ADM_CAL_TYPE, ADM_ADM_CI_SEQUENCE_NUMBER, ADM_ADMISSION_CAT, and ADM_S_ADMISSION_PROCESS_TYPE capture the equivalent last-used academic and admission calendar data plus the admission category and process type.
• Enquiry flow preferences: ENQ_ACAD_CAL_TYPE, ENQ_ACAD_CI_SEQUENCE_NUMBER, ENQ_ADM_CAL_TYPE, and ENQ_ADM_CI_SEQUENCE_NUMBER.
• Operational defaults: SERVER_PRINTER_DFLT and ALLOW_STND_REQ_IND, plus ORG_ID for multi-organization security.
• Standard Who columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The primary consumption pattern is form-driven retrieval of a user's prior context. A typical point lookup joins the preference row to the party to resolve the person:

• Pre-populating a data-entry form: SELECT enr_acad_cal_type, enr_acad_sequence_number, enr_enrolment_cat, enr_enr_method_type FROM igs_pe_pers_prefs_all WHERE person_id = :p_person_id;
• Resolving the person identity: SELECT h.party_name FROM igs_pe_pers_prefs_all p, hz_parties h WHERE p.person_id = h.party_id AND p.person_id = :p_person_id;
• Auditing recent activity: filtering on LAST_UPDATE_DATE to identify persons whose admissions or enrollment defaults were recently modified.
• Admissions reporting: aggregating by ADM_ADMISSION_CAT or ADM_S_ADMISSION_PROCESS_TYPE to profile the categories most recently used by staff processing direct admissions.
• Enquiry analysis: using ENQ_ADM_CAL_TYPE and ENQ_ACAD_CAL_TYPE to determine which calendar contexts are most frequently referenced during enquiry processing.

Because the table is one row per person and updated in place, there is no history; joins to enrollment or admissions transaction tables are required for point-in-time reporting.

Related Objects

The documented foreign key links this object to the Trading Community Architecture registry:

• HZ_PARTIES — IGS_PE_PERS_PREFS_ALL.PERSON_ID references the party record; this is the only documented FK and establishes the person identity behind the preference row.
• IGS_PE_PERS_PREFS_PK and IGS_PE_PERS_PREFS_U1 — the primary key constraint and unique index, both on PERSON_ID, enforcing one preference row per person.
• Process-level dependencies implied by the column semantics include the record enrollments and direct admissions forms and their associated academic calendar and admission calendar setup tables (referenced by the %_CAL_TYPE columns), which supply the valid values stored here.

Collectively, these relationships position IGS_PE_PERS_PREFS_ALL as a lightweight person satellite that supports the OSS user interface layer rather than the transactional enrollment or admissions record itself.