Search Results adm_s_admission_process_type




Overview

IGS_PE_PERS_PREFS is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It belongs to the Student Information Management / PeopleSoft-style "IGS" (Integrated Graduate System / Student System) family of objects used within Oracle Student System and related CRM admission modules. The view exposes person-level preference defaults — the operational settings that control how an individual user or person interacts with enrolment, admissions, and enquiry processing screens. Its central role is to provide a stable, Multi-Org-secured read interface over the underlying preference table so that forms, concurrent programs, and integrations can retrieve admission and enrolment context defaults without directly querying the base table. The column adm_s_admission_process_type, which the user searched for, is surfaced here as a preference indicating the default admission process type that applies to the person's admission activities.

Underlying Base Objects

The view text shows it is defined with a simple projection over a single base table:

  • IGS_PE_PERS_PREFS_ALL — the source table, referenced as tab in the SELECT statement. The _ALL suffix confirms it is a Multi-Org (operating unit) enabled table, carrying an ORG_ID column.
  • Although the ETRM metadata lists "Referenced base objects: none documented," the view definition itself explicitly names igs_pe_pers_prefs_all as the sole source. No joins to descriptor or lookup tables appear in the view text.
  • Row identity is preserved through TAB.ROWID AS ROW_ID, and standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are carried through unchanged.

The WHERE clause applies the standard EBS Multi-Org security predicate, comparing ORG_ID against the operating unit derived from USERENV('CLIENT_INFO'), defaulting to -99 when no client context is set. This means the view returns only rows for the currently selected operating unit (or the -99 sentinel when Org context is absent).

Key Columns

Common Use Cases and Queries

Typical uses include retrieving a person's default admission process type, populating admission/enrolment form defaults, and integration extracts that require person preference settings. Because the view enforces Org security, callers must set an operating unit context (via FND_GLOBAL or the client info) before querying.

  • Retrieve the admission process type for a person:
    SELECT person_id, adm_s_admission_process_type FROM apps.igs_pe_pers_prefs WHERE person_id = :p_person_id;
  • List all preference defaults for an operating unit:
    SELECT person_id, adm_admission_cat, enr_enrolment_cat FROM apps.igs_pe_pers_prefs WHERE org_id = :p_org_id;
  • Filter by a specific admission process type to identify affected persons:
    SELECT person_id FROM apps.igs_pe_pers_prefs WHERE adm_s_admission_process_type = :p_process_type;

Because it is a read-only projection with no joins, performance is generally good provided standard indexes on PERSON_ID and ORG_ID exist on the base table. All queries should reference the APPS synonym and honour Multi-Org context.