Search Results ota_scorm_obj_attempts




Overview

The OTA_SCORM_OBJ_ATTEMPTS table is a core transactional data store within the Oracle E-Business Suite Learning Management (OTA) module, specifically for SCORM (Sharable Content Object Reference Model) content tracking. Its primary role is to serve as a staging area for granular, real-time performance data captured during a learner's interaction with a SCORM-based learning object. The table holds raw, attempt-specific status and score changes communicated by the SCORM content package. Once an attempt is finalized, this granular data is aggregated and processed to update the learner's overall, persistent performance record for the associated learning objective, ensuring accurate tracking of competency and completion.

Key Information Stored

The table's structure is designed to capture the detailed interaction log between the SCORM runtime environment and the EBS database. The primary key, OBJECTIVE_ATTEMPT_ID, uniquely identifies each recorded interaction event. Two critical foreign keys define the table's relationships: ATTEMPT_ID links to the OTA_ATTEMPTS table, anchoring the data to a specific learner's session on an activity, and OBJECTIVE_ID links to the OTA_SCORM_OBJECTIVES table, identifying the specific learning objective within the SCORM content being measured. While the provided metadata does not list all columns, the description indicates the table centrally stores the raw lesson status (e.g., "incomplete", "passed", "failed"), raw score values, and any changes to objective identifiers sent from the content during the attempt.

Common Use Cases and Queries

This table is essential for troubleshooting learner progress issues, auditing SCORM communication, and building detailed training transcripts. Support personnel may query it to verify the raw data received from a learner's session when the overall course status appears incorrect. A common reporting use case involves analyzing the sequence of score changes during an attempt to understand learner performance patterns. A sample query to retrieve attempt details for a specific learner might be:

  • SELECT osa.ATTEMPT_ID, osa.OBJECTIVE_ID, osa.SCORE, osa.LESSON_STATUS FROM OTA_SCORM_OBJ_ATTEMPTS osa, OTA_ATTEMPTS oa WHERE osa.ATTEMPT_ID = oa.ATTEMPT_ID AND oa.PERSON_ID = <learner_id>;

Data from this table is typically processed by the underlying LMS engine and reflected in higher-level summary views and standard LMS reports.

Related Objects

OTA_SCORM_OBJ_ATTEMPTS is a child table with defined dependencies within the LMS schema. Its existence is predicated on two key parent tables, as defined by its foreign key constraints:

  • OTA_ATTEMPTS: Provides the contextual framework for the attempt, including the learner (PERSON_ID), the activity (ACTIVITY_VERSION_ID), and the overall attempt timestamps and status.
  • OTA_SCORM_OBJECTIVES: Defines the master list of objectives associated with SCORM activities, to which the attempt-specific performance data is linked.

Data from this table is ultimately consolidated and reflected in the learner's overall competency records, which may be accessed via standard LMS user interfaces or summary reporting views.

  • Table: OTA_SCORM_OBJ_ATTEMPTS 12.1.1

    owner:OTA,  object_type:TABLE,  fnd_design_data:OTA.OTA_SCORM_OBJ_ATTEMPTS,  object_name:OTA_SCORM_OBJ_ATTEMPTS,  status:VALID,  product: OTA - Learning Managementdescription: Holds the raw lesson status, score, and identifier changes (SCORM only) set by the content during a particular attempt. When the attempt is finished, this data is used to update the learner's overall performance on the objective, which is ,  implementation_dba_data: OTA.OTA_SCORM_OBJ_ATTEMPTS

  • Table: OTA_SCORM_OBJ_ATTEMPTS 12.2.2

    owner:OTA,  object_type:TABLE,  fnd_design_data:OTA.OTA_SCORM_OBJ_ATTEMPTS,  object_name:OTA_SCORM_OBJ_ATTEMPTS,  status:VALID,  product: OTA - Learning Managementdescription: Holds the raw lesson status, score, and identifier changes (SCORM only) set by the content during a particular attempt. When the attempt is finished, this data is used to update the learner's overall performance on the objective, which is ,  implementation_dba_data: OTA.OTA_SCORM_OBJ_ATTEMPTS

  • Table: OTA_SCORM_OBJECTIVES 12.1.1

    owner:OTA,  object_type:TABLE,  fnd_design_data:OTA.OTA_SCORM_OBJECTIVES,  object_name:OTA_SCORM_OBJECTIVES,  status:VALID,  product: OTA - Learning Managementdescription: Holds one record for each objective. Objectives are used in both AICCand SCORM. ,  implementation_dba_data: OTA.OTA_SCORM_OBJECTIVES

  • Table: OTA_ATTEMPTS 12.1.1

    owner:OTA,  object_type:TABLE,  fnd_design_data:OTA.OTA_ATTEMPTS,  object_name:OTA_ATTEMPTS,  status:VALID,  product: OTA - Learning Managementdescription: Every time a learner plays online learning, a row in this table is created for a specific leaner against a learning object. ,  implementation_dba_data: OTA.OTA_ATTEMPTS

  • Table: OTA_ATTEMPTS 12.2.2

    owner:OTA,  object_type:TABLE,  fnd_design_data:OTA.OTA_ATTEMPTS,  object_name:OTA_ATTEMPTS,  status:VALID,  product: OTA - Learning Managementdescription: Every time a learner plays online learning, a row in this table is created for a specific leaner against a learning object. ,  implementation_dba_data: OTA.OTA_ATTEMPTS

  • Table: OTA_SCORM_OBJECTIVES 12.2.2

    owner:OTA,  object_type:TABLE,  fnd_design_data:OTA.OTA_SCORM_OBJECTIVES,  object_name:OTA_SCORM_OBJECTIVES,  status:VALID,  product: OTA - Learning Managementdescription: Holds one record for each objective. Objectives are used in both AICCand SCORM. ,  implementation_dba_data: OTA.OTA_SCORM_OBJECTIVES