Results for “overridden_date”

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

Overview

OTA_PERFORMANCES is a core transactional table within the Oracle E-Business Suite Learning Management module (OTA), owned by the OTA schema. It persists the latest known status of a learner against a specific learning object, functioning as the authoritative single-row-per-learner-per-object record in the Learning Management data model. According to the ETRM metadata, there is only ever one row for a given learner and learning object combination, meaning the table is maintained as a current-state snapshot rather than a historical transaction log.

The heuristic Data Vault classification mined from the foreign-key structure describes this object as standalone. In Data Vault modeling terms, this suggests OTA_PERFORMANCES behaves more like a satellite-style current-state store than a true hub or link. Its natural business keys are the learner (USER_ID) and the learning object (LEARNING_OBJECT_ID), while the surrogate PERFORMANCE_ID anchors the physical row. The standalone classification implies the table carries its own descriptive attributes and does not serve as a pure intersection entity, even though it references multiple parent objects.

Key Information Stored

The table contains 26 documented columns. The surrogate primary key is PERFORMANCE_ID, enforced by the OTA_PERFORMANCES_PK unique index. The remaining columns fall into several functional groups:

• Identity and ownership: USER_ID identifies the learner; BUSINESS_GROUP_ID scopes the record to an operating unit or business group; USER_TYPE distinguishes categories of learner.
• Learning relationship: LEARNING_OBJECT_ID ties the row to the catalogued learning object; ATTEMPT_ID and CERT_PRD_ENROLLMENT_ID link to a specific attempt or certification-period enrollment.
• Progress and outcome: LESSON_STATUS, COMPLETION_STATUS, SUCCESS_STATUS, and SCORE capture the learner's current standing; COMPLETED_DATE records the completion timestamp.
• Context and provenance: TIME and LOCATION store duration and delivery location; SOURCE identifies the originating system or channel; OVERRIDDEN_BY and OVERRIDDEN_DATE record manual administrative overrides.
• SCORM interoperability: SCORM_TIMESTAMP and SCORM_LEARNER_ATTEMPT_ID support integration with external SCORM-compliant content players.
• Audit and concurrency: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER provide standard EBS auditing and optimistic locking.

AVAILABLE_CHILDREN supports hierarchical content navigation. No business-key unique index beyond the primary key is documented, reinforcing that uniqueness is enforced indirectly through the learner/learning-object pairing rather than a secondary constraint.

Common Use Cases and Queries

Typical reporting scenarios include learner transcript generation, completion tracking, certification eligibility checks, and SCORM result reconciliation. A representative query joining the learner and learning object looks like:

• SELECT p.user_id, p.learning_object_id, p.lesson_status, p.score, p.completion_status, p.completed_date FROM ota_performances p WHERE p.user_id = :user_id AND p.learning_object_id = :object_id;
• Aggregation for completion rates: SELECT learning_object_id, COUNT(*) total, SUM(CASE WHEN completion_status = 'COMPLETED' THEN 1 ELSE 0 END) completed FROM ota_performances GROUP BY learning_object_id;
• Attempt reconciliation: join ATTEMPT_ID to OTA_ATTEMPTS to correlate the current performance row with historical attempt records.
• Override auditing: filter on OVERRIDDEN_BY IS NOT NULL to identify administratively adjusted outcomes.

Related Objects

The documented foreign keys establish the principal relationships:

• OTA_LEARNING_OBJECTS — joined via OTA_PERFORMANCES.LEARNING_OBJECT_ID.
• OTA_ATTEMPTS — joined via OTA_PERFORMANCES.ATTEMPT_ID.
• OTA_CERT_PRD_ENROLLMENTS — joined via OTA_PERFORMANCES.CERT_PRD_ENROLLMENT_ID.

Additional dependencies include the OTA learner and person reference tables implied by USER_ID, and EBS standard audit columns referencing FND_USER and related foundation objects.