Results for “chk_valid_activity”
16 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OTA_EL_ENROLL_SS is a PL/SQL package body owned by APPS within the Oracle E-Business Suite Oracle Learning Management (OTM/OTA) module. Its package header comment identifies it as the self-service enrollment engine used to create enrollment data when a learner enrolls in a scheduled class or event through the employee self-service application. Both 12.1.1 and 12.2.2 use the same underlying self-service architecture, so the package behaves consistently across those releases. It is classified as an "OTHER" API, indicating it is intended primarily for internal use by the OTM self-service flows, Oracle Workflow, and related concurrent processes rather than as a public, formally supported integration API. It is referenced by one other package, and it exposes 21 documented procedures and functions.
Users searching for "get_person_to_enroll_details" are typically working with a financials-to-OTM integration flow: this function resolves who should be enrolled when a charge is processed (for example, a learner versus a cost center or delegate), which is why it is exposed as a documented API in this self-service package.
Key Procedures and Functions
- PROCESSSAVEENROLLMENT — the primary entry point. Processes and persists enrollment records when a learner enrolls in a class, returning a booking id and message name to the caller.
- GET_PERSON_TO_ENROLL_DETAILS — returns the person details that should be used in the enrollment, resolving the correct learner or enrollment party (the object of the user's search).
- CANCEL_FINANCE — reverses the financial and cost charging associated with a booking when an enrollment is cancelled.
- GET_BOOKING_STATUS_FOR_WEB — supplies the current booking status for display in self-service pages.
- CHECK_COST_CENTER / CROSS_CHARGES_NOTIFICATIONS — validate cost center data and raise cross-charge notifications, supporting internal cross-charging of training costs.
- CREATE_ENROLL_WF_PROCESS — instantiates the Oracle Workflow enrollment process used to orchestrate the enrollment business flow.
- VALIDATE_ENROLLMENT / CHECK_ENROLLMENT_CREATION — validate that an enrollment may be created and that all prerequisites are met.
- CHK_EVENT_CANCELLED_FOR_PERSON, CHK_BOOKING_CLASH, CHK_DELEGATE_OK_FOR_EVENT, CHK_FOR_SECURE_EVT, CHK_FOR_RESTRICTED_EVT, CHK_VALID_EVENT, CHK_VALID_ACTIVITY, CHK_UNIQUE_FUNC — a family of validation and eligibility checks covering cancellations, scheduling clashes, delegate permission, security and restricted events, and event/activity validity.
- GET_CURRENT_PERSON_ID — returns the person id of the currently logged-in user for self-service authorization.
- CHECK_WF_STATUS — checks the status of the associated Oracle Workflow process.
- APPROVED — used as the approval step within the enrollment workflow.
Tables Accessed
- OTA_EVENTS, OTA_ACTIVITY_VERSIONS, OTA_ACTIVITY_DEFINITIONS — event, activity definition, and activity version data used during enrollment validation.
- OTA_DELEGATE_BOOKINGS — delegate and booking records written during enrollment (the booking id is returned by ProcessSaveEnrollment).
- OTA_BOOKING_STATUS_TYPES, OTA_BOOKING_STATUS_TYPES_TL — booking status codes and their translated descriptions.
- PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, HR_ALL_ORGANIZATION_UNITS, HR_WORKFLOW_ITEM_KEY_S — person, assignment, organization unit, and workflow item key data for the learner and cost center.
- WF_ITEMS, WF_PROCESS_ACTIVITIES — Oracle Workflow item and process activity records driving the enrollment workflow.
- FND_FORM_FUNCTIONS, FND_RESPONSIBILITY, FND_USER — application function security and user data used by the CHK_FOR_SECURE_EVT and CHK_UNIQUE_FUNC checks.
Usage Notes
OTA_EL_ENROLL_SS is invoked from the OTM self-service enrollment pages (the Learner/Manager self-service flows), from Oracle Workflow enrollment processes, and by custom code that needs programmatic enrollment creation and validation. When extending or debugging enrollment behavior, GET_PERSON_TO_ENROLL_DETAILS is the appropriate call to determine the enrollment party, and PROCESSSAVEENROLLMENT is the correct entry point for creating the booking. Because the package is classified OTHER and marked "Internal Development Use Only" in its header, any direct invocation should be performed in a controlled, tested manner, and custom code should expect the interface to change without the compatibility guarantees of a public API.