Results for “min_normalized_measure”

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

Overview

OTA_SCORM_OBJECTIVES is a core table in the Oracle E-Business Suite Learning Management module (OTA product schema). It holds one record per learning objective, and objectives are consumed by both the AICC and SCORM e-learning content integration standards. In practice, the table represents the reusable catalog of instructional objectives that scripts, SCOs (Shareable Content Objects), and attempt records reference when tracking learner progress and completion against defined performance criteria.

From a Data Vault modeling perspective, the metadata classifies this table as hub-leaning. That classification is a suggestion rather than a documented design decision: the table carries a single-column surrogate primary key (OBJECTIVE_ID) with long-lived, non-volatile identity semantics, and it is referenced by multiple dependent tables. A modeler would typically treat OBJECTIVE_ID as a hub key, with descriptive attributes such as NAME, IDENTIFIER, and DESCRIPTION split off into a satellite.

Key Information Stored

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

• OBJECTIVE_ID — surrogate primary key, enforced by the unique index OTA_SCORM_OBJECTIVES_PK. This is the only documented business-key candidate and the join column used by all child tables.
• IDENTIFIER — the SCORM/AICC objective identifier, the value content packages use to match an objective at runtime.
• NAME and DESCRIPTION — human-readable label and narrative for the objective.
• FOLDER_ID — foreign key to OTA_LO_FOLDERS, placing the objective within the Learning Management folder hierarchy used for catalog organization and security.
• BUSINESS_GROUP_ID — multi-tenant partitioning column, essential for any HRMS-secured query.
• SCORM_SEQUENCING_ID — sequencing rule reference governing navigation behavior in SCORM content.
• OBJECTIVE_MAP_OBJ_IDENTIFIER — the source objective identifier used when mapping content objectives to catalog objectives.
• SATISFIED_BY_MEASURE, MIN_NORMALIZED_MEASURE, and SCORM_OBJECTIVE_TYPE — the satisfaction model: which measure satisfies the objective, the minimum normalized score required, and the objective classification.
• ATTEMPT_ID — links the objective definition to the attempt context it was evaluated under.
• Standard WHO/audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, USER_ID, USER_TYPE, and OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

The dominant use case is reporting on objective definitions and joining them to attempt and performance records to assess learner attainment. A typical catalog lookup joins to the folder hierarchy:

• SELECT o.OBJECTIVE_ID, o.IDENTIFIER, o.NAME, f.FOLDER_NAME FROM OTA_SCORM_OBJECTIVES o, OTA_LO_FOLDERS f WHERE o.FOLDER_ID = f.FOLDER_ID AND o.BUSINESS_GROUP_ID = :bg_id — inventories objectives by folder for a given business group.
• Joining to OTA_SCORM_OBJ_ATTEMPTS on OBJECTIVE_ID produces learner-by-objective attempt history, while joining to OTA_SCORM_OBJ_PERFS yields raw performance measures suitable for scoring dashboards.
• Joining upstream through OTA_LO_SCORM_OBJECTIVES links objectives to the learning objects that expose them, supporting content-to-objective traceability audits.
• Satisfaction analysis filters on SATISFIED_BY_MEASURE and MIN_NORMALIZED_MEASURE to identify objectives that require a minimum score before completion is recorded.

Because the table is multi-org aware, every query should constrain BUSINESS_GROUP_ID and respect the security profile applied to the folder structure.

Related Objects

• OTA_LO_FOLDERS — parent folder table; OTA_SCORM_OBJECTIVES.FOLDER_ID references OTA_LO_FOLDERS.FOLDER_ID.
• OTA_LO_SCORM_OBJECTIVES — child link between learning objects and objectives, joined on OBJECTIVE_ID.
• OTA_SCORM_OBJ_ATTEMPTS — child table of attempt-level objective results, joined on OBJECTIVE_ID.
• OTA_SCORM_OBJ_PERFS — child table holding objective performance measures, joined on OBJECTIVE_ID.
• OTA_SCORM_OBJECTIVES_PK — the unique index enforcing OBJECTIVE_ID uniqueness and serving as the reference target for all inbound foreign keys.