Search Results igs_pe_acad_intents




Overview
Explore in AI Chat

Overview

The IGS_PE_ACAD_INTENTS table is a core data object within the Oracle E-Business Suite Student System (IGS). It serves as the primary repository for storing a student's declared academic intent. This concept is fundamental to student lifecycle management, capturing a learner's planned educational trajectory at a specific point in time. The table's role is to formally record these intentions, which are critical for academic advising, program planning, enrollment forecasting, and compliance reporting. By linking a student (PERSON_ID) to an academic calendar instance (CAL_TYPE and SEQUENCE_NUMBER), it anchors the intent within a specific term or period, providing essential context for the student's planned academic activities.

Key Information Stored

The table's structure is designed to uniquely identify and describe a student's academic plan. The primary key, ACAD_INTENT_ID, ensures each record is distinct. The two most critical foreign key relationships define the table's core purpose: the PERSON_ID column links to the IGS_PE_HZ_PARTIES table to identify the specific student, while the CAL_TYPE and SEQUENCE_NUMBER columns together link to the IGS_CA_INST_ALL table to identify the academic calendar period (e.g., Fall Semester 2024) for which the intent is declared. While the provided metadata does not list all columns, typical data stored in such a table would include fields for the intended program of study, load type (full-time/part-time), attendance type, status of the intent, and creation/modification timestamps.

Common Use Cases and Queries

This table is central to numerous operational and reporting functions. Common use cases include generating lists of students intending to enroll in a forthcoming term for resource planning, verifying a student's declared program for advising sessions, and tracking changes in academic intent over time for retention analysis. A typical reporting query would join this table to person and calendar tables to produce a clean list. For example:

  • Identifying all students with an active academic intent for a specific term: SELECT person_id FROM igs_pe_acad_intents WHERE cal_type = 'SEM' AND sequence_number = 202401;
  • Joining to person details to create a roster: SELECT p.party_number, p.person_first_name, p.person_last_name, ai.cal_type, ai.sequence_number FROM igs_pe_acad_intents ai, igs_pe_hz_parties p WHERE ai.person_id = p.party_id;

Data is typically created and maintained through dedicated Student System application flows, not via direct SQL manipulation.

Related Objects

As indicated by the foreign key constraints, IGS_PE_ACAD_INTENTS has direct and essential relationships with other foundational tables in the EBS Student System.

  • IGS_PE_HZ_PARTIES: This table stores the person or student entity. The PERSON_ID foreign key ensures every academic intent is associated with a valid person record.
  • IGS_CA_INST_ALL: This table defines calendar instances (specific terms or periods). The composite foreign key on CAL_TYPE and SEQUENCE_NUMBER ties each academic intent to a specific academic period, providing crucial temporal context.

Furthermore, this table is likely referenced by other transactional and reporting objects within the IGS module, such as enrollment-related tables, academic history records, and various student information views, forming a key node in the student data model.