Search Results ota_category_usage_swi




Overview
Explore in AI Chat

Overview

OTA_CATEGORY_USAGE_SWI is an Oracle Application Object Library (APPS) PL/SQL package belonging to the Oracle Training Administration (OTA) module, the core schema behind Oracle iLearning and Oracle Learning Management in Oracle E-Business Suite. The "_SWI" suffix identifies this object as a Supplemental Web Interface, a thin wrapper layer that sits in front of the corresponding base package, OTA_CATEGORY_USAGE_API. Its purpose is to expose category-usage maintenance operations to web-tier and service-layer callers — such as iLearning self-service pages, Learning Management administrative flows, and integration endpoints — without requiring those callers to invoke the API layer directly.

The package owns data manipulation logic governing how learner categories are associated with, dissociated from, and modified against learning objects such as courses, offerings, and enrollment records. This association data drives catalog visibility rules, enrollment eligibility, and pricing behavior in Oracle Learning Management. The object is declared VALID under the APPS schema in both EBS 12.1.1 and 12.2.2. Its API classification in ETRM is OTHER, indicating it is not a formally published public API but an internally consumed interface.

Key Procedures and Functions

ETRM documents three procedures for this package:

  • CREATE_CATEGORY — Establishes a new category-usage relationship. It is invoked when a category must be newly associated with a learning object, creating the corresponding usage record and any required validation of the target category and object.
  • UPDATE_CATEGORY — Modifies an existing category-usage record. Typically called when the attributes or effective configuration of an existing category-to-object association change.
  • DELETE_CATEGORY — Removes a category-usage relationship. Invoked when a category is no longer applicable to the associated learning object or when the association is being retired.

The correspondence between this three-procedure surface and the base API (CREATE_CATEGORY, UPDATE_CATEGORY, DELETE_CATEGORY) confirms the SWI pattern: the wrapper receives web-tier calls, performs supplemental normalization, and delegates to the API layer, which enforces the business rules and performs the actual inserts, updates, and deletes. Parameter lists are not enumerated in the documented metadata and are therefore not reproduced here.

Tables Accessed

The documented ETRM metadata does not enumerate specific tables referenced through APPS synonyms for this package. Based on its base API counterpart and the OTA data model, the package operates primarily against the OTA_CATEGORY_USAGES table, which stores the category-to-learning-object association rows. Because it delegates to OTA_CATEGORY_USAGE_API, all physical DML against that table occurs in the API layer; the SWI wrapper itself performs no direct SQL against OTA entities. The package additionally depends on HR_API, consistent with OTA's use of Human Resources security and date-tracking conventions, and on the SYS.STANDARD package supplied by the Oracle database. The metadata records no table dependencies of its own, and the dependency listing identifies only APPS.HR_API and SYS.STANDARD.

Usage Notes

OTA_CATEGORY_USAGE_SWI is invoked by Oracle Learning Management and iLearning web-tier components rather than by end users or concurrent programs directly. Typical invocation paths include the administrative forms and OAF pages that maintain category assignments on courses and offerings, and self-service pages that adjust eligibility groupings. Custom integrations that need to programmatically manage category usage should target the base API, OTA_CATEGORY_USAGE_API, and observe the standard JTF/HR API conventions rather than calling the SWI layer, which is an internal web interface and not a supported external entry point.

The ETRM dependency report records that OTA_CATEGORY_USAGE_SWI is referenced by zero other packages and references APPS.HR_API and SYS.STANDARD, confirming it sits at the outer edge of the dependency graph as a caller, not a callee, within the OTA stack. Its VALID status in both 12.1.1 and the 12.2.2 reference environment indicates it has been carried forward through the Online Patching architecture without signature change, so existing callers continue to function across the 12.1 to 12.2 upgrade boundary.