Search Results ota_qbank_questions_pk




Overview

The OTA_QBANK_QUESTIONS table is a core data object within the Oracle E-Business Suite (EBS) Learning Management (OTA) module, specifically in versions 12.1.1 and 12.2.2. It functions as a bridge or junction table designed to resolve a many-to-many (N:N) relationship between two primary entities: question banks (OTA_QUESTION_BANKS) and individual questions (OTA_QUESTIONS). Its role is to enable the flexible association of a single question to multiple banks and a single bank to contain multiple questions, thereby providing a reusable and organized structure for managing assessment content. This table is essential for the underlying data model supporting the creation, categorization, and administration of tests and quizzes.

Key Information Stored

The table's structure is minimal, containing only the two foreign key columns that define each unique association. The primary data stored consists of paired identifiers. The QUESTION_BANK_ID column stores the unique identifier (primary key) of a specific question bank or category from the OTA_QUESTION_BANKS table. The QUESTION_ID column stores the unique identifier (primary key) of a specific assessment question from the OTA_QUESTIONS table. Together, these two columns form the composite primary key (OTA_QBANK_QUESTIONS_PK), ensuring that any specific question-to-bank relationship is recorded only once within the system.

Common Use Cases and Queries

A primary use case is reporting and administration, allowing administrators to list all questions within a specific bank or to identify all banks containing a particular question. This is critical for content reuse, version control, and audit trails. Common SQL queries involve joining this bridge table to its parent tables. For example, to retrieve all questions for a specific bank name:

  • SELECT q.question_text, q.question_id FROM ota_questions q, ota_qbank_questions bq, ota_question_banks qb WHERE q.question_id = bq.question_id AND bq.question_bank_id = qb.question_bank_id AND qb.name = '&BANK_NAME';

Another typical pattern is to find unused questions not assigned to any bank, which would involve a NOT EXISTS or outer join query against OTA_QBANK_QUESTIONS.

Related Objects

The OTA_QBANK_QUESTIONS table has direct, documented dependencies on two key master tables via foreign key constraints, and it is central to the question bank data model.

  • OTA_QUESTIONS: This table stores the master definition of all assessment questions. The OTA_QBANK_QUESTIONS.QUESTION_ID column references OTA_QUESTIONS, linking an association record to the specific question details.
  • OTA_QUESTION_BANKS: This table stores the definitions of question banks or categories. The OTA_QBANK_QUESTIONS.QUESTION_BANK_ID column references OTA_QUESTION_BANKS, linking an association record to the specific bank.

These relationships enforce referential integrity, ensuring that associations are only created for valid questions and banks. The table is primarily accessed through the standard Learning Management user interface for test creation and maintenance.

  • Table: OTA_QBANK_QUESTIONS 12.2.2

    owner:OTA,  object_type:TABLE,  fnd_design_data:OTA.OTA_QBANK_QUESTIONS,  object_name:OTA_QBANK_QUESTIONS,  status:VALID,  product: OTA - Learning Managementdescription: This table acts as a bridge table between OTA_QUESTION_BANKS and OTA_QUESTIONS because of the N:N relation that could be specified between the two entities. ,  implementation_dba_data: OTA.OTA_QBANK_QUESTIONS

  • Table: OTA_QBANK_QUESTIONS 12.1.1

    owner:OTA,  object_type:TABLE,  fnd_design_data:OTA.OTA_QBANK_QUESTIONS,  object_name:OTA_QBANK_QUESTIONS,  status:VALID,  product: OTA - Learning Managementdescription: This table acts as a bridge table between OTA_QUESTION_BANKS and OTA_QUESTIONS because of the N:N relation that could be specified between the two entities. ,  implementation_dba_data: OTA.OTA_QBANK_QUESTIONS