Search Results user_can_attempt_lo




Overview

APPS.OTA_LO_UTILITY is a core Oracle E-Business Suite package body belonging to the Oracle Training Administration (OTA) / Enterprise Training and Resource Management (ETRM) module. Its principal business function is to encapsulate the utility logic that governs learner interaction with Learning Objects (LOs), Events, and Certifications within the learning management environment. The package centralizes reusable decision routines used across the ETRM UI and processing flows, including determination of learner attempt eligibility, navigation between learning objects in a curriculum sequence, calculation of play-button availability, and computation of default lesson status based on the state of child learning objects. The header comment (otloutil.pkb 120.68.12010000.8) indicates this is a long-maintained utility library shipped with the EBS 12.1.1 release line and carried forward into 12.2.2. The API classification is OTHER, reflecting its role as an internal helper package rather than a public business API. It is referenced by two other packages, positioning it as a shared dependency within the ETRM learning engine.

Key Procedures and Functions

The package exposes 54 documented procedures and functions. The most significant groups include:

Tables Accessed

The package references the following tables via APPS synonyms: OTA_LEARNING_OBJECTS and OTA_PERFORMANCES (core to LO status and hierarchy logic), OTA_ATTEMPTS (attempt records, including user_type), FND_USER, FND_LANGUAGES, OTA_EVENTS, OTA_TESTS, OTA_EVALUATIONS, OTA_CERT_ENROLLMENTS, OTA_CERT_MBR_ENROLLMENTS, OTA_CERT_PRD_ENROLLMENTS, OTA_LP_MEMBER_ENROLLMENTS, OTA_DELEGATE_BOOKINGS, OTA_BOOKING_STATUS_TYPES, and OTA_CATEGORY_USAGES. These support the enrollment, certification, booking, and performance domains that the utility functions interrogate.

Usage Notes

OTA_LO_UTILITY is invoked internally by other ETRM packages (two documented dependents) and by ETRM learner-facing forms and pages when rendering learning paths, evaluating whether a learner may launch content, or writing back performance status. Because it is not a public integration API, customizations should avoid calling it directly where a documented public API exists; instead, treat functions such as USER_CAN_ATTEMPT_LO as reference implementations for understanding ETRM attempt logic. The package operates within the APPS schema and inherits standard EBS security and language considerations through its FND_USER and FND_LANGUAGES references.