Search Results igs_ad_ent_test_typs

Overview

The IGS_AD_ENT_TEST_TYPS table is a data object within the Oracle E-Business Suite (EBS) Student System module, specifically designated as IGS. Its primary function was to store associations between specific inquiry entry statuses and defined admission test types. This table served as a junction or mapping table, linking the status of an inquiry entry to the type of admission test that might be required or relevant at that stage. Crucially, the provided ETRM metadata explicitly labels this table, and the entire IGS Student System module, as "Obsolete." Furthermore, the metadata states it is "Not implemented in this database," indicating that while the table definition exists in the data dictionary, it contains no operational data and is not part of the active application logic in EBS versions 12.1.1 or 12.2.2.

Key Information Stored

The table's structure centers on a composite key that uniquely identifies each association. The primary columns are:

• ENT_TEST_TYPE_ID: A unique system-generated identifier serving as the primary key for the table row.
• INQ_ENTRY_STAT_ID: A foreign key referencing the IGS_AD_I_ENTRY_STATS table, identifying a specific inquiry entry status.
• ADMISSION_TEST_TYPE: A foreign key referencing the IGS_AD_TEST_TYPE table, identifying a specific type of admission test (e.g., SAT, ACT, TOEFL).

The combination of INQ_ENTRY_STAT_ID and ADMISSION_TEST_TYPE is also enforced as a unique key (IGS_AD_ENT_TEST_TYPS_UK), preventing duplicate test type assignments for the same inquiry status.

Common Use Cases and Queries

Given the table's obsolete and unimplemented status, there are no active use cases in a standard EBS 12.1.1 or 12.2.2 environment. Historically, its intended use would have been to support processes where the system needed to determine which admission tests were applicable based on an applicant's current inquiry or entry status. Sample queries would have been simple joins to resolve the foreign key descriptions. For example, a historical report might have looked like:

SELECT stat.entry_status_code, test.test_type, test.description
FROM igs_ad_ent_test_typs map,
    igs_ad_i_entry_stats stat,
    igs_ad_test_type test
WHERE map.inq_entry_stat_id = stat.inq_entry_stat_id
AND map.admission_test_type = test.admission_test_type
ORDER BY stat.entry_status_code;

In a current implementation, any such logic would be managed through different, active tables and application features.

Related Objects

The table's relationships are defined entirely by its foreign key constraints, linking it to two other tables in the obsolete Student System module:

• IGS_AD_TEST_TYPE: This table holds the master list of admission test types. The ADMISSION_TEST_TYPE column in IGS_AD_ENT_TEST_TYPS references this parent table.
• IGS_AD_I_ENTRY_STATS: This table stores the valid inquiry entry statuses. The INQ_ENTRY_STAT_ID column in IGS_AD_ENT_TEST_TYPS references this parent table.

As all related objects are part of the same obsolete module, they collectively represent decommissioned functionality and should not be used for custom development or reporting in a live EBS instance.