Search Results igs_ad_i_entry_stats




Overview
Explore in AI Chat

Overview

The table IGS_AD_I_ENTRY_STATS is a core data object within the Oracle E-Business Suite Student System (IGS), specifically within the Admissions module. Its primary function is to serve as a master reference table for storing and managing all valid inquiry entry statuses. An inquiry entry status is a key classification used to track the stage or disposition of a prospective student's inquiry or application during the admissions process. This table acts as a foundational lookup, ensuring data integrity and consistency across the admissions lifecycle by providing a controlled set of status codes. It is important to note that the provided ETRM documentation explicitly marks both the IGS product and this specific table as "Obsolete," indicating it is part of a legacy system footprint that may no longer be actively developed or implemented in newer installations.

Key Information Stored

The table's structure is designed to support a normalized status model. The primary identifier is the INQ_ENTRY_STAT_ID column, which serves as the unique system-generated primary key (IGS_AD_I_ENTRY_STATS_PK). A significant business key is the INQ_ENTRY_STAT column, which holds the actual status code or short name and is enforced by a unique key constraint (IGS_AD_I_ENTRY_STATS_UK). The table's design integrates with other code classifications and master data within EBS through several foreign key columns. These include TEST_SOURCE_ID (linking to IGS_AD_CODE_CLASSES), ENQUIRY_SOURCE_TYPE (linking to IGS_IN_ENQ_SRC_TYPE), INSTITUTION_TYPE (linking to IGS_OR_ORG_INST_TYPE_ALL), and IMP_SOURCE_TYPE_ID (linking to IGS_PE_SRC_TYPES_ALL). These relationships allow statuses to be contextualized and associated with specific admission rules, sources, and institution types.

Common Use Cases and Queries

In a functional context, this table is primarily referenced for validation, reporting, and configuration. Application forms and processes would validate user-entered statuses against this table. Common reporting use cases involve analyzing inquiry pipelines by status or tracking conversion rates from inquiry to application. A typical query might join this table to an inquiry transaction table to generate a status summary report. It is critical to emphasize that the ETRM metadata states "Not implemented in this database," which strongly suggests that in the specific EBS instance documented, this table and its related logic are not in active use. Therefore, while sample SQL patterns might involve simple selects or joins, any operational use would be exceptional. For example: SELECT stat.INQ_ENTRY_STAT, COUNT(app.APPLICANT_ID)
FROM IGS_AD_I_ENTRY_STATS stat, IGS_IN_ENQUIRY_APPL_ALL app
WHERE stat.INQ_ENTRY_STAT_ID = app.INQ_ENTRY_STAT_ID
GROUP BY stat.INQ_ENTRY_STAT;

Related Objects

The IGS_AD_I_ENTRY_STATS table has extensive relationships within the obsolete Student System, acting as a parent lookup for numerous transactional and configuration entities. As per the foreign key metadata, it is referenced by a significant number of child tables that store admissions setup and transaction data. Key dependent objects include: IGS_AD_ENT_ORG_UNITS, IGS_AD_ENT_PKG_ITEMS, IGS_AD_ENT_INQ_PROGS, IGS_AD_ENT_TEST_TYPS, and IGS_AD_ENT_INQ_USET, which likely store status-specific admission rules and package assignments. Crucially, the main inquiry transaction table, IGS_IN_ENQUIRY_APPL_ALL, holds a foreign key to this table, linking each inquiry record to its current status. This web of dependencies underscores its former role as a central control point for the admissions inquiry workflow before being marked obsolete.