Search Results ot_workflow_ss




Overview
Explore in AI Chat

Overview

OT_WORKFLOW_SS is a server-side PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the OTHER API category. It encapsulates workflow-related business logic introduced for the v4.0+ generation of Oracle Training Administration (OTA), the module that underpins Oracle Learning Management and its associated self-service functions. The suffix "_SS" indicates that the package serves self-service or workflow-driven processing rather than the core maintenance APIs, and its declaration as AUTHID CURRENT_USER means that execution privileges and unqualified object resolution follow the invoking user's schema rather than the definer's.

The package's central design purpose is to abstract the retrieval of activity, event, enrollment, and pricing attributes from the underlying OTA transactional model so that Oracle Workflow processes and notification functions do not need to embed direct SQL against those tables. Callers pass a transaction identifier from HR_API_TRANSACTIONS, and the package resolves the relevant business value — activity type, category, delivery method, standard price, or enrollment status — returning it as a scalar value suitable for use in workflow attributes, message tokens, or conditional branching.

Key Procedures and Functions

  • GET_EVENT_STANDARD_PRICE — Returns the standard price associated with the event tied to a given HR_API_TRANSACTIONS transaction. Used wherever a workflow process must surface or evaluate the monetary value of a learning event.
  • GET_ACTIVITY_TYPE — Returns the activity type for the activity referenced by the transaction, allowing workflow logic to distinguish between the different kinds of learning activities defined in the training catalog.
  • GET_ACT_PM_CATEGORY — Returns the primary category of the activity. This supports categorization-dependent routing, approvals, and reporting decisions inside workflow definitions.
  • GET_ACT_PM_DELIVERY_METHOD — Returns the primary delivery method of the activity, the attribute most commonly used by customers investigating this package. Delivery method determines whether a learning activity is delivered in a classroom, online, or through another modality, and it drives workflow behavior such as notification content and enrollment handling.
  • GET_ENROLLMENT_STATUS — Returns the enrollment status for the transaction context, enabling workflow processes to evaluate whether a learner is enrolled, waitlisted, cancelled, or in another booking state before proceeding to the next activity in the process.

Tables Accessed

The package reads from a focused set of OTA and HR tables, resolved through APPS synonyms. HR_API_TRANSACTIONS and HR_API_TRANSACTION_STEPS provide the transaction context that every function uses as its entry parameter. The activity definition and translation tables, OTA_ACTIVITY_DEFINITIONS, OTA_ACTIVITY_DEFINITIONS_TL, and OTA_ACTIVITY_VERSIONS, supply activity type, category, and delivery method attributes, while OTA_ACT_CAT_INCLUSIONS and OTA_CATEGORY_USAGES resolve category membership and usage rules. OTA_EVENTS is the source for event-level pricing returned by GET_EVENT_STANDARD_PRICE. Enrollment and booking state is derived from OTA_BOOKING_STATUS_TYPES, OTA_BOOKING_STATUS_TYPES_TL, and OTA_DELEGATE_BOOKINGS. The package is documented as read-oriented; no insert, update, or delete operations are described in the metadata.

Usage Notes

OT_WORKFLOW_SS is not an end-user-facing API and is referenced by zero other documented packages, which confirms its position as a leaf-level utility consumed by workflow infrastructure and notification logic rather than a shared library. It is typically invoked from workflow function activities, message attribute derivations, and notification mailer content generation, and may also be called from custom PL/SQL or OAF extensions that need to surface OTA activity or enrollment attributes. In EBS 12.1.1 and 12.2.2 the package remains APPS-owned; customizations should call it qualified as APPS.OT_WORKFLOW_SS and pass a valid transaction identifier, since all documented functions depend on HR_API_TRANSACTIONS context and will return no meaningful value without it.