Results for “question_id”

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

Overview

OTA_TEST_QUESTIONS is a bridge (intersection) table within the Oracle E-Business Suite Learning Management module (OTA). It associates individual questions from the question bank with specific sections of a pre-selected test — that is, a test whose TYPE_FLAG is set to S. In addition to the question-to-section mapping, the table also carries the owning test identifier, which means it effectively joins three parent entities: the test, its section, and the question drawn from a question bank. The table therefore governs exactly which questions are presented under which sections when a pre-selected test is assembled and delivered to learners.

From a Data Vault modeling perspective, the heuristic classification of this object is a link table. This is a natural fit: the object exists solely to resolve a many-to-many relationship between parent hubs (tests, sections, questions, and question banks) and holds no descriptive attributes of its own beyond sequencing and audit columns. A Data Vault implementation would typically model OTA_TEST_QUESTIONS as a link connecting the test, section, question, and question bank hubs.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• TEST_QUESTION_ID — the surrogate primary key (index OTA_TEST_QUESTIONS_PK), uniquely identifying each row.
• TEST_ID — foreign key to OTA_TESTS identifying the parent test.
• SECTION_ID — foreign key to OTA_TEST_SECTIONS identifying the section under which the question is displayed.
• QUESTION_ID — foreign key to OTA_QUESTIONS identifying the specific question.
• QUESTION_BANK_ID — foreign key to OTA_QUESTION_BANKS identifying the bank from which the question originates.
• SEQUENCE — controls the ordering in which questions appear within a section.
• BUSINESS_GROUP_ID — the multi-tenant partition key standard across EBS HR/OTA tables.
• OBJECT_VERSION_NUMBER — optimistic locking / concurrency control column.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO-column audit set.

The business-key candidate is captured by the unique index OTA_TEST_QUESTIONS_UK1, comprising TEST_ID, QUESTION_BANK_ID, QUESTION_ID. This guarantees that any given question from a given bank appears only once per test, preventing accidental duplication of questions across a test's sections. The surrogate TEST_QUESTION_ID is distinct from this composite business key.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include reconstructing the full content of a pre-selected test, auditing question ordering, and confirming which bank a question was sourced from. A representative query listing every question in a test, ordered by section and sequence, is:

• SELECT tq.TEST_ID, tq.SECTION_ID, tq.SEQUENCE, tq.QUESTION_ID, tq.QUESTION_BANK_ID FROM OTA.OTA_TEST_QUESTIONS tq WHERE tq.TEST_ID = :p_test_id ORDER BY tq.SECTION_ID, tq.SEQUENCE;
• Joining to OTA_QUESTIONS to retrieve question text or type for a test assembly report.
• Joining to OTA_TEST_SECTIONS to report section names and question counts per section.
• Validating integrity by checking for orphaned QUESTION_ID or SECTION_ID values against their parent tables.

Related Objects

The following objects are directly referenced through foreign key relationships documented in the ETRM metadata:

• OTA_TESTS — joined on TEST_ID; the parent test definition.
• OTA_TEST_SECTIONS — joined on SECTION_ID; groups questions within a test.
• OTA_QUESTIONS — joined on QUESTION_ID; the question master.
• OTA_QUESTION_BANKS — joined on QUESTION_BANK_ID; the source bank of each question.

Together these four parent tables form the referential backbone of the pre-selected test structure, with OTA_TEST_QUESTIONS acting as the linking mechanism that binds test, section, and question together.