Results for “adm_test_type”

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

Overview

IGS_SS_TEST_RESULTS is a transactional table in the IGS (Student System) product schema of Oracle E-Business Suite, documented as VALID in ETRM releases 12.1.1 and 12.2.2. It stores Test Results details captured for an Online Admission Application. In the self-service admissions flow, prospective applicants record standardized or institution-specific test outcomes — such as TOEFL, GRE, GMAT, or internal placement examinations — that admissions officers subsequently evaluate as part of the application decision. The table therefore acts as the persistence layer for test-score entry and validation within the online application pages, sitting downstream of the applicant-facing self-service UI and upstream of admissions evaluation and decision processing.

The ETRM relationship metadata classifies this object heuristically as standalone under Data Vault modeling conventions. In practice this means no foreign key relationships were mined from the documented structure, suggesting the table behaves as an independent record set keyed solely by its own surrogate identifier rather than as a hub or link participating in a shared business-key network. A Data Vault modeler might therefore treat it as a satellite-like structure anchored to a person or application hub at the logical level, while noting that the physical implementation in EBS carries no enforced declarative foreign keys to those parent entities.

Key Information Stored

The documented physical schema for release 12.1.1 contains 12 columns. The most significant are:

• SS_TEST_RESULTS_ID — the surrogate primary key, enforced by unique index IGS_SS_TEST_RESULTS_PK. This is the sole documented unique index and the only business-key candidate identified; the table carries no other unique constraint in the ETRM record.
• PERSON_ID — identifies the person (applicant) to whom the test result belongs. Although no foreign key is documented, this column logically references the person/party model and is the primary linkage used in reporting.
• ADM_TEST_TYPE — the admissions test type, distinguishing which examination the score relates to.
• TEST_DATE — the date the test was taken or the result recorded.
• SCORE_TYPE — classifies the nature or format of the score reported.
• COMP_TEST_SCORE — the composite or component test score value captured from the applicant.
• STATUS — the processing state of the test result record.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO columns supporting auditability and concurrency control.

Absent any additional unique index beyond the primary key, duplication control on business attributes such as person plus test type must be enforced in the application layer rather than by the database.

Common Use Cases and Queries

Typical reporting retrieves all test results for a given applicant, or summarizes scores by test type across an admissions cycle.

• Applicant score retrieval: SELECT ADM_TEST_TYPE, TEST_DATE, COMP_TEST_SCORE, STATUS FROM IGS_SS_TEST_RESULTS WHERE PERSON_ID = :person_id;
• Score validation and completeness checks prior to an admissions decision.
• Cycle-level reporting on test-type volume and score distributions.
• Data reconciliation between the self-service application and the admissions office review screen.
• Audit queries using LAST_UPDATE_DATE and LAST_UPDATED_BY to trace who entered or amended a score.

Related Objects

The documented metadata confirms no FK relationships, so associations below are logical rather than declarative:

• IGS_SS_TEST_RESULTS_PK — the unique index backing the SS_TEST_RESULTS_ID primary key.
• PERSON_ID linkage — to the person/party tables in the IGS/HR foundation used to resolve applicant identity.
• Online Admission Application objects in the IGS self-service family, which call the pages that write to this table.
• Admissions test type and score type lookup tables referenced by ADM_TEST_TYPE and SCORE_TYPE.
• Admissions decision and evaluation entities that consume these results downstream.