Search Results is_personal_trng_plan




Overview
Explore in AI Chat

Overview

APPS.OTA_TRNG_PLAN_UTIL_SS is a server-side PL/SQL utility package within the Oracle E-Business Suite OTA (Oracle Training Administration) module, part of the Oracle Learning Management (OLM) product family. The package encapsulates shared validation and utility logic used across Training Plan processing, providing callers with a consistent mechanism to determine the nature of a training plan (personal versus organizational), validate whether a plan may be cancelled or completed, and resolve enrollment-related status and eligibility questions. It is declared AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking schema rather than the definer; in EBS this generally implies the APPS schema context is expected, and the package operates under standard EBS security and MOAC/operating unit semantics applied by its callers.

The package is classified as OTHER in the ETRM metadata, indicating it is not a fully public, documented Open Interface or public API, and its procedures are marked "Internal Development Use Only" in the source comments. It is nonetheless referenced by eight other packages, making it an established internal dependency. The global variable g_is_per_trng_plan carries plan-type context across calls within a session.

Key Procedures and Functions

The 15 documented procedures and functions serve the following purposes:

  • IS_PERSONAL_TRNG_PLAN — overloaded function returning TRUE when the training plan is a Personal Training Plan and FALSE when it is an Organization Training Plan; one overload derives the answer from session context, the other accepts a training plan identifier.
  • CHK_COMPLETE_PLAN_OK — the routine associated with the search term; it validates whether the plan satisfies the conditions required for completion, allowing callers to gate the completion action.
  • CHK_CANCEL_PLAN_OK — the parallel validation for cancellation, determining whether a training plan may be cancelled.
  • COMPLETE_PLAN — performs the completion action on a training plan once the corresponding checks have passed.
  • GET_ENROLL_STATUS — returns the enrollment status for a learner/plan context.
  • CHK_LOGIN_PERSON — validates the currently logged-in person, typically against the person associated with the plan.
  • CHK_SRC_FUNC_TLNTMGT — checks whether the originating function is Talent Management, controlling behavior differences for plans created from that source.
  • CHK_VALID_ACT_VERSION_DATES — validates the effective dates of activity versions associated with the plan.
  • CHK_ENROLLMENT_EXIST — determines whether an enrollment already exists, used to prevent duplicates.
  • MODIFY_TPC_STATUS_ON_CREATE and MODIFY_TPC_STATUS_ON_UPDATE — maintain training plan component status when components are created or updated.
  • GET_PERSON_ID — resolves a person identifier from the calling context.
  • GET_VALID_ENROLL — returns a valid enrollment record or reference for the given context.

Tables Accessed

The package reads and writes the core OTA training objects: OTA_TRAINING_PLANS (plan header and type), OTA_TRAINING_PLAN_MEMBERS (plan membership), OTA_ACTIVITY_VERSIONS (version date validation), OTA_EVENTS (scheduled offerings), and OTA_BOOKING_STATUS_TYPES and OTA_DELEGATE_BOOKINGS for enrollment and delegation status. FND_USER is referenced to identify the logged-in application user. All access is through APPS synonyms.

Usage Notes

OTA_TRNG_PLAN_UTIL_SS is invoked primarily from OTA forms and concurrent processes that manage training plans, and from dependent PL/SQL packages (eight documented referrers) that delegate plan-type checks and completion/cancellation validation to it. Custom code should treat it as internal: callers requiring its behavior should reference it only where the corresponding standard OLM functionality is already in use, because its interfaces are neither frozen nor supported for external integration. Recompilation of dependent packages is advisable after OLM patches, given the AUTHID CURRENT_USER declaration and the shared global variable.