Results for “ota_prerequisites_uk1”

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

Overview

OTA_PREREQUISITES is a Learning Management table in the OTA schema that governs sequencing rules between learning objects in Oracle EBS 12.1.1 and 12.2.2. As documented, prerequisites apply exclusively to learning objects (online learning): the table records which learning objects must be completed before another learning object can be attempted, thereby defining the order in which a curriculum or certification path must be traversed. The table is classified as VALID and stores 11 columns under the OTA schema owner.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. That classification indicates the table is not strongly integrated into a parent-child dependency chain within the mined metadata and may be modeled as an independent construct rather than a strict link or satellite. The metadata further notes that Oracle labels the content as proprietary and confidential.

Key Information Stored

The documented physical schema contains 11 columns. The most significant are:

• OBJECT_ID — the learning object that carries the prerequisite; a component of the primary key.
• PARENT_OBJECT_ID — the learning object that must be completed first; the other business component of the unique key.
• PARENT_TYPE — the type discriminator for the parent learning object; completes the business key.
• BUSINESS_GROUP_ID — multi-organization/HR business group partition key.
• ENFORCED_FLAG — indicates whether the prerequisite is strictly enforced or advisory.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OTA framework.
• CREATED_BY, CREATION_DATE — audit columns for row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns for the most recent change.

The primary key is documented as the unique index OTA_PREREQUISITES_UK1 over (OBJECT_ID, PARENT_OBJECT_ID, PARENT_TYPE). Because the documented primary key is the same as the business-key candidate, this table exposes no separate surrogate key beyond the composite business key; the unique index is the principal identity mechanism.

Common Use Cases and Queries

Typical scenarios include validating enrollment eligibility, rendering prerequisite chains on learner self-service pages, and building curriculum reports. A query to list the prerequisites for a given learning object:

• SELECT parent_object_id, parent_type, enforced_flag FROM ota.ota_prerequisites WHERE object_id = :object_id AND business_group_id = :bg_id;

A reverse query to find which learning objects depend on a given parent:

• SELECT object_id, enforced_flag FROM ota.ota_prerequisites WHERE parent_object_id = :parent_id AND parent_type = :parent_type;

A reporting pattern that joins both sides to OTA learning object definitions supports curriculum-graph extraction and cycle detection. Because prerequisites apply only to online learning objects, reports should filter to learning-object rows when joining to the object master.

Related Objects

The metadata describes the FK structure as standalone, so join relationships are inferred from the documented key columns rather than declared constraints. The most significant related objects are:

• OTA_LEARNING_OBJECTS (or equivalent learning object master) — joined on OBJECT_ID and on PARENT_OBJECT_ID to resolve titles and types.
• OTA_LEARNING_OBJECT_TYPES — resolves PARENT_TYPE.
• OTA_LEARNER_ENROLLMENTS — used to check completion status against prerequisites.
• OTA_LEARNING_CERTIFICATIONS — curriculum/certification paths that consume prerequisite sequencing.
• OTA_DELEGATES / OTA_ATTENDEES — learner records validated against prerequisite satisfaction.
• HR_ALL_ORGANIZATION_UNITS / PER_BUSINESS_GROUPS — resolves BUSINESS_GROUP_ID.

No documented FK constraints are exposed in the ETRM excerpt; integrators should confirm actual constraints in the target instance before relying on referential enforcement.