Search Results test_segment_name




Overview
Explore in AI Chat

Overview

IGS_AD_TEST_SCORES_V is a reporting view in the Oracle E-Business Suite application schema APPS, belonging to the Student System (Oracle Student System / IGS) product family. It presents admissions test score information for a person, resolving the coded lookups that underlie admissions test records into their human-readable descriptions. The view is part of the admissions (IGS_AD) module and is intended primarily for inquiry, reporting, and integration scenarios where a flat, denormalized representation of test results is preferable to joining the normalized base tables directly.

The user's search term, "test_segment_name," corresponds directly to the TEST_SEGMENT column exposed by this view. That column is not stored on the view's driving table; it is derived through an inline scalar sub-query against IGS_AD_TEST_SEGMENTS, which returns TEST_SEGMENT_NAME for the matching TEST_SEGMENT_ID. This makes the view the practical access point when the segment name is the value of interest.

Underlying Base Objects

The view is defined over the following base and resolved objects:

The joins are deliberately outer so that a header test result with no detail rows, or a detail row with no matching segment definition, is still returned rather than dropped. The ETRM metadata documents no separately named base objects, so the definition itself is the authoritative source of these relationships.

Key Columns

  • ROW_ID — the ROWID of the driving IGS_AD_TEST_RESULTS row; useful for identifying duplicates or performing row-level updates.
  • TEST_RESULTS_ID, PERSON_ID — identifiers for the test result record and the person to whom it belongs.
  • TEST_TYPE, TEST_DATE — the admission test type and the date the test was taken.
  • SCORE_SOURCE — decoded name from IGS_AD_CODE_CLASSES for the score source.
  • SCORE_TYPE, SCORE_TYPE_MEANING — the lookup code and its meaning from IGS_LOOKUP_VALUES.
  • TEST_SEGMENT — the segment name resolved from IGS_AD_TEST_SEGMENTS; this is the column sought by the "test_segment_name" search.
  • SEGMENT_SCORE, COMBINED_SCORE — the detail-level test score and the header-level composite score.
  • SEGMENT_TYPE, SEGMENT_GROUP — classification of the segment from IGS_AD_TEST_SEGMENTS.
  • ACTIVE_IND and audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — standard transactional audit attributes.

Common Use Cases and Queries

The view is typically used to list a person's test results with readable segment names, to report on segments of a given type or group, and to feed downstream integration extracts. A representative query returning segment-level scores for a person is:

  • SELECT person_id, test_type, test_date, test_segment, segment_score, score_type_meaning FROM apps.igs_ad_test_scores_v WHERE person_id = :p_person_id AND active_ind = 'Y';
  • SELECT test_segment, segment_type, segment_group, segment_score FROM apps.igs_ad_test_scores_v WHERE test_results_id = :p_test_results_id ORDER BY test_segment;
  • SELECT person_id, test_date, combined_score, test_segment FROM apps.igs_ad_test_scores_v WHERE score_type = :p_score_type AND test_date BETWEEN :p_from AND :p_to;

Because TEST_SEGMENT and SCORE_SOURCE are resolved through scalar sub-queries on each execution, queries filtering heavily on segment name are more efficient when filtered on TEST_SEGMENT_ID or TEST_RESULTS_ID where available, and most product reporting uses this view in conjunction with a person or test-result key rather than as a full-table scan source.