Results for “test_score_active”

3 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_DA_OUT_TSTS is a table within the IGS (Student System) product schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the persistent storage location for outgoing test information associated with a student within a Degree Audit Request. In the degree audit process, student test data—such as standardized test scores, placement examinations, and institutional test results—must be evaluated against academic requirements. This table captures the test records that the degree audit engine emits or transmits as part of that evaluation, rather than the raw incoming test data held elsewhere in the student system.

The object is owned by the IGS schema and holds a status of VALID in the documented environment. The table is physically defined with 34 columns in the ETRM 12.1.1 documentation. Its primary key, IGS_DA_OUT_TSTS_PK, is a composite of BATCH_ID, PERSON_ID, and TEST_SEQ_NUM. A unique index, IGS_DA_OUT_TSTS_U1, mirrors this same column set, confirming it as the business-key candidate for the table.

From a data-modeling perspective, the heuristic Data Vault classification for this object is satellite-leaning, based on the mined foreign key structure. This suggests that, in a warehouse or analytics model, IGS_DA_OUT_TSTS would most naturally be modeled as a satellite attached to a parent hub or link representing the degree audit request and student, rather than as an independent hub or a connecting link table.

Key Information Stored

The table's identifying structure comprises three key columns. BATCH_ID identifies the degree audit processing batch, PERSON_ID identifies the student, and TEST_SEQ_NUM is a sequence number distinguishing individual test records within a batch and student combination. Together these three form the surrogate primary key, which doubles as the unique business key.

The most significant descriptive columns include:

  • TEST_TYPE — categorizes the test (for example, admissions, placement, or institutional test).
  • TEST_DATE — the date the test was taken or recorded.
  • TERM — the academic term associated with the test record.
  • SPECIAL_CODE — a code flagging special handling or conditions for the test.
  • COMPOSITE_SCORE — the aggregate or composite score derived from the test.
  • TEST_SCORE_ACTIVE — an indicator of whether the test score is currently active.
  • TEST_SCORE_ATTR1 through TEST_SCORE_ATTR20 — a wide block of twenty generic attribute columns that store flexible, institution-configurable test score details. These provide extensibility for varied test formats without schema changes.

The table also carries standard Oracle EBS audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATED_BY, and LAST_UPDATE_DATE. These support auditability and change tracking across the application.

Common Use Cases and Queries

Typical use cases center on degree audit reporting and test score verification. A common pattern retrieves all outgoing test records for a specific student within a batch:

  • Querying test records by BATCH_ID and PERSON_ID to reconstruct a student's outgoing test payload for a degree audit run.
  • Reporting on active composite scores filtered by TEST_SCORE_ACTIVE for a given TERM.
  • Auditing changes by filtering on LAST_UPDATE_DATE to find test records modified since a given date.
  • Joining to the degree audit request student table to reconcile outgoing test information against the request that produced it.

A representative query joins the table to its parent via the composite key:

SELECT o.PERSON_ID, o.TEST_TYPE, o.TEST_DATE, o.COMPOSITE_SCORE FROM IGS_DA_OUT_TSTS o WHERE o.BATCH_ID = :batch_id AND o.PERSON_ID = :person_id AND o.TEST_SCORE_ACTIVE = 'Y';

Because TEST_SCORE_ATTR columns are generically named, reporting teams typically consult institution-specific configuration to map each attribute to its business meaning before including them in extracts.

Related Objects

IGS_DA_OUT_TSTS participates in a defined set of foreign key relationships within the IGS schema. The most significant related objects are:

  • IGS_DA_REQ_STDNTS — the parent table representing students on the degree audit request. IGS_DA_OUT_TSTS references it via BATCH_ID and PERSON_ID, establishing the request context for each outgoing test record.
  • IGS_DA_OUT_TST_SGMT — a child table that references IGS_DA_OUT_TSTS through BATCH_ID, PERSON_ID, and TEST_SEQ_NUM. This table stores the segmented detail of outgoing test information, meaning one test record can be composed of multiple segments.

The relationship to IGS_DA_REQ_STDNTS places each test record firmly within a specific degree audit request batch and student, while the dependency from IGS_DA_OUT_TST_SGMT means that any deletion or key change on IGS_DA_OUT_TSTS can cascade into the segment detail. Understanding both the parent and child relationships is essential when designing extracts, since the complete outgoing test picture requires the header record here and its associated segments in IGS_DA_OUT_TST_SGMT.