Search Results igs_ca_gen_001




Overview
Explore in AI Chat

Overview

The view APPS.IGS_PE_PERSON_PREFS_ADM_V is a reporting and integration object within the Oracle E-Business Suite Student System (formerly Oracle Student System, now part of the Oracle Higher Education product family). It exposes admissions-related person preferences recorded against a person record, denormalising calendar instance attributes and alternate calendar codes so that consumers do not need to reconstruct the relationships among the person preference table, the calendar instance relationship table, and the calendar instance table themselves. The view is defined in the APPS schema and is therefore accessible to any responsibility or integration account granted SELECT on APPS objects.

The view is particularly relevant because it resolves the academic and admissions calendar instances associated with each person preference row and presents their start and end dates alongside short-form alternate calendar codes. This makes it suitable for downstream reporting, extracts, and interface programs that must present admissions calendar context without embedding the full calendar resolution logic.

Underlying Base Objects

The view is defined over four base objects: IGS_PE_PERS_PREFS, IGS_CA_INST_REL, and two aliased instances of IGS_CA_INST (aliased as CI1 and CI2).

  • IGS_PE_PERS_PREFS (alias PP) is the driving table and supplies the person identifier, the academic calendar type and sequence number, the admissions calendar type and sequence number, the admission category, the admission process type, and the standard WHO columns.
  • IGS_CA_INST_REL (alias CIR) is the calendar instance relationship table. It links the academic calendar instance (superior) to the admissions calendar instance (subordinate).
  • IGS_CA_INST (CI1) provides the start and end dates for the superior (academic) calendar instance.
  • IGS_CA_INST (CI2) provides the start and end dates for the subordinate (admissions) calendar instance.

All joins to CIR, CI1, and CI2 are outer joins (indicated by the (+) operator), so rows in IGS_PE_PERS_PREFS are preserved even when no matching calendar relationship or calendar instance exists. The documentation records no additional referenced base objects beyond these.

Key Columns

Common Use Cases and Queries

The view is used where admissions personnel preferences must be reported with resolved calendar dates and codes. Typical consumers include admissions reporting extracts, data warehouse loads, and integration interfaces that synchronise person preferences to external systems. Because the joins are outer, the view is safe for querying all preferences without filtering out records lacking a calendar relationship.

A representative query retrieves all admissions preferences for a person:

SELECT person_id, adm_acad_cal_type, adm_adm_cal_type,
       adm_admission_cat, adm_s_admission_process_type
FROM   apps.igs_pe_person_prefs_adm_v
WHERE  person_id = :p_person_id;

A second example restricts output to preferences whose admissions calendar instance is currently active:

SELECT person_id, adm_adm_cal_type, start_dt, end_dt
FROM   apps.igs_pe_person_prefs_adm_v
WHERE  adm_adm_cal_type = :p_cal_type
AND    TRUNC(SYSDATE) BETWEEN start_dt AND end_dt;

The reference to IGS_CA_GEN_001.CALP_GET_ALT_CD in the view definition means the view depends on the IGS_CA_GEN_001 package, which must be valid and compiled for the view to return alternate calendar codes correctly. Queries that do not reference the alternate code columns still execute the function as part of the view's select list, so package validity is a prerequisite for reliable results.