Search Results get_item_type

Overview

OT_WORKFLOW_SS is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that encapsulates workflow-related business logic for the Oracle Learning Management (OT) module. The package body header, identified as version 120.0.12010000.2 (last modified 2009/07/07), states that it contains "new (v4.0+) workflow related business logic," indicating it was introduced or significantly revised to support the workflow-enabled architecture of Oracle Training Administration and related self-service learning functionality. In EBS 12.1.1 and 12.2.2, the suffix "_SS" conventionally denotes a self-service package, meaning the logic is designed for invocation from self-service web pages, Oracle Forms with self-service routines, or workflow background processes rather than from batch-only interfaces. The package provides helper functions used to resolve descriptive attributes—item types, activity classifications, pricing, and enrollment status—that are required to drive Oracle Workflow item attributes and notifications. Because the package is classified as "OTHER" in the ETRM metadata and is referenced by no other documented packages, it functions as a leaf-level utility supporting workflow and self-service display logic rather than as a shared business API.

Key Procedures and Functions

• GET_EVENT_STANDARD_PRICE — Returns the standard price associated with an event or offering, used when workflow notifications or self-service pages must display the default commercial price for a training event before discounts or enrollment-specific pricing are applied.
• GET_ACTIVITY_TYPE — Resolves the type of a training activity (for example, course, offering, or other activity classification) so that downstream workflow logic and user interfaces can branch on activity category.
• GET_ACT_PM_CATEGORY — Retrieves the category associated with an activity's program or promotional grouping, supporting categorization and filtering of learning activities in workflow and self-service contexts.
• GET_ACT_PM_DELIVERY_METHOD — Returns the delivery method (such as instructor-led, self-paced, or online) for an activity, allowing workflow routing and display logic to reflect how training is delivered.
• GET_ENROLLMENT_STATUS — Returns the enrollment status value for a learner's booking, used by workflow notifications and self-service pages to communicate approval, waitlist, cancellation, or completion states.

The package body additionally contains private helper functions, including GET_ITEM_TYPE and GET_ITEM_KEY. GET_ITEM_TYPE queries HR_API_TRANSACTION_STEPS by transaction ID to return the workflow item type, defaulting to '-1' when no value is found, while GET_ITEM_KEY performs the equivalent lookup for the workflow item key. Both raise WF_CORE.CONTEXT on error to enrich the workflow error stack. These private functions are typical of packages that build workflow item type and item key attributes from HR API transaction records.

Tables Accessed

The package reads from HR_API_TRANSACTIONS and HR_API_TRANSACTION_STEPS, which store HR API transaction headers and their associated workflow steps; these are the source for the item type and item key resolution described above. Learning-specific data is drawn from OTA_ACTIVITY_DEFINITIONS and its translation table OTA_ACTIVITY_DEFINITIONS_TL, together with OTA_ACTIVITY_VERSIONS, to determine activity type, category, and delivery characteristics. OTA_ACT_CAT_INCLUSIONS and OTA_CATEGORY_USAGES support category and catalog inclusion logic. OTA_BOOKING_STATUS_TYPES and OTA_BOOKING_STATUS_TYPES_TL supply enrollment and booking status descriptions, while OTA_DELEGATE_BOOKINGS holds delegate-level booking records. OTA_EVENTS provides event-level data used for price resolution. All of these are accessed through APPS synonyms, confirming the package operates entirely within the APPS schema namespace.

Usage Notes

OT_WORKFLOW_SS is invoked in workflow-enabled learning scenarios where notifications, approval routings, or self-service pages require derived attributes rather than raw table values. Typical callers include Oracle Workflow function activities associated with training enrollment and cancellation processes, custom workflow definitions, and Oracle Forms or OAF-based self-service pages that display activity type, delivery method, category, price, or enrollment status. Because the documented procedures are simple lookup functions, they must be called after the underlying OTA and HR API transaction rows have been committed. The package is not referenced by other documented packages, so customizations should treat it as a utility layer and call the public functions directly rather than relying on internal GET_ITEM_TYPE or GET_ITEM_KEY helpers, which are private to the package body. When extending workflow logic in EBS 12.1.1 or 12.2.2, developers should note the WF_CORE.CONTEXT error handling convention, which propagates workflow context for diagnostic purposes and should be preserved in any cloned or wrapped logic.