Results for “user_type”

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

Overview

OTA_LO_SCORM_OBJECTIVES is an Oracle E-Business Suite table owned by the OTA (Learning Management) schema. It functions as an intersection table that captures the relationship between SCORM objectives and learning objects. In Oracle EBS 12.1.1 and 12.2.2, this table is a core structural component of the Learning Management module's support for SCORM-compliant e-learning content, where a single learning object may be associated with one or more SCORM objectives, and an objective may in turn be reused across multiple learning objects.

From a data modeling perspective, the metadata supports a heuristic Data Vault classification of link. This classification should be treated as a modeling suggestion rather than a physical design mandate: the table resolves a many-to-many relationship between two parent entities (OTA_LEARNING_OBJECTS and OTA_SCORM_OBJECTIVES) and carries only descriptive and audit attributes alongside its composite key, which is characteristic of a link construct. The table is marked VALID and is documented with 13 columns in the ETRM 12.2.2 schema reference.

Key Information Stored

The table's uniqueness is defined by the composite primary key OTA_LO_SCORM_OBJECTIVES_PK, which spans LEARNING_OBJECT_ID and OBJECTIVE_ID. Two foreign keys reinforce the intersection semantics: LEARNING_OBJECT_ID references OTA_LEARNING_OBJECTS, and OBJECTIVE_ID references OTA_SCORM_OBJECTIVES. Neither column is a surrogate identifier; both are business-key components of the parent entities and jointly constitute the business-key candidate for this table.

• LEARNING_OBJECT_ID — identifies the parent learning object; part of the composite primary key and FK to OTA_LEARNING_OBJECTS.
• OBJECTIVE_ID — identifies the associated SCORM objective; part of the composite primary key and FK to OTA_SCORM_OBJECTIVES.
• OBJECTIVE_ORDER — sequencing value that determines the order in which objectives are presented within the learning object.
• IS_PRIMARY — flag indicating whether the associated objective is the primary objective for the learning object.
• BUSINESS_GROUP_ID — multi-tenant / operating unit style partition key used throughout OTA tables for data security and business group isolation.
• USER_ID and USER_TYPE — identify the application user context associated with the row, commonly used in EBS "Who" columns for FND_USER-based auditing.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit ("Who") columns recording row creation and last modification details.

Common Use Cases and Queries

Typical usage centers on reporting and integration: enumerating the objectives attached to a learning object, determining which learning objects depend on a given objective, and validating SCORM content structure during imports. A representative join pattern follows:

• List all objectives for a learning object: SELECT o.objective_id, o.objective_order, o.is_primary FROM ota_lo_scorm_objectives o WHERE o.learning_object_id = :lo_id ORDER BY o.objective_order;
• Find learning objects referencing a specific objective: SELECT lo.learning_object_id, lo.name FROM ota_learning_objects lo, ota_lo_scorm_objectives x WHERE lo.learning_object_id = x.learning_object_id AND x.objective_id = :obj_id;
• Identify the single primary objective per learning object using the IS_PRIMARY flag, useful for building learner-facing catalogs.
• Reconcile SCORM manifests against EBS data by comparing OBJECTIVE_ORDER values with the sequencing declared in the source content package.
• Audit recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY for troubleshooting content-authoring workflows.

Related Objects

The following objects are the most significant dependencies, derived from the documented FK relationships and the OTA Learning Management schema:

• OTA_LEARNING_OBJECTS — parent entity; joined on OTA_LO_SCORM_OBJECTIVES.LEARNING_OBJECT_ID = OTA_LEARNING_OBJECTS.LEARNING_OBJECT_ID.
• OTA_SCORM_OBJECTIVES — parent entity; joined on OTA_LO_SCORM_OBJECTIVES.OBJECTIVE_ID = OTA_SCORM_OBJECTIVES.OBJECTIVE_ID.
• OTA_LO_SCORM_OBJECTIVES_PK — the primary key constraint/index enforcing uniqueness of the LEARNING_OBJECT_ID and OBJECTIVE_ID combination.
• OTA_SCORM_OBJECTIVES_PK and OTA_LEARNING_OBJECTS_PK — referenced primary keys supporting the two foreign keys above.
• OTA_CONTENT_ITEMS and other SCORM import staging tables — indirectly involved when content packages are processed and objective relationships are written.
• Learning Management OAF pages and the SCORM import/player routines that read and write this intersection during content deployment and playback.

Because the table is purely associative, no dependent child tables reference it; its lifecycle is governed by the two parent entities, and rows are typically deleted or re-created when a learning object's objective mapping is revised.