Search Results igs_ca_inst_adm_perd_v




Overview

The IGS_CA_INST_ADM_PERD_V view is a reporting object within the Oracle E-Business Suite Student System (IGS) product family. Its name reflects its purpose: it exposes an "instance admission period" — that is, the pairing of an admission calendar instance with its associated academic calendar instance. The view is classified under the IGS - Student System (Obsolete) documentation set and, per the ETRM metadata, is not implemented in this database in the 12.2.2 environment. This distinction is important: the object appears in historical ETRM documentation and in earlier Oracle Student System releases, but it is not a deployed, queryable database object in the current release under review.

Functionally, the view consolidates calendar instance data so that admission cycles can be reported alongside the academic periods they relate to. This supports institutional reporting of admission windows, commencement periods, and status, and would historically have been consumed by integration extracts and operational reports in the student administration module.

Underlying Base Objects

The view text is defined over five base objects joined through outer and inner joins:

  • IGS_CA_INST (aliased CI1) — the primary calendar instance, restricted to instances whose calendar type belongs to calendar category ADMISSION.
  • IGS_CA_INST_REL (aliased CIR) — the calendar instance relationship table, linking a sub-instance to a superior instance, joined with outer (+) syntax on SUB_CAL_TYPE and SUB_CI_SEQUENCE_NUMBER.
  • IGS_CA_INST (aliased CI2) — the superior academic calendar instance, outer-joined via the relationship table.
  • IGS_CA_TYPE (aliased CAT1) — the calendar type definition for the admission calendar, inner-joined with S_CAL_CAT = 'ADMISSION'.
  • IGS_CA_TYPE (aliased CAT2) — the calendar type definition for the academic calendar, outer-joined with S_CAL_CAT = 'ACADEMIC'.

The outer joins permit admission instances to appear even where no superior academic instance is associated, which is essential for completeness in admissions reporting.

Key Columns

Common Use Cases and Queries

Because the object is documented as not implemented in 12.2.2, the following query patterns illustrate intended usage rather than executed behaviour in the current release. A typical reporting query would retrieve admission periods with their academic counterparts:

  • Admission period listing: SELECT ADM_CAL_TYPE, ADM_CI_SEQUENCE_NUMBER, ADM_START_DT, ADM_END_DT, ADM_CAL_STATUS, COMMENCEMENT_PERIOD FROM IGS_CA_INST_ADM_PERD_V ORDER BY ADM_START_DT;
  • Alternate code lookup: filtering on ADM_ALTERNATE_CODE or ACAD_ALTERNATE_CODE to resolve an instance from an external reference code supplied by an integration feed.
  • Commencement extraction: selecting COMMENCEMENT_PERIOD to populate external commencement listings or student communications.

In all cases, implementers should confirm whether the view exists in their specific ETRM release before deploying dependent logic, and should query the current IGS data dictionary for a supported replacement where it has been retired.