Results for “term_sequence_number”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_EN_SS_SCHEDULE_DISP_V is a VALID Oracle E-Business Suite view owned by the APPS schema within the IGS (Student System) product. Its documented purpose is to expose all program attempts enriched with derived scheduling attributes, such as applicable minimum and maximum credit points, the year of the program unit set, attendance type, attendance mode, and location details. The view is consumed by the Self-Service schedule page, providing the presentation layer with a consolidated, denormalised row per student, program, and term.

Because the view is defined in the APPS schema, it is callable by any application responsibility that holds SELECT privileges on it, which is the standard pattern for ETRM (Enterprise Trading and Records Management / Student System) self-service pages and concurrent report extracts.

Underlying Base Objects

The ETRM metadata for this object documents no explicitly registered base objects, though the embedded view text reveals its dependency chain. The primary driving table is SCA (the student course attempt), from which PERSON_ID, COURSE_CD (aliased to PROGRAM_CD), and VERSION_NUMBER are sourced. It is joined to the program version table (aliased PV) to obtain CAREER via COURSE_TYPE.

Calendar instance tables supply term context: CI1 provides the term CAL_TYPE, SEQUENCE_NUMBER, DESCRIPTION, and START_DT, while CIR supplies the sub-calendar and superior calendar relationships. CI2 contributes the academic period description. The view also directly references IGS_EN_SU_ATTEMPT for unconfirmed unit attempt detection, and the helper view IGS_CA_LOAD_TO_TEACH_V for teaching calendar mapping. Behaviour is largely delegated to stored PL/SQL functions in the IGS_EN_SPA_TERMS_API, IGS_EN_ELGBL_PROGRAM, and IGS_EN_PRC_LOAD packages.

Key Columns

Common Use Cases and Queries

The view is primarily queried by the self-service schedule page and by enrollment reports that need per-term program attempt detail. A typical query filters by person and term:

SELECT person_id, program_cd, version_number, career,
       term_description, start_dt,
       applied_min_cp, applied_max_cp, unconf_sua
  FROM apps.igs_en_ss_schedule_disp_v
 WHERE person_id = :p_person_id
   AND start_dt BETWEEN :p_from AND :p_to;

Because the view calls PL/SQL functions per row, ad-hoc queries across large student populations should restrict the driving set first, for example by joining back to a specific calendar instance, to avoid executing the API functions for every program attempt in the institution.