Results for “tuition_end_date”

17 results




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

Overview

IGSBV_ACADEMIC_CATALOGS is a read-only database view in the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to expose information about the academic catalog associated with a person. In practice, the view correlates a party record from the Oracle Trading Community Architecture (TCA) with the person's student status detail rows, producing a flattened, report-friendly projection that joins identity information (party number) to enrollment-related attributes such as tuition status and the various calendar type/sequence pairs that describe a student's academic program milestones.

The view is documented in the ETRM metadata as belonging to the obsolete IGS Student System component, and the metadata explicitly notes that it is not implemented in the current database. This means the object may not exist in a given 12.1.1 or 12.2.2 instance, particularly if the institution never licensed or activated the student system modules, or if the object was removed during a prior upgrade. Its role in reporting and integration is nonetheless clear from its definition: it consolidates person-level party identifiers and academic calendar references from IGS_PE_STAT_DETAILS and HZ_PARTIES into a single query surface.

Underlying Base Objects

The view text joins two base objects:

  • IGS_PE_STAT_DETAILS PSD — The primary source of academic status detail. It supplies effective dating, tuition flags and dates, and the matriculation, initial, recent, and catalog calendar type/sequence pairs, along with descriptive code columns for further education, religion, and social-economic status. Person and audit columns also originate here.
  • HZ_PARTIES HZP — The TCA party master, supplying PARTY_NUMBER. The join condition is PSD.PERSON_ID = HZP.PARTY_ID.

The view is declared WITH READ ONLY, so it cannot be used for DML. The ETRM metadata documents no other referenced base objects, and the view's owner is not recorded in the available metadata. Because it is a view rather than a table, it inherits the security and row-level behavior of its underlying objects, including any TCA party access controls applied at query time.

Key Columns

The exposed column list comprises the following logical groups:

Common Use Cases and Queries

Typical uses include verifying a student's academic calendar context, extracting catalog data for downstream reporting, and reconciling person identity against TCA. A representative query retrieving initial calendar information is:

  • SELECT PERSON_NUMBER, INITIAL_CALENDAR_TYPE, INITIAL_SEQUENCE_NUMBER, CATALOG_CALENDAR_TYPE FROM IGSBV_ACADEMIC_CATALOGS WHERE PERSON_NUMBER = :p_party_number;
  • SELECT PERSON_ID, MATRICULATION_CALENDAR_TYPE, RECENT_CALENDAR_TYPE FROM IGSBV_ACADEMIC_CATALOGS WHERE INITIAL_CALENDAR_TYPE = :p_cal_type;
  • SELECT PERSON_NUMBER, EFFECTIVE_START_DATE, IN_STATE_TUITION FROM IGSBV_ACADEMIC_CATALOGS WHERE SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;

Because the view is read-only and its implementation status varies by instance, administrators should confirm its presence before relying on it in concurrent programs or interfaces.