Results for “test_seq_num”

2 results




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

Overview

IGS_DA_OUT_TST_SGMT is a table in the IGS (Student System) product schema of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. It stores outgoing information about the test segments associated with the tests identified for a student within a Degree Audit Request. In the Degree Audit processing flow, the audit engine evaluates a student's academic record against program requirements and produces structured output that describes the tests, sub-tests, and segments that the student has satisfied, is deficient in, or is otherwise flagged against. This table is the persistence point for the segment-level portion of that output, so it sits at the detail end of the Degree Audit output hierarchy.

From a data-modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table's primary key includes the composite identifier of its parent test record plus the segment name, meaning the table extends and describes a parent business entity rather than independently identifying one. The rows carry the descriptive and load-metadata attributes typical of a satellite structure, with the full business key repeated within the primary key.

Key Information Stored

The table is documented with ten columns. Four of these form the composite primary key, IGS_DA_OUT_TST_SGMT_PK, and the same four columns constitute the unique index IGS_DA_OUT_TST_SGMT_U1, making them the business-key candidates: BATCH_ID, PERSON_ID, TEST_SEQ_NUM, and TEST_SEGMT_NAME.

  • BATCH_ID — Identifies the Degree Audit request batch that produced the outgoing record. This is part of the foreign key that links the row back to its parent test record.
  • PERSON_ID — The identifier of the student for whom the Degree Audit was executed. Combined with BATCH_ID and TEST_SEQ_NUM, it anchors the row to the correct student-test combination.
  • TEST_SEQ_NUM — The sequence number of the test found for the student within the Degree Audit request. Together with BATCH_ID and PERSON_ID it forms the composite foreign key into the parent test table.
  • TEST_SEGMT_NAME — The name of the test segment being reported. This is the final component of the primary key and distinguishes multiple segment rows belonging to the same test.
  • TEST_SEGMT_SCORE — The score or value recorded for the test segment. This is the principal descriptive payload of the row and the column most commonly surfaced in reporting.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard Oracle EBS audit/WHO columns that capture row creation and last modification metadata for auditing and change-tracking purposes.

Common Use Cases and Queries

This table is typically queried in Degree Audit reporting and diagnostic contexts. Analysts extracting a student's audit results join segment rows back to the parent test table to reconstruct the full test-to-segment hierarchy. A representative query pattern selects the segment score for a given student and batch:

  • Reporting on segment-level scores for a student within a specific Degree Audit batch, filtered by PERSON_ID and BATCH_ID.
  • Comparing the segments reported for the tests found for a student against expected program requirements.
  • Data validation and reconciliation during Degree Audit processing, checking that each test has the expected set of segment rows.
  • Auditing row provenance and change history using the WHO columns, for example identifying rows created or updated after a specific date.

A typical SQL skeleton joins IGS_DA_OUT_TST_SGMT to IGS_DA_OUT_TSTS on BATCH_ID, PERSON_ID, and TEST_SEQ_NUM, restricting by PERSON_ID to retrieve all segment-level output for the student, and optionally pivoting or aggregating on TEST_SEGMT_NAME.

Related Objects

The principal related object is the parent table that this table extends. The documented foreign key relationship is:

  • IGS_DA_OUT_TSTS — Referenced through the composite foreign key columns BATCH_ID, PERSON_ID, and TEST_SEQ_NUM. Every segment row must correspond to an existing test row for the same batch and student.

Because the metadata provided covers only this single foreign key, the broader Degree Audit output family—including the batch and request-level tables that feed IGS_DA_OUT_TSTS—are related by inference through the BATCH_ID and PERSON_ID columns rather than by documented direct keys. Application logic that populates the Degree Audit output writes to IGS_DA_OUT_TSTS first and then to this segment table, so any extraction or interface that consumes Degree Audit results should treat IGS_DA_OUT_TST_SGMT as the terminal detail source beneath IGS_DA_OUT_TSTS.