Search Results adm_acad_cal_type




Overview
Explore in AI Chat

Overview

IGS_PE_PERS_PREFS is an Oracle E-Business Suite (EBS) view owned by the APPS schema within the IGS – Student System product family. It presents person-level preference records maintained for students, applicants, and related parties in the Oracle Student System, exposing configuration choices such as default academic calendars, enrolment and admission categories, admission process types, enquiry calendars, a default server printer, and the ALLOW_STND_REQ_IND flag. The view is classified as VALID in both EBS 12.1.1 and 12.2.2.

The view serves as the operational, multi-tenant-aware read interface over the underlying preference table. Its primary purpose is to enforce organizational (ORG_ID) security at query time, so that forms, concurrent programs, and reports executed in a given business context see only the preferences belonging to the active organization. For integration and reporting purposes, the view provides a stable, denormalized column list that downstream extracts, BI Publisher reports, and interface programs can consume without directly addressing the base table. The column ALLOW_STND_REQ_IND, the object of the user's search, is the "allow standing request" indicator, controlling whether the person may submit or maintain standing requests within the Student System.

Underlying Base Objects

The ETRM documentation identifies a single documented base object: IGS_PE_PERS_PREFS_ALL, referenced in the view text as the source of all columns. The view is defined with a SELECT over IGS_PE_PERS_PREFS_ALL, aliased TAB, projecting ROWID as ROW_ID plus the full set of preference columns. No additional tables, synonyms, or joined objects are documented.

Row filtering is implemented through the standard multi-org predicate, combining NVL and USERENV('CLIENT_INFO') to compare the session's current organization against the row's ORG_ID. Where the client context lacks a valid organization, the expression resolves to -99, which typically matches only global or non-org-specific rows. This confirms that IGS_PE_PERS_PREFS_ALL is an org-striped table and that the view is the org-secured projection of it. The _ALL suffix on the base table indicates the presence of an associated org-secured synonym pattern (for example, a corresponding non-_ALL synonym or view used inside Oracle Forms).

Key Columns

Common Use Cases and Queries

Typical usage includes verifying standing-request eligibility, driving default calendar and category values into student self-service and administrative forms, and producing extracts of person preferences for downstream student records integration. Because the view enforces ORG_ID security, it should be queried in the correct operating unit context to avoid returning only global rows.

Sample query for standing-request eligibility by person:

  • SELECT person_id, org_id, allow_stnd_req_ind FROM apps.igs_pe_pers_prefs WHERE person_id = :p_person_id;

Sample query listing persons permitted to raise standing requests within the active organization:

  • SELECT person_id, allow_stnd_req_ind FROM apps.igs_pe_pers_prefs WHERE allow_stnd_req_ind = 'Y';

Sample query to audit changes to preference records:

  • SELECT person_id, last_updated_by, last_update_date FROM apps.igs_pe_pers_prefs WHERE last_update_date >= :p_since_date;

When updating preference data, changes should be applied to the base table IGS_PE_PERS_PREFS_ALL in the correct organization context, since the view's ROW_ID maps directly to the base row; direct DML through the view is subject to the same ORG_ID predicate and should be performed with the appropriate CLIENT_INFO or org initialization.