Search Results inq_entry_stat




Overview
Explore in AI Chat

Overview

The IGS_AD_I_ENTRY_STATS table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Student Management (OSM) product, which is part of the IGS (iGrants) schema. Its primary function is to store and manage the various statuses associated with prospective student inquiries and application entries within the admissions lifecycle. This table acts as a reference or lookup table, providing a standardized set of codes and descriptions that classify the stage or condition of an inquiry or entry record. It is critical for tracking the progression of prospective students from initial contact through to formal application. Notably, the provided ETRM documentation explicitly marks this table as "Obsolete," indicating it may have been superseded in later functional designs or its usage deprecated, though it remains present and valid in the specified database versions.

Key Information Stored

The table's columns are designed to capture both the status definition and its contextual attributes. The primary identifier, INQ_ENTRY_STAT_ID, is a unique numeric key. The core business code, INQ_ENTRY_STAT, is a 30-character string representing the status itself, such as 'ACTIVE', 'CONVERTED', or 'CLOSED'. The DESCRIPTION field provides a longer explanation. Several columns classify the status based on the inquiry's origin or type, including ENQUIRY_SOURCE_TYPE, ACTIVITY_SOURCE_CD, INSTITUTION_TYPE, TEST_SOURCE_ID, and IMP_SOURCE_TYPE_ID. The CLOSED_IND flag is crucial for filtering active versus inactive statuses. Furthermore, the table supports configuration and integration through fields like CONFIGURABILITY_FUNC_NAME and EMAIL_LINK. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are present for auditability.

Common Use Cases and Queries

This table is predominantly used in reporting and data validation scenarios within the admissions module. Common use cases include generating lists of inquiries by their current status, determining conversion rates from inquiry to application, and applying business rules based on status hierarchies (HIERARCHY_CD). A typical query would join this table to a main inquiry or application table to pull descriptive status information. For example, to retrieve all active inquiry statuses for a specific source type, one might use:

  • SELECT stat.INQ_ENTRY_STAT, stat.DESCRIPTION
  • FROM IGS.IGS_AD_I_ENTRY_STATS stat
  • WHERE stat.CLOSED_IND = 'N'
  • AND stat.ENQUIRY_SOURCE_TYPE = 'WEB';

Another common pattern is using the table to validate status codes during data imports or integrations, ensuring only defined statuses are applied to student records.

Related Objects

The table's relationships are primarily inferred from its indexed columns. The presence of a primary key (IGS_AD_I_ENTRY_STATS_PK on INQ_ENTRY_STAT_ID) and a unique key (IGS_AD_I_ENTRY_STATS_U1 on INQ_ENTRY_STAT) suggests these columns are foreign keys in other transactional tables, such as those storing individual inquiry or application records. The non-unique indexes on columns like ENQUIRY_SOURCE_TYPE, INSTITUTION_TYPE, TEST_SOURCE_ID, and IMP_SOURCE_TYPE_ID indicate these are likely foreign keys to other reference tables defining those source and type classifications. While specific table names are not listed in the metadata, related objects would include the main inquiry/entry header tables and various source type code tables within the IGS schema. The "FND Design Data" reference points to integration with the Oracle Application Object Library.