Search Results test_segmt_score

Overview

The IGS_DA_OUT_TST_SGMT table is a data store within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically in the IGS (presumably Institutional Global Systems) schema. Its documented purpose is to store outgoing information on test segments for tests associated with students selected in a processing request. This table functions as a staging or interface table, likely used by batch processes to hold segmented test score data (e.g., SAT Math, SAT Verbal) before it is transmitted or further processed. The ETRM metadata explicitly marks this table as "Obsolete," indicating it is part of a legacy data model that may be superseded in current or future implementations. Its storage in the APPS_TS_INTERFACE tablespace further supports its role as a transient data repository for interface operations.

Key Information Stored

The table's structure is designed to uniquely identify a test segment score for a specific person and request batch. The primary key is a composite of BATCH_ID, PERSON_ID, TEST_SEQ_NUM, and TEST_SEGMT_NAME. Key data columns include:

• BATCH_ID: A unique identifier linking all records belonging to a specific processing request.
• PERSON_ID: The unique identifier for the student or person.
• TEST_SEQ_NUM: A sequence number that references the parent test record from a related tests table, crucial for joining to the main test information.
• TEST_SEGMT_NAME: The name of the specific test segment (e.g., 'MATH', 'VERBAL').
• TEST_SEGMT_SCORE: The numerical score achieved for the named test segment.

The table also includes standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing.

Common Use Cases and Queries

This table is primarily accessed for reporting on batched test segment data or for troubleshooting interface processes. A common query would retrieve all segment scores for a specific batch to verify outgoing data integrity. Given the user's search for "test_seq_num," a frequent pattern involves joining this table to a parent test table using BATCH_ID, PERSON_ID, and TEST_SEQ_NUM to get a complete view of test and segment details.

Sample Query: Retrieving all test segment details for a specific batch and person.

SELECT seg.TEST_SEGMT_NAME,
       seg.TEST_SEGMT_SCORE,
       seg.TEST_SEQ_NUM
FROM IGS.IGS_DA_OUT_TST_SGMT seg
WHERE seg.BATCH_ID = :batch_id
  AND seg.PERSON_ID = :person_id
ORDER BY seg.TEST_SEQ_NUM;

Another critical use case is data validation before transmission, ensuring that for every TEST_SEQ_NUM present, the required segment scores (TEST_SEGMT_NAME and TEST_SEGMT_SCORE) are populated.

Related Objects

The table's relationships are defined by its primary key and foreign keys. The primary key constraint IGS_DA_OUT_TST_SGMT_PK enforces uniqueness on the composite columns. According to the provided relationship data, a foreign key exists where this table's BATCH_ID column references another table, IGS_DA_OUT_TSTS. This indicates that IGS_DA_OUT_TST_SGMT is a child table, with its batch context governed by a parent table storing the main outgoing test information. The TEST_SEQ_NUM column is also documented as referencing a "parent" test sequence number found in a tests table, though the specific table name is not provided in the excerpt. The dependency information notes that an APPS synonym (IGS_DA_OUT_TST_SGMT) exists for this table, allowing access from the central APPS schema.