Search Results inq_college_id

Overview

The IGS_SS_INQ_COLLEGE table is a data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, residing under the IGS (iGrants) schema. Its primary function was to stage college-related activity records for inquiries within the Self-Service module. The ETRM documentation explicitly marks this table as "Obsolete," indicating it is no longer actively used in current implementations for holding live transactional data. Its historical role was to temporarily hold data related to a prospective student's (inquiry's) interactions and interests with colleges before potential processing or migration to permanent tables. The table is stored in the APPS_TS_INTERFACE tablespace, which is typically designated for transient or staging data, aligning with its described purpose.

Key Information Stored

The table's structure captures details about an inquiry's college-specific engagements. The key columns include INQ_COLLEGE_ID, which serves as the unique primary key identifier for each college activity record. The INQ_PERSON_ID links the activity to a specific inquiry person. A central column for the user's search is COLLEGE_ACTIVITY_TYPE, a VARCHAR2(30) field that categorizes the nature of the interaction (e.g., "Campus Visit," "Information Request," "Application Started"). The INTEREST_NAME column (VARCHAR2(240)) holds the descriptive name of the college or program of interest. Additional operational columns include ACTIVITY_SOURCE_CD for the origin of the activity data, STATUS to indicate the record's state, and a full complement of Standard Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, etc.) for audit and processing context.

Common Use Cases and Queries

Given its obsolete status, current use cases are primarily limited to historical data analysis, data migration validation, or supporting legacy reports. Common queries would involve extracting staged college activity data for specific inquiries or time periods. For instance, to analyze all college activities of a particular type for a given inquiry person, one might use:

SELECT INTEREST_NAME, CREATION_DATE, STATUS
FROM IGS.IGS_SS_INQ_COLLEGE
WHERE INQ_PERSON_ID = :person_id
AND COLLEGE_ACTIVITY_TYPE = :activity_type
ORDER BY CREATION_DATE DESC;

Another pattern might involve joining this staging data with core person or student tables (via INQ_PERSON_ID) to build a historical view of inquiry engagement before they became applicants or students, though such joins are not explicitly defined by foreign keys in the provided metadata.

Related Objects

Based on the provided dependency information, the IGS_SS_INQ_COLLEGE table does not reference any other database objects. However, it is referenced by an object named IGS_SS_INQ_COLLEGE under the APPS synonym. This indicates that an APPS synonym exists to point to this IGS-owned table, which is a standard EBS practice for granting cross-schema access. The metadata does not list any foreign key relationships, views, or APIs with explicit join columns that depend on this table. Its primary relationship is through the INQ_PERSON_ID, which would logically relate to a person or party table in the system, but this link is not formally documented in the provided excerpt.