Results for “cal_type”

50+ results




Overview
Explore in AI Chat

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

Overview

The view IGS_EN_EFFECTIVE_TERMS_V belongs to the IGS – Student System product family within Oracle E-Business Suite. Under the 12.1.1 and 12.2.2 releases the IGS modules are classified as obsolete, and the ETRM metadata explicitly records that this object is "Not implemented in this database." Consequently, in a standard EBS 12.1.1 or 12.2.2 instance the view will not exist unless it was created as part of a legacy or customized Student System deployment. The view fetches the current term, one previous term, and one next term for the academic calendar, presenting a three-term rolling window of academic period definitions.

Its role is fundamentally reporting- and integration-oriented. Rather than requiring downstream consumers to resolve term boundaries themselves, the view consolidates academic calendar instances into a normalized, ready-to-query result set. This is consistent with the operational pattern in EBS where a reporting view wraps procedural term-navigation logic so that SQL-based reporting tools, interfaces, and extracts can select effective terms without invoking PL/SQL directly. The "Jun three terms" search association reflects the practical use case: a user seeking the June term configuration and its immediately adjacent academic periods.

Underlying Base Objects

The ETRM metadata documents the referenced base objects as "none documented," but the supplied view text makes the dictionary dependencies explicit. The view is defined over three base tables:

  • IGS_CA_INST — the calendar instance table holding each concrete term occurrence, including its calendar type, sequence number, start and end dates, alternate code, and description.
  • IGS_CA_TYPE (aliased CT) — the academic calendar type driving the term-retrieval functions.
  • IGS_CA_TYPE (aliased CT1) — the second reference to the calendar type used to expose the abbreviation alongside each instance row.

Term identification is not resolved through a stored foreign key. Instead, the view calls the IGS_EN_SPA_TERMS_API package functions GET_CURR_TERM, GET_PREV_TERM, and GET_NEXT_TERM. Each function returns a concatenated value in which the first six characters are the sequence number and the remaining characters (from position 7) carry the calendar type. The view splits this value using SUBSTR and RTRIM to join back to IGS_CA_INST on matching CAL_TYPE and SEQUENCE_NUMBER. Three such blocks are combined with UNION ALL to yield the current, previous, and next terms in a single result set.

Key Columns

  • CAL_TYPE — the calendar type of the resolved term instance.
  • SEQUENCE_NUMBER — the ordinal sequence identifying the specific term within the calendar, derived from the API return value.
  • START_DT / END_DT — the effective start and end dates of the term, essential for date-range filtering and reporting.
  • ALTERNATE_CODE — the user-facing or external code assigned to the term.
  • DESCRIPTION — the descriptive name of the calendar instance.
  • ACAD_CAL_TYPE — the driving academic calendar type from which the term navigation originated.
  • ABBREVIATION — the short label for the calendar type, useful for compact reporting output.

Common Use Cases and Queries

Typical uses include validating which terms are active, extracting term boundaries for enrollment or billing interfaces, and driving date-sensitive reports that must default to the current academic period while referencing adjacent terms. A representative query is:

SELECT cal_type, sequence_number, start_dt, end_dt, alternate_code, description, acad_cal_type, abbreviation FROM igs_en_effective_terms_v WHERE acad_cal_type = :calendar_type;

To locate a specific period such as the June term, reporting logic would filter on START_DT and END_DT or on ALTERNATE_CODE. Because the object is obsolete and unimplemented in 12.1.1 and 12.2.2, any usage should first confirm that the view and the supporting IGS_EN_SPA_TERMS_API package exist in the target instance.