Search Results get_ext_lrnr_details

Overview

APPS.OTA_LEARNER_ENROLL_SS is a self-service PL/SQL package in the Oracle E-Business Suite OTA (Oracle Training Administration / Oracle Learning Management) schema. As its name and header comment indicate, the package supports the self-service enrollment flow, allowing a learner to create enrollment (booking) data directly from a web or self-service interface when the user enrolls in a class. The header comment within the body states that the package "is used for self service application to create enrollment data when user enroll in the class." A global package name variable g_package is declared for error-message prefixing, a convention used throughout OTA APIs.

The package is classified in the ETRM metadata as OTHER (not a pure public API), and its access status is documented as Internal Development Use Only. It contains 22 documented procedures and functions and is referenced by five other packages within the OTA schema, indicating that it forms part of the internal infrastructure supporting the learner-facing enrollment and cancellation pages.

Key Procedures and Functions

The documented procedures and functions fall into three functional groupings.

• Enrollment creation and validation: PROCESSSAVEENROLLMENT creates the enrollment/booking record when a learner enrolls in a class; VALIDATE_ENROLLMENT performs pre-enrollment validation; CHK_VALID_EVENT, CHK_VALID_OFFERING, CHK_VALID_ACTIVITY and CHK_EVENT_CANCELLED_FOR_PERSON validate the target event, offering, activity and event-cancellation state. CHK_BOOKING_CLASH detects schedule conflicts, CHK_UNIQUE_FUNC enforces a uniqueness rule, and CHECK_COST_CENTER validates cost-centre input.
• External learner and delegate handling: GET_EXT_LRNR_DETAILS (the object of the user's search) retrieves details for an external learner, supporting the delegate/external-learner path added to the package ("Added for External Learner Support"). GET_PERSON_TO_ENROLL_DETAILS returns person data used to drive the enrollment; SUPERVISOR_EXISTS checks for a supervising person; CHK_DELEGATE_OK_FOR_EVENT verifies delegate eligibility; and GET_BOOKING_OVN returns the booking object version number.
• Cancellation, status and security: CANCEL_ENROLLMENT cancels an existing enrollment; CANCEL_FINANCE reverses associated financial entries; GET_BOOKING_STATUS_FOR_WEB returns booking status for the web layer; CHK_FOR_SECURE_EVT and CHK_FOR_RESTRICTED_EVT enforce event security and restriction rules; and GET_WF_ATTR_FOR_CANCEL_NTF supplies workflow attributes used when generating a cancellation notification.

Tables Accessed

The package operates against OTA and shared HR/CRM/Foundation synonyms. Core OTA tables include OTA_DELEGATE_BOOKINGS (the enrollment/booking record, including the OUT booking id returned by PROCESSSAVEENROLLMENT), OTA_EVENTS, OTA_OFFERINGS, OTA_ACTIVITY_VERSIONS, and OTA_BOOKING_STATUS_TYPES with its translated table OTA_BOOKING_STATUS_TYPES_TL for web-displayable booking status. Person and assignment information is drawn from PER_ALL_ASSIGNMENTS_F. Organization and location data come from HR_ALL_ORGANIZATION_UNITS and HR_LOCATIONS_ALL. External-learner and delegate data are sourced from the CRM/HZ tables HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_ORG_CONTACTS, HZ_PARTIES and HZ_RELATIONSHIPS, and the acting user is identified via FND_USER.

Usage Notes

OTA_LEARNER_ENROLL_SS is invoked by the self-service learning pages rather than by end users directly. PROCESSSAVEENROLLMENT is designed to be called with in-parameters describing the event, person, assignment, organization and business group, plus optional external-learner/delegate information and descriptive-flexfield values; on success it returns a booking id (p_booking_id) and on failure it passes a message name (p_message_name) back to the caller, which raises the notification. Because the package is marked Internal Development Use Only and is referenced by several other OTA packages, customizations should call the supported public enrollment APIs instead of this body. Sites on 12.1.1 and 12.2.2 should treat GET_EXT_LRNR_DETAILS and its siblings as internal implementation procedures whose signatures may change between patches.