Results for “object_type_flag”

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

Overview

OTA_UTEST_QUESTIONS is a transactional table in the Oracle E-Business Suite Learning Management (OTA) module. It stores the test definition — the individual questions that make up a test — and the per-attempt instance of each question. Whenever a learner takes a test, a new test instance is generated, and the questions comprising that instance are recorded here. If the test is resumable and the learner resumes an old attempt, the questions are re-associated with the existing attempt via the ATTEMPT_ID foreign key.

Each row represents one question posed to a learner within a specific test attempt, capturing the question's identity, its scoring information, and the learner's interaction state. The table therefore functions as the bridge between the abstract test definition (the bank of questions) and the concrete responses a learner submits, which are stored in OTA_UTEST_RESPONSES. The documented physical schema records 16 columns owned by the OTA schema. Based on the foreign key topology, the heuristic Data Vault classification is satellite-leaning: the table describes an attempt (a hub-like parent) and carries descriptive, attempt-scoped attributes rather than acting as a pure many-to-many linking construct.

Key Information Stored

The surrogate primary key, enforced by unique index OTA_UTEST_QUESTIONS_PK, is USER_TEST_QUESTION_ID. No separate business-key unique index is documented beyond this primary key, so USER_TEST_QUESTION_ID serves both as the row identifier and the join anchor for dependent data.

• USER_TEST_QUESTION_ID — Surrogate primary key; uniquely identifies one question instance within a test attempt.
• ATTEMPT_ID — Foreign key to OTA_ATTEMPTS; ties the question to the specific learner test attempt.
• OBJECT_ID and OBJECT_TYPE_FLAG — Identify the underlying question object and its type within the question bank.
• BUSINESS_GROUP_ID — Multi-tenant partition key isolating data by business group.
• PARENT_ID — Supports hierarchical or grouped question structures (for example, a parent container or sub-question relationship).
• SUGGESTED_POINTS and POINTS_AWARDED — Store the maximum attainable score for the question and the score actually earned by the learner, respectively.
• SKIPPED_FLAG — Indicates whether the learner skipped the question.
• MARKED_FOR_REVIEW_FLAG — Records whether the learner flagged the question for later review before submission.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing row creation and modification metadata.

Common Use Cases and Queries

Typical usage centers on reconstructing a learner's test experience and scoring. Reporting queries commonly join this table to OTA_ATTEMPTS to retrieve attempt-level context and to OTA_UTEST_RESPONSES for the submitted answers.

• Score reconciliation: Sum POINTS_AWARDED against SUGGESTED_POINTS per USER_TEST_QUESTION_ID to verify attempt totals.
• Engagement analysis: Count rows where SKIPPED_FLAG or MARKED_FOR_REVIEW_FLAG is set to assess learner behavior patterns.
• Attempt reconstruction: Filter by ATTEMPT_ID to list every question presented in a given attempt, ordered by USER_TEST_QUESTION_ID.

A representative pattern: SELECT q.USER_TEST_QUESTION_ID, q.POINTS_AWARDED, q.SUGGESTED_POINTS FROM OTA.OTA_UTEST_QUESTIONS q WHERE q.ATTEMPT_ID = :attempt_id. Responses are then retrieved by joining OTA_UTEST_RESPONSES on USER_TEST_QUESTION_ID.

Related Objects

The principal dependencies follow the documented foreign key relationships:

• OTA_ATTEMPTS — Referenced through OTA_UTEST_QUESTIONS.ATTEMPT_ID; the parent record defining a learner's test attempt.
• OTA_UTEST_RESPONSES — Child table referencing OTA_UTEST_QUESTIONS.USER_TEST_QUESTION_ID; stores the actual answers submitted.
• OTA_UTEST_QUESTIONS_PK — Primary key index on USER_TEST_QUESTION_ID used for unique lookups and joins.

Because ATTEMPT_ID and USER_TEST_QUESTION_ID are the dominant access paths, queries and reports should filter on these columns to leverage the documented constraints efficiently.