Results for “igs_ad_tstdtl_uh_int”

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

Overview

IGS_AD_TSTDTL_UH_INT is an interface (staging) table in the Oracle EBS Student System (IGS) product family. It holds admissions test result detail records that have been loaded from external sources and are awaiting validation and migration into the base admissions test result tables. In the Oracle EBS 12.1.1 and 12.2.2 architectures, tables with the _INT suffix serve as the landing zone for the concurrent import process, allowing data from legacy systems, third-party testing agencies, or flat-file loads to be staged before the main admissions test setup is updated.

The table is owned by the IGS schema and is classified as VALID in the ETRM data dictionary. It is a standalone object from a referential standpoint, with no child tables depending on it. Based on the heuristic Data Vault classification mined from its foreign key structure, this table is best modeled as a satellite. It carries descriptive attributes (test scores and audit columns) attached to a parent test-result entity, rather than acting as a hub or a link. This classification should be treated as a modeling suggestion, not a physical constraint enforced by the database.

Key Information Stored

The table documents 13 physical columns in the 12.1.1 schema. The most operationally significant are:

• INTERFACE_TSTDTL_ID — the surrogate primary key, defined by the constraint IGS_AD_TSTDTL_UH_INT_PK. It uniquely identifies each staged detail row.
• INTERFACE_TST_ID — foreign key to IGS_AD_TSTRST_UH_INT, linking the detail row to its parent test-result interface header.
• TEST_SEGMENT_ID — foreign key to IGS_AD_TEST_SEGMENTS, identifying the specific test segment or component to which the score applies.
• TEST_SCORE — the actual score value captured for the test segment. This is the principal business payload of the row and the field most frequently consumed by downstream validation logic.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard Oracle EBS WHO columns recording row creation and modification audit information.
• LAST_UPDATE_LOGIN — the login identifier of the user or process that last touched the record.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns that identify the request, application, and program responsible for populating or updating the interface row, enabling traceability back to the batch job.

The uniqueness of the primary key is enforced through IGS_AD_TSTDTL_UH_INT_PK on INTERFACE_TSTDTL_ID; no alternate unique indexes are documented in the ETRM metadata.

Common Use Cases and Queries

Typical usage centers on auditing staged admissions test data before or after the import concurrent program runs. Common queries include verifying that each detail row resolves to a valid header and segment, checking for orphaned rows, and reporting score distributions. A representative join pattern is:

• Join IGS_AD_TSTDTL_UH_INT to IGS_AD_TSTRST_UH_INT on INTERFACE_TST_ID = INTERFACE_TST_ID to reconcile detail rows against their parent test result.
• Join to IGS_AD_TEST_SEGMENTS on TEST_SEGMENT_ID to resolve the human-readable segment name associated with TEST_SCORE.
• Filter by REQUEST_ID to isolate rows created by a specific concurrent request, which is useful for error triage and reprocessing.

Report writers commonly aggregate TEST_SCORE by TEST_SEGMENT_ID to produce validation summaries prior to promotion into the production admissions tables.

Related Objects

The following objects are the most significant in the relationship graph:

• IGS_AD_TSTRST_UH_INT — parent interface table referenced by the INTERFACE_TST_ID foreign key. Each detail row belongs to exactly one test-result header.
• IGS_AD_TEST_SEGMENTS — segment definition table referenced by TEST_SEGMENT_ID, providing the valid list of test components.
• IGS_AD_TSTDTL_UH_INT_PK — the primary key constraint on INTERFACE_TSTDTL_ID.

These relationships confirm that the table functions as a dependent detail structure within the admissions test interface flow, consuming header and segment references while contributing score-level attributes.