Search Results inq_person_id




Overview
Explore in AI Chat

Overview

The IGS.IGR_IS_ACAD table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Student Management (OSM) product family under the IGS (iGrants) schema. Its primary function is to serve as a staging area for self-service academic interest data related to student inquiries. The table acts as a transient repository where academic history information for prospective students (inquiries) is captured or imported before being validated and processed into the main transactional tables of the system. Its designation to the APPS_TS_INTERFACE tablespace further confirms its role in the data interface and staging layer of the application architecture.

Key Information Stored

The table stores academic background details for inquiry records. Key columns include the unique identifier INQ_ACAD_ID and the critical foreign key INQ_PERSON_ID, which links the academic data to a specific person/inquiry record in the system. The table captures institutional history through INSTITUTION_CD, START_DATE, and END_DATE. Academic performance is stored via self-reported metrics such as SELFREP_INST_GPA, SELFREP_RANK_IN_CLASS, and SELFREP_TOTAL_CP_EARNED. Program-specific information is held in COURSE_MAJOR and DEGREE_EARNED. The STATUS column likely indicates the processing state of the staged record (e.g., 'NEW', 'PROCESSED', 'ERROR'). Standard EBS "Who" columns (CREATED_BY, LAST_UPDATE_DATE, etc.) and concurrent program tracking columns are also present for audit and processing control.

Common Use Cases and Queries

A primary use case is the batch import or manual entry of an inquiry's prior academic history through a self-service interface or data loader. The presence of the non-unique index IGR_IS_ACAD_N1 on INQ_PERSON_ID is optimized for queries fetching all academic records for a specific inquiry. Common reporting and validation SQL patterns include:

  • Retrieving all staged academic history for a specific inquiry to display in a review interface: SELECT * FROM igs.igr_is_acad WHERE inq_person_id = :person_id ORDER BY start_date;
  • Identifying unprocessed (e.g., pending) academic records for batch processing: SELECT inq_person_id, institution_cd FROM igs.igr_is_acad WHERE status = 'NEW' AND request_id IS NULL;
  • Aggregating self-reported academic metrics for an inquiry for assessment purposes: SELECT inq_person_id, COUNT(*) institution_count, MAX(selfrep_inst_gpa) FROM igs.igr_is_acad WHERE inq_person_id = :person_id GROUP BY inq_person_id;

Related Objects

The most direct relationship is implied by the INQ_PERSON_ID column, which is a foreign key to a person or inquiry master table, likely named IGR_I_PERSON or similar within the IGS schema. The table's primary key, INQ_ACAD_ID, is enforced by the unique index IGR_IS_ACAD_PK. Data from this staging table is typically processed by concurrent programs or PL/SQL APIs that validate and transfer it into permanent academic history tables. These related programs would populate the REQUEST_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE columns upon successful execution. The table may also be referenced by views that present a consolidated profile of an inquiry, combining data from multiple staging tables.