Search Results test_segment_name




Overview
Explore in AI Chat

Overview

IGS_AD_TST_RSLT_DTLS_V is a reporting and integration view owned by the APPS schema in the Oracle EBS Student System (IGS) product family. It exposes admissions test result detail records in a denormalized, presentation-ready form, resolving foreign key identifiers into their descriptive equivalents and flattening the transactional detail table for downstream consumption. The view is valid in Oracle EBS 12.1.1 and 12.2.2 and is intended for use by concurrent programs, OBIEE/XML Publisher reports, and interface extracts where a single row per test result detail line is required, enriched with the segment name, segment type, segment group, and irregularity code description.

The object plays a supporting role in admissions processing: it lets functional users and developers avoid re-implementing the joins between test result details, test segments, and code classes, and it delivers a stable column list suitable for external test score file imports and score reporting.

Underlying Base Objects

The view definition is a three-table join. The driving table is IGS_AD_TST_RSLT_DTLS (aliased TRD), which stores the individual score and percentile lines for a test result. It is inner-joined to IGS_AD_TEST_SEGMENTS (aliased TS) on TEST_SEGMENT_ID, meaning only detail rows with a valid segment are returned. It is outer-joined to IGS_AD_CODE_CLASSES (aliased CC) on CC.CODE_ID (+) = TRD.IRREGULARITY_CODE_ID, so a row is still returned even when no irregularity code is assigned; the irregularity code name is then null.

The documented referenced base objects are IGS_AD_TST_RSLT_DTLS, IGS_AD_TEST_SEGMENTS, and IGS_AD_CODE_CLASSES. Because the view exposes TRD.ROWID as ROW_ID, it is not directly updateable through the ROW_ID column in the usual sense; DML should target IGS_AD_TST_RSLT_DTLS directly.

Key Columns

Common Use Cases and Queries

A typical use is to report test results grouped by segment with irregularity codes flagged. Because the user query concerned irregularity_code_id, the following pattern is common:

  • Filtering all detail rows for a given test result: SELECT test_segment_name, test_score, percentile, irregularity_code_name FROM igs_ad_tst_rslt_dtls_v WHERE test_results_id = :p_results_id;
  • Identifying lines with an irregularity assigned: SELECT tst_rslt_dtls_id, test_segment_name, irregularity_code_id, irregularity_code_name FROM igs_ad_tst_rslt_dtls_v WHERE irregularity_code_id IS NOT NULL;
  • Looking up a code description by joining back to the code classes table or filtering on irregularity_code_id for a specific value.
  • Extracting score bands and percentile data for XML Publisher test score reports or inbound score file validation, using the flexfield attributes to carry external file metadata.

Before using the view, verify that the IGS admissions tables are populated for the operating unit in scope and that the outer-joined code classes row is expected to exist for any flagged irregularity.