Search Results complete_path

Overview

OTA_LRNG_PATH_UTIL is a PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite, classified under the Oracle Learning Management (OTL) module. It provides the core processing logic for managing learner progress and completion within Learning Paths. A Learning Path in Oracle Learning Management is a structured grouping of courses and sections that a learner must complete in order to achieve a certification or fulfill a curriculum requirement. This package encapsulates the business rules that determine whether a learner has satisfied the mandatory requirements of a path, whether a path has been completed successfully, and how enrollment records should be updated as learners move through their assigned learning.

Because it carries an API classification of UTIL, the package is not intended to be a public-facing business API. Instead, it functions as a shared internal service that other Learning Management APIs and member utilities call upon to evaluate path status and to trigger completion processing. Its presence as a dependency of OTA_LP_ENROLLMENT_API, OTA_DELEGATE_BOOKING_API, and OTA_LRNG_PATH_MEMBER_UTIL confirms its role as a foundational component in the Learning Path enrollment and completion subsystem.

Key Procedures and Functions

The ETRM metadata documents fifteen procedures and functions within this package. These can be grouped by their purpose:

• Path completion and status: COMPLETE_PATH, IS_PATH_SUCCESSFUL, CHK_COMPLETE_PATH_OK, GET_LP_CURRENT_STATUS. These routines evaluate whether a Learning Path may be marked complete and return the current status of a learner's path enrollment.
• Course counting and mandatory requirements: GET_NO_OF_MANDATORY_COURSES, GET_NO_OF_COMPLETED_COURSES, GET_NO_OF_MAND_COMPL_COURSES. These functions calculate how many mandatory courses exist within a path and how many the learner has finished, supporting completion eligibility checks.
• Enrollment and member handling: GET_PERSON_ID, GET_LP_ENROLL_ID, CHK_LOGIN_PERSON, UPDATE_LPE_LPM_CHANGES. These resolve the learner identity and enrollment identifiers and synchronize changes between Learning Path Enrollments (LPE) and Learning Path Members (LPM).
• Talent Management integration: GET_TALENT_MGMT_LP. This function supports the integration of Learning Paths with Oracle Talent Management objectives.
• Messaging and processing: GET_LPE_CRSE_COMPL_STATUS_MSG, START_COMP_PROC_SUCCESS_ATTND. These produce completion status messages and initiate completion processing upon successful attendance.

Tables Accessed

The package reads and writes a set of Learning Management and Workflow tables through APPS synonyms:

• OTA_LEARNING_PATHS and OTA_LP_SECTIONS — define the structure and mandatory content of a path.
• OTA_LP_ENROLLMENTS and OTA_LP_MEMBER_ENROLLMENTS — store the learner's path-level and member-level enrollment records, which the package queries and updates.
• OTA_LEARNING_PATH_MEMBERS — defines the individual members (courses) that make up a path.
• OTA_EVENTS, OTA_ACTIVITY_VERSIONS, OTA_BOOKING_STATUS_TYPES, and OTA_DELEGATE_BOOKINGS — support attendance, booking, and delegate booking evaluation.
• FND_USER — resolves the logged-in person identity.
• WF_ITEMS — interacts with the Oracle Workflow engine, typically for completion notifications or process triggering.

Usage Notes

OTA_LRNG_PATH_UTIL is invoked indirectly rather than directly by end users. It is called by OTA_LP_ENROLLMENT_API when a learner enrolls in or completes a Learning Path, by OTA_DELEGATE_BOOKING_API to process delegate bookings against path requirements, and by OTA_LRNG_PATH_MEMBER_UTIL when member-level changes affect overall path completion. In Oracle EBS 12.1.1 and 12.2.2, these calls are triggered from the Learning Management self-service pages, administrator enrollment forms, and concurrent processes that recalculate learner progress. Custom extensions that need to determine path completion or update enrollment status should call the higher-level enrollment APIs rather than this utility package, since its interface is internal and not guaranteed as an external contract. Developers reviewing this package should account for its dependencies on Workflow and the OTA booking tables, as these affect the timing and side effects of completion processing.