Search Results academic_description




Overview
Explore in AI Chat

Overview

IGS_EN_SS_STUD_CONTEXT_V is an APPS-owned database view in the Oracle E-Business Suite Student System (IGS) product family. It exposes the student program attempt context—the enrollment-level attributes associated with a student's attempt at a program (course) within a specific academic calendar term. Its role is to consolidate, for a given student program attempt, the term identifiers, career, attendance type/mode/location, primary and secondary program titles, applied credit point ranges, unit sets, and institutional attendance and credit-point load figures into a single queryable row. Because these values are resolved through PL/SQL API calls (IGS_EN_SPA_TERMS_API, IGS_EN_ELGBL_PROGRAM, IGS_EN_PRC_LOAD, IGS_SS_ENR_DETAILS) rather than through direct joins to base tables, the view is chiefly intended for reporting, self-service (SS) display, and integration scenarios where a flattened, human-readable snapshot of the student context is required.

Underlying Base Objects

The view text references SCA (the student course attempt record), the program version entity (aliased PV, supplying COURSE_TYPE as CAREER), calendar instance CI1 as the primary term, and calendar instance relationship CIR with its secondary calendar CI2. No base tables are explicitly documented in the ETRM metadata ("none documented"), and no owner is recorded for the referenced objects in the 12.2.2 metadata. The authoritative values for term description, attendance type/mode/location (and their descriptions), primary program, applied minimum/maximum credit points, institutional attendance, institutional credit points, and primary/secondary program titles are produced at runtime by API calls into the IGS_EN and IGS_SS packages. Consequently the view functions as a virtual composite over the student course attempt and calendar structures, with derivations governed by the underlying APIs.

Key Columns

  • PERSON_ID — the student's unique person identifier.
  • PROGRAM_CD — derived from SCA.COURSE_CD, identifying the program attempted.
  • VERSION_NUMBER — the program version in effect for the attempt.
  • CAREER — the course type, mapped from the program version.
  • TERM_DESCRIPTION — the description of the primary calendar instance (CI1.DESCRIPTION), i.e. the term label; this is the column the user's search term targets.
  • START_DT — the start date of the primary term.
  • SUB_CAL_TYPE / SUB_CI_SEQUENCE_NUMBER — the subordinate calendar type and sequence.
  • SUP_CAL_TYPE / SUP_CI_SEQUENCE_NUMBER — the superior calendar type and sequence.
  • ACADEMIC_DESCRIPTION — the description of the secondary calendar instance (CI2.DESCRIPTION), typically the academic period.
  • Attendance and progression columns returned by IGS_EN_SPA_TERMS_API, including attendance type and description, mode and description, and location and description.
  • Credit point columns (applied minimum/maximum) from IGS_EN_ELGBL_PROGRAM, and institutional attendance and institutional credit points from IGS_EN_PRC_LOAD.
  • Primary and secondary program titles and student year-of-program unit set from IGS_SS_ENR_DETAILS.

Common Use Cases and Queries

Typical usage includes term-level enrollment reporting, "my program" self-service pages, and extract feeds requiring a single record per student program attempt per term. The TERM_DESCRIPTION column is frequently used to label or filter records by academic term.

  • List a student's program attempts and terms:

    SELECT person_id, program_cd, version_number, term_description, start_dt FROM apps.igs_en_ss_stud_context_v WHERE person_id = :p_person_id ORDER BY start_dt DESC;

  • Filter by term label:
  • SELECT person_id, program_cd, career, term_description FROM apps.igs_en_ss_stud_context_v WHERE term_description LIKE :term;
  • Report attendance and load per term:
  • SELECT person_id, program_cd, term_description, academic_description FROM apps.igs_en_ss_stud_context_v WHERE person_id = :p_person_id;

Because many values are computed via API calls, queries over this view carry per-row PL/SQL execution cost and should be constrained by PERSON_ID or term wherever possible to control performance.