Search Results igs_ss_inq_person_all




Overview
Explore in AI Chat

Overview

The IGS_SS_INQ_PERSON_ALL table is a core data structure within the Oracle E-Business Suite's Student System (IGS) module, specifically for releases 12.1.1 and 12.2.2. It functioned as a staging table designed to hold person-level information for inquiries submitted through the Self-Service application. Its primary role was to act as a central hub for inquiry-related person data, facilitating the intake and temporary storage of prospect information before potential integration into the main student information system. Critically, the official ETRM documentation explicitly marks this table as "Obsolete," indicating it is no longer actively developed or recommended for use in current implementations. Its presence in the schema is typically for backward compatibility or data migration purposes.

Key Information Stored

While the provided metadata does not list specific column details beyond the primary key, the table's purpose and relationships define its core data elements. The primary key, INQ_PERSON_ID, serves as the unique identifier for each person record within the inquiry staging context. Based on its described role and the nature of the tables that reference it, IGS_SS_INQ_PERSON_ALL would logically store foundational demographic and biographical data for an inquiry prospect. This typically includes fields such as name, date of birth, gender, and contact identifiers. The table's "ALL" suffix signifies it is a multi-organization table, meaning it includes an ORG_ID column to partition data by operating unit, a standard design pattern in Oracle EBS for tables that support multiple business units.

Common Use Cases and Queries

Given its obsolete status, direct operational use cases for new development are strongly discouraged. Its primary contemporary use is for historical data analysis, auditing, or supporting legacy data extracts related to old self-service inquiry processes. Common queries would involve joining this central person table to its related detail tables to reconstruct a complete prospect inquiry record for reporting. A typical analytical SQL pattern would be:

SELECT person.*, inq.* FROM IGS_SS_INQ_PERSON_ALL person JOIN IGS_SS_INQUIRY inq ON person.INQ_PERSON_ID = inq.INQ_PERSON_ID WHERE person.CREATION_DATE > SYSDATE - 365;

This query retrieves person and core inquiry data for records created in the past year. Any custom reporting or integration that references this table should be reviewed for migration to current, supported tables and APIs within the Student System.

Related Objects

The IGS_SS_INQ_PERSON_ALL table maintains a central relationship with several detail staging tables, as documented by its foreign key constraints. These related tables store specific categories of information linked to a primary person record. The key documented relationships are:

  • IGS_SS_INQUIRY: Links via INQ_PERSON_ID. This is likely the core inquiry header record.
  • IGS_SS_INQ_ACAD: Links via INQ_PERSON_ID for storing academic background or interest data.
  • IGS_SS_INQ_ADDRESS: Links via INQ_PERSON_ID for storing address details.
  • IGS_SS_INQ_COLLEGE: Links via INQ_PERSON_ID for college-specific inquiry information.
  • IGS_SS_INQ_CONTACT: Links via INQ_PERSON_ID for contact information or preferences.
  • IGS_SS_INQ_EXTRACURR: Links via INQ_PERSON_ID for extracurricular activity details.
  • IGS_SS_INQ_TEST: Links via INQ_PERSON_ID for standardized test score information.

All joins to these child tables are performed on the INQ_PERSON_ID column, which is the table's primary key.