Search Results inq_test_seg_id




Overview
Explore in AI Chat

Overview

The IGS_SS_INQ_TESTSEG table is a core data structure within the Oracle E-Business Suite (EBS) Student Systems (SS) module, specifically for versions 12.1.1 and 12.2.2. As documented, its primary function is to hold Self Service Staging Inquiry Test Segments. This table acts as a staging or transactional repository for detailed segment-level results associated with standardized admission tests submitted via self-service inquiry processes. The metadata explicitly notes the table and one of its columns (ADMISSION_TEST_TYPE) as "Obsolete," indicating its functional relevance may have been superseded in later application logic, though the table remains structurally valid within the database schema. Its storage in the APPS_TS_INTERFACE tablespace further supports its role as an intermediary data store for processing transactional information.

Key Information Stored

The table's columns are designed to capture test segment details, audit information, and processing status. The most critical columns include:

  • INQ_TEST_SEG_ID (NUMBER): The primary key, providing a unique identifier for each test segment record.
  • INQ_TEST_ID (NUMBER): A foreign key linking the segment to its parent inquiry test record in the IGS_SS_INQ_TEST table.
  • TEST_SEGMENT_ID (NUMBER): Identifies the type or category of the test segment (e.g., Verbal, Quantitative, Analytical Writing).
  • TEST_SCORE (NUMBER): Stores the numerical score achieved for this specific test segment.
  • STATUS (VARCHAR2): Indicates the processing status of the segment record within the staging workflow.
  • ADMISSION_TEST_TYPE (VARCHAR2): Documented as obsolete, this field originally specified the type of admission test (e.g., GRE, GMAT).
The table also contains a full suite of Standard Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and Standard Who columns for concurrent Programs (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) for comprehensive audit tracking.

Common Use Cases and Queries

This table is primarily accessed for troubleshooting, data validation, and legacy reporting related to student inquiry test submissions. A common operational query involves retrieving all segment scores for a specific inquiry test to validate data completeness before further processing. For example: 

SELECT INQ_TEST_SEG_ID, TEST_SEGMENT_ID, TEST_SCORE, STATUS
FROM IGS.IGS_SS_INQ_TESTSEG
WHERE INQ_TEST_ID = :p_inq_test_id
ORDER BY TEST_SEGMENT_ID;
Another typical use case is identifying staged test segment records that are in an error or pending status for reconciliation: 
SELECT *
FROM IGS.IGS_SS_INQ_TESTSEG
WHERE STATUS NOT IN ('PROCESSED', 'COMPLETE')
AND CREATION_DATE > SYSDATE - 30;
Given the "obsolete" designation, direct transactional use by new customizations is not recommended. However, queries may be necessary for historical data extraction or migration projects.

Related Objects

The table maintains defined relationships with other key EBS Student Systems tables, primarily through foreign key constraints. Based on the provided relationship data:

  • Primary Key: The table is uniquely identified by the constraint IGS_SS_INQ_TESTSEG_PK on the column INQ_TEST_SEG_ID.
  • Foreign Key (Outbound): The column INQ_TEST_ID references the parent table IGS.IGS_SS_INQ_TEST. This is a critical relationship, as every test segment must be associated with a master inquiry test record. A typical join for reporting would be: 
    SELECT seg.*, test.inquiry_id
FROM IGS.IGS_SS_INQ_TESTSEG seg,
     IGS.IGS_SS_INQ_TEST test
WHERE seg.INQ_TEST_ID = test.INQ_TEST_ID;
The dependency information notes that the table is referenced by the APPS synonym IGS_SS_INQ_TESTSEG, which is the standard access point for EBS application code. No other referencing objects are listed in the provided excerpt.