Search Results calp_get_alt_cd




Overview

APPS.IGS_PE_PERSON_PREFS_ENQ_V is a reporting and enquiry view within the Oracle E-Business Suite Student System (formerly Oracle Student System, now part of the Student Information Management / Campus Solutions lineage) that exposes person-level enrolment preference data alongside resolved academic and admissions calendar information. It is one of the enquiry ("_ENQ_V") views delivered under the IGS (Institution of Higher/Graduate Studies) schema and is intended for use in forms, reports, and integration extracts where the raw identifiers held against a person's enrolment preferences must be translated into human-readable alternate calendar codes and enriched with calendar instance start and end dates.

The view plays a presentation role: rather than forcing callers to resolve calendar type codes and instance sequence numbers through multiple joins and API calls, the view performs that resolution internally and returns a flattened, denormalised result set. The object name and structure indicate it is bound to the enrolment (ENQ) context, since the driving columns are prefixed ENQ_ACAD_* and ENQ_ADM_*.

Underlying Base Objects

The view is defined over three documented base objects:

  • IGS_PE_PERS_PREFS (aliased PP) — the driving table holding person preferences, including person_id and the enrolment academic and admissions calendar identifiers. It is the only non-outer-joined table in the definition and therefore determines the row population.
  • IGS_CA_INST_REL (aliased CIR) — the calendar instance relationship table, which maps a superior (sup) calendar instance to a subordinate (sub) calendar instance. It is outer-joined to the preference table, so preferences without a matching relationship still return rows.
  • IGS_CA_INST (aliased CI1 and CI2) — the calendar instance table, joined twice (once via CIR.SUP_* as CI1 and once via CIR.SUB_* as CI2) to supply start_dt and end_dt values for the academic and admissions calendar instances respectively. Both joins are outer joins.

The ETRM metadata records no referenced base objects for this view in addition to those visible in the view text, so the four tables above constitute the complete documented dependency set.

Key Columns

Common Use Cases and Queries

The view is typically queried to display a person's enrolment calendar preferences with readable codes and dates, or to export them for downstream integration. Because all joins to the relationship and instance tables are outer joins, callers must tolerate NULL alternate codes and dates where no calendar relationship has been configured.

A typical projection limits output to a single person:

  • SELECT person_id, enq_acad_cal_type, enq_adm_cal_type, start_dt, end_dt FROM apps.igs_pe_person_prefs_enq_v WHERE person_id = :person_id;

A reporting extract may instead filter on date ranges or join to person reference data. Callers requiring the untruncated alternate code should invoke IGS_CA_GEN_001.calp_get_alt_cd directly, since this view exposes only the first ten characters.