Search Results upgrade_act_cat_inclusions




Overview

APPS.OTA_CLASSIC_UPGRADE is a PL/SQL upgrade package belonging to the Oracle Training Administration (OTA) product family within Oracle E-Business Suite. Its principal business function is to migrate legacy, "classic" Oracle Learning Management data structures into the current OTA data model that was introduced with the Online Learning / iLearning architecture. The package handles the one-time conversion of categories, activities, offerings, delivery modes, events, and associated descriptive flexfield contexts so that historical training records remain accessible and consistent after an upgrade to Release 12.1.1 or 12.2.2.

The object is registered in the ETRM as owner APPS, status VALID, and API classification OTHER, indicating that it is an internal upgrade utility rather than a public, supported application programming interface. It is not intended for routine transactional use; it is invoked during the upgrade or patching cycle to reconcile pre-existing data with the revised schema.

Key Procedures and Functions

The documented interface exposes 22 procedures and functions. The most significant include the following.

Tables Accessed

The package reads and writes OTA transactional tables including OTA_ACTIVITY_DEFINITIONS, OTA_ACTIVITY_DEFINITIONS_TL, OTA_ACTIVITY_VERSIONS, and HR_ALL_ORGANIZATION_UNITS_TL, which hold the training catalog, translated names, activity versions, and owning organizations. Foundation data is drawn from FND_LOOKUP_VALUES, FND_FLEX_VALUE_SETS, FND_DESCRIPTIVE_FLEXS, FND_DESCR_FLEX_CONTEXTS, and FND_DESCR_FLEX_COLUMN_USAGES to drive flexfield and lookup migration. FND_LANGUAGES, FND_LANGUAGES_TL, and FND_NATURAL_LANGUAGES support multilanguage handling; FND_PRODUCT_INSTALLATIONS, FND_RESPONSIBILITY, and FND_USER supply installation and security context.

Usage Notes

OTA_CLASSIC_UPGRADE is referenced by three other packages — OTA_REPROCESS_CLASSIC_UPGRADE, OTA_TIMEZONE_UPGRADE, and OTA_TRAINING_PLAN_UPGRADE — which orchestrate reruns and complementary migration tasks. In practice the package is invoked by the Oracle Learning Management upgrade driver during the standard upgrade or patch application, not from a form. Custom code should avoid direct calls because the interface is undocumented and unsupported; the supported path is to execute the delivered concurrent upgrade programs, which in turn call these procedures.