Search Results ota_evaluations_uk1

Overview

OTA_EVALUATIONS is a Learning Management (OTA) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that controls the assignment of evaluations to learning objects. It functions as a cross-reference between an evaluation definition and the training object it measures, such as a course, offering, or class. Rather than storing evaluation questions or responses, OTA_EVALUATIONS stores the scheduling and routing metadata that determines which evaluation applies, whether completion is mandatory, and the window during which the association is active.

The heuristic Data Vault classification mined from the FK structure is standalone. In Data Vault modeling terms this suggests the table behaves closest to a link or association construct, because it binds an evaluation to a learning object through composite keys rather than acting as a pure descriptive satellite. Modelers should treat the OBJECT_TYPE/OBJECT_ID pair as the anchor of the relationship when integrating this table into an analytical vault.

Key Information Stored

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

• EVALUATION_ID — foreign key to AMW_EVALUATIONS_B; identifies which evaluation instrument is attached.
• OBJECT_TYPE and OBJECT_ID — together the composite unique key (OTA_EVALUATIONS_UK1) identifying the target learning object.
• EVAL_MANDATORY_FLAG — indicates whether the learner must complete the evaluation.
• DFLT_CLASS_EVAL_ID — default class-level evaluation reference used when the assignment propagates to scheduled classes.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective dating that controls when the association is live.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns maintained by EBS.

The surrogate identifier is EVALUATION_ID, while the business-key candidate is the composite unique index OTA_EVALUATIONS_UK1 over (OBJECT_TYPE, OBJECT_ID).

Common Use Cases and Queries

Typical reporting asks which evaluations are attached to a course, whether they are mandatory, and whether the assignment is currently effective. A representative query joins the evaluation definition table:

• SELECT e.evaluation_id, e.object_type, e.object_id, e.eval_mandatory_flag, e.start_date_active, e.end_date_active FROM ota_evaluations e WHERE e.object_type = :object_type AND e.object_id = :object_id;
• Join to AMW_EVALUATIONS_B on OTA_EVALUATIONS.EVALUATION_ID = AMW_EVALUATIONS_B.EVALUATION_ID to resolve evaluation names and types.
• Filter on SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE) to return only active assignments.

Common scenarios include LMS compliance audits that verify mandatory evaluations are configured for regulated courses, migration scripts that re-point evaluation assignments when courses are cloned, and reporting on evaluation coverage across a curriculum catalog.

Related Objects

The most significant related objects, based on documented FK and PK relationships, are:

• AMW_EVALUATIONS_B — master evaluation definition; joined on EVALUATION_ID.
• OTA_EVALUATIONS_UK1 — unique index on (OBJECT_TYPE, OBJECT_ID) enforcing one assignment per learning object.
• Learning object base tables referenced by OBJECT_TYPE/OBJECT_ID, such as courses and offerings in the OTA schema.
• Class and class-evaluation tables that consume DFLT_CLASS_EVAL_ID.
• OTA learner enrollment and completion tables that apply the assigned evaluation during delivery.

Developers extending this area should respect the OAF-managed OBJECT_VERSION_NUMBER semantics and preserve the composite unique constraint during any DML.