Search Results test_score_type




Overview
Explore in AI Chat

Overview

IGS_AD_TEST_TYPES_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered as part of the Oracle Student System (formerly Oracle iLearning and Student Information/Academic) product family. It presents admission test type definitions together with their descriptive context, joining each test type record to its associated processing step and to the lookup value that classifies the score produced by that test. The view is read-only in practice, constructed as a three-table join with outer joins on two of its sources, and it denormalizes lookup meanings and step descriptions so that consumers do not have to resolve these codes themselves.

For reporting and integration, the view is the standard supported access path for admission test configuration. Rather than querying IGS_AD_TEST_TYPE directly and manually resolving SCORE_TYPE codes against FND_LOOKUPS or the lookups view, callers use IGS_AD_TEST_TYPES_V to obtain the human-readable score type meaning directly. The user-facing search term "test_score_type" corresponds precisely to the SCORE_TYPE and SCORE_TYPE_MEANING columns returned here, making this view the primary reference for that lookup type.

Underlying Base Objects

The documented definition of the view references three objects in its FROM clause:

  • IGS_AD_TEST_TYPE (aliased TT) — the driving table, holding admission test type rows. The view selects ROWID from this table as ROW_ID, along with the descriptive, audit, and classification columns.
  • IGS_TR_STEP_CTLG (aliased SC) — the transfer step catalog, joined on TT.STEP_CODE = SC.STEP_CATALOG_CD using an outer join (SC.STEP_CATALOG_CD(+)), so test types without a matching step code are still returned.
  • IGS_LOOKUPS_VIEW (aliased LV) — the lookup view, joined on TT.SCORE_TYPE = LV.LOOKUP_CODE with the filter LV.LOOKUP_TYPE = 'TEST_SCORE_TYPE'. This join is written without the outer-join operator, so a valid SCORE_TYPE lookup row is required for a test type to appear.

Because the lookups filter is fixed to TEST_SCORE_TYPE, the view effectively publishes only test types whose score type is a recognized lookup in that lookup type. Note that the metadata documents no additional referenced base objects beyond these three.

Key Columns

  • ROW_ID — the ROWID of the underlying IGS_AD_TEST_TYPE row, useful for DML targeting and row identification.
  • ADMISSION_TEST_TYPE — the primary identifier/code for the admission test type.
  • DESCRIPTION — the descriptive name of the test type.
  • STEP_CODE and STEP_CODE_DESC — the step catalog code and its resolved description from IGS_TR_STEP_CTLG.
  • SCORE_TYPE — the lookup code classifying the score produced by the test; this is the "test_score_type" value.
  • SCORE_TYPE_MEANING — the meaningful description of SCORE_TYPE sourced from IGS_LOOKUPS_VIEW, where LOOKUP_TYPE = 'TEST_SCORE_TYPE'.
  • CLOSED_IND — indicates whether the test type is closed to new usage.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, inherited directly from the base table.

Common Use Cases and Queries

Typical scenarios include building admission test configuration reports, populating LOV-style queries, validating score types before data load, and extracting reference data for integrations into external assessment systems.

To list all active admission test types with resolved score type meanings:

  • SELECT ADMISSION_TEST_TYPE, DESCRIPTION, STEP_CODE_DESC, SCORE_TYPE, SCORE_TYPE_MEANING FROM APPS.IGS_AD_TEST_TYPES_V WHERE CLOSED_IND = 'N' ORDER BY ADMISSION_TEST_TYPE;

To find test types grouped by score type for a specific step:

  • SELECT SCORE_TYPE, SCORE_TYPE_MEANING, COUNT(*) FROM APPS.IGS_AD_TEST_TYPES_V WHERE STEP_CODE = :step_code GROUP BY SCORE_TYPE, SCORE_TYPE_MEANING;

To identify recently changed configuration for audit purposes:

  • SELECT ADMISSION_TEST_TYPE, SCORE_TYPE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM APPS.IGS_AD_TEST_TYPES_V WHERE LAST_UPDATE_DATE >= :since ORDER BY LAST_UPDATE_DATE DESC;

Because the lookup and step outer joins may yield NULLs in STEP_CODE_DESC, reports should handle null descriptions gracefully. Filtering on SCORE_TYPE is the most direct way to satisfy a "test_score_type" query requirement.