Results for “finished_date”

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

Overview

OTA_ATTEMPTS is a transaction-level table in the Oracle E-Business Suite learning management module (OTA). It records each instance in which a learner plays or interacts with an online learning object. One row is created per learner action against a specific learning object, making the table the central audit trail for online learning activity. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the OTA schema and is classified as VALID. The physical schema documents 48 columns, supporting both native online learning and SCORM-conformant content delivery.

From a Data Vault modeling perspective, the metadata heuristic classifies OTA_ATTEMPTS as satellite-leaning. It carries descriptive, time-stamped attributes tied to a learner activity event, with foreign keys anchoring it to established dimension-like parents (events, learning objects, enrollment records). This suggests the table is best modeled as the descriptive detail surrounding a business event, rather than as a pure hub or link.

Key Information Stored

ATTEMPT_ID is the surrogate primary key and the column most commonly referenced by users searching on the term. It uniquely identifies each attempt and is enforced by the OTA_ATTEMPTS_PK unique index. The remaining significant columns include:

• USER_ID — the learner who initiated the attempt.
• LEARNING_OBJECT_ID and TARGET_LEARNING_OBJECT_ID — the content object being played and any target object.
• EVENT_ID — the scheduled learning event or offering context.
• ATTEMPT_STATUS, PREVIOUS_STATUS, RAW_STATUS — the lifecycle status of the attempt and its prior values.
• SCORE, RAW_SCORE, SCALED_SCORE, MASTERY_SCORE — scoring results, including pass/mastery thresholds.
• COMPLETION_STATUS, SUCCESS_STATUS, GRADE_FLAG — outcome indicators.
• ATTEMPT_ORDER, ATTEMPT_TYPE — sequencing and nature of the attempt.
• TIME, TIME_EXTENDED, FINISHED_DATE — duration and completion timing.
• CERT_PRD_ENROLLMENT_ID — linkage to certification enrollment.
• SCORM_LEARNER_ATTEMPT_ID, SCORM_SUSPEND_DATA — SCORM-specific tracking.

Though the primary key is the sole documented unique business key candidate, ATTEMPT_ID is a surrogate; the natural business keys are the composite of USER_ID, LEARNING_OBJECT_ID, and EVENT_ID across attempts.

Common Use Cases and Queries

Typical reporting includes learner attempt history, online course completion tracking, and SCORM progress monitoring. A common query retrieves all attempts for a learner:

• SELECT attempt_id, learning_object_id, attempt_status, score, finished_date FROM ota_attempts WHERE user_id = :p_user_id;
• Joining to OTA_EVENTS and OTA_LEARNING_OBJECTS to resolve descriptions for reporting.
• Aggregating mastery and completion rates per learning object for compliance dashboards.

Related Objects

OTA_ATTEMPTS is referenced by several downstream tables and references key parents:

• OTA_EVENTS — via OTA_ATTEMPTS.EVENT_ID.
• OTA_LEARNING_OBJECTS — via LEARNING_OBJECT_ID.
• OTA_CERT_PRD_ENROLLMENTS — via CERT_PRD_ENROLLMENT_ID.
• OTA_SCORM_OBJ_ATTEMPTS — references OTA_ATTEMPTS.ATTEMPT_ID.
• OTA_UTEST_QUESTIONS — references ATTEMPT_ID for test question responses.
• OTA_PERFORMANCES — references ATTEMPT_ID for performance records.
• IRC_ASSIGNMENT_DETAILS_F and IRC_NOTIFICATION_PREFERENCES — reference ATTEMPT_ID for iRecruitment integration.