Results for “igs_ad_test_segs_int”

39 results




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

Overview

The IGS_AD_TEST_SEGS_INT table resides in the IGS (Student System) schema and serves as an interface staging table within the Oracle E-Business Suite admissions test management framework. As documented in the ETRM metadata for release 12.1.1, the table holds person's test segment details — specifically, inbound test segment score data captured prior to validation and loading into the core admissions test tables. The table is a validated object owned by IGS and contains 49 columns, reflecting the broad attribute footprint typical of EBS open-interface tables.

From a Data Vault modeling perspective, the metadata's heuristic classification identifies this object as standalone. This classification is a modeling suggestion only: because the table's foreign keys resolve to two different parent entities (test segments and test results), an alternate reading would treat it as a link-style structure connecting those parents, with descriptive score attributes behaving as satellite content. In practice the object functions as a transient landing zone, so its standalone classification reflects the fact that it is not itself a durable hub, link, or satellite in the warehouse sense.

Key Information Stored

The surrogate primary key is IGS_AD_TEST_SEGS_INT_PK, defined on INTERFACE_TEST_ID. A separate unique index, IGS_AD_TEST_SEGS_INT_ALL_U1, is defined on INTERFACE_TESTSEGS_ID, making that column the principal business-key candidate for row-level de-duplication and matching.

The remaining columns supply standard EBS audit and concurrency fields plus twenty generic ATTRIBUTE columns (ATTRIBUTE_CATEGORY through ATTRIBUTE20) for extensibility.

Common Use Cases and Queries

Typical usage centers on validating inbound test data before it is promoted to the operational admissions tables. Error handling is the dominant reporting pattern:

  • Identifying rows that failed validation prior to a retry or correction cycle.
  • Reconciling interface counts against source files by interface run.
  • Reviewing score and percentile distributions for admissions committees.

A query to surface failed rows for a given interface run would follow this pattern:

SELECT t.INTERFACE_TESTSEGS_ID, t.TEST_SEGMENT_ID, t.TEST_SCORE, t.STATUS, t.ERROR_CODE, t.ERROR_TEXT FROM IGS_AD_TEST_SEGS_INT t WHERE t.INTERFACE_TEST_ID = :p_interface_test_id AND t.STATUS = 'E';

Joining to the parent segment table supports enrichment reporting, for example linking TEST_SEGMENT_ID to IGS_AD_TEST_SEGMENTS while filtering on INTERFACE_RUN_ID to constrain the population to a single load.

Related Objects

The table's dependency graph is compact and defined by its two declared foreign keys:

  • IGS_AD_TEST_SEGMENTS — Referenced via TEST_SEGMENT_ID; holds the authoritative test segment definition.
  • IGS_AD_TEST_RESULTS — Referenced via TEST_RESULTS_ID; holds the parent test result records.
  • IGS_AD_TEST_RESULTS_INT — Companion interface table for test results, populated in the same batch as this segment interface.
  • IGS_AD_TEST_SEGMENTS_INT — Companion interface table for segment definitions.

Concurrent programs that import admissions test data read from IGS_AD_TEST_SEGS_INT, validate the rows using ERROR_CODE and ERROR_TEXT, then insert the survivors into IGS_AD_TEST_SEGMENTS and IGS_AD_TEST_RESULTS. Because the table is an interface object, no other IGS table declares a foreign key back to it, consistent with its standalone classification.