Results for “success_status”

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

Overview

OTA_SCORM_OBJ_PERFS is a transactional table in the Oracle E-Business Suite Learning Management module (OTA). It stores a learner's current lesson status and score for a particular objective, making it the primary record of objective-level performance tracking within a SCORM-based e-learning environment. In EBS 12.1.1 and 12.2.2, the table resides in the OTA schema and is classified as VALID. SCORM (Sharable Content Object Reference Model) content communicates learner progress to the LMS through runtime calls, and each objective defined within that content generates a corresponding performance row in this table. This provides a granular view of learner achievement beyond simple lesson completion, capturing mastery of specific learning objectives.

From a Data Vault modeling perspective, the mined foreign key structure suggests this table is satellite-leaning. Its single documented FK link to OTA_SCORM_OBJECTIVES, combined with descriptive measures such as score, status, and progress, implies it functions primarily as a descriptive satellite attached to an objective/attempt hub or link rather than acting as a hub or link in its own right. This classification is a heuristic suggestion, not an enforced schema design.

Key Information Stored

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

• OBJECTIVE_PERFORMANCE_ID — the surrogate primary key, enforced by OTA_SCORM_OBJ_PERFS_PK. It uniquely identifies each objective performance record.
• OBJECTIVE_ID — foreign key to OTA_SCORM_OBJECTIVES, linking the performance record to its parent objective definition.
• USER_ID — the learner to whom the performance record belongs.
• OBJECTIVE_SCORE — the raw score the learner achieved on the objective.
• OBJECTIVE_STATUS — the current status of the objective attempt.
• SCALED_SCORE, MIN_SCORE, MAX_SCORE — the scaled score and the score range boundaries used to normalize performance.
• SUCCESS_STATUS and COMPLETION_STATUS — flags indicating whether the objective was passed and completed, respectively.
• PROGRESS_MEASURE — the measured progress toward objective completion.
• SCORM_LEARNER_ATTEMPT_ID and EVENT_ID — references to the learner attempt and the triggering event context.
• BUSINESS_GROUP_ID, USER_TYPE, DESCRIPTION — organizational and descriptive attributes.
• OBJECT_VERSION_NUMBER and the standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — supporting concurrency control and change tracking.

OBJECTIVE_PERFORMANCE_ID is the only unique index documented; no separate business-key unique index is defined in the metadata, though OBJECTIVE_ID plus USER_ID plus SCORM_LEARNER_ATTEMPT_ID is a natural composite candidate for identifying a performance record.

Common Use Cases and Queries

Typical reporting scenarios include determining which learners passed a given objective, aggregating average scores across a SCORM course, and auditing completion status for compliance training. A common query joins performance records to learner and objective context:

• Selecting a learner's objective results: SELECT p.OBJECTIVE_ID, p.OBJECTIVE_SCORE, p.SUCCESS_STATUS, p.COMPLETION_STATUS FROM OTA.OTA_SCORM_OBJ_PERFS p WHERE p.USER_ID = :user_id;
• Computing average scores per objective: SELECT OBJECTIVE_ID, AVG(OBJECTIVE_SCORE), AVG(PROGRESS_MEASURE) FROM OTA.OTA_SCORM_OBJ_PERFS GROUP BY OBJECTIVE_ID;
• Tracking completions by business group: joining on BUSINESS_GROUP_ID and filtering by CREATION_DATE for period reporting.

Related Objects

• OTA_SCORM_OBJECTIVES — the documented foreign key target; join on OTA_SCORM_OBJ_PERFS.OBJECTIVE_ID = OTA_SCORM_OBJECTIVES.OBJECTIVE_ID. This is the principal parent relationship.
• OTA_SCORM_LEARNER_ATTEMPTS — referenced via SCORM_LEARNER_ATTEMPT_ID, providing attempt-level context for the performance row.
• PER_ALL_PEOPLE_F — joins on USER_ID to resolve learner names and person details for reporting.
• OTA_LEARNER_ENROLLMENTS — relates learners to enrollments, enabling correlation of objective performance with course enrollment.
• OTA_EVENTS and OTA_DELEGATES — provide event and audience context through EVENT_ID and USER_ID.
• HR_ALL_ORGANIZATION_UNITS — resolves BUSINESS_GROUP_ID for organizational reporting.

These relationships make OTA_SCORM_OBJ_PERFS a central fact source for objective-level SCORM reporting across the Learning Management module.