Search Results restrictions_apply




Overview
Explore in AI Chat

Overview

APPS.OTV_SCHEDULED_EVENTS is a reporting view within the Oracle E-Business Suite (EBS) Training Administration (OTA) module, delivered under the OTV (Training Views) naming convention. It exposes a pre-joined, business-friendly projection of scheduled training events, combining event scheduling attributes, offering version details, vendor information, currency, language, and lookup-decoded status values. The view is designed to be queried directly by reports, OBIEE/XML Publisher extracts, and integration interfaces without requiring the caller to reconstruct the multi-table joins between OTA_EVENTS, OTA_ACTIVITY_VERSIONS, and associated lookup tables.

A defining characteristic of this view is that it is pre-filtered to return only events meeting specific runtime criteria. The WHERE clause restricts output to events whose enrolment window and course window are open as of TRUNC(SYSDATE), whose EVENT_TYPE is 'SCHEDULED', and whose EVENT_STATUS is one of ('N','P','F'). Because these filters are embedded in the view definition, results are inherently dynamic and depend on the system date at query execution time. The business group of the session (via OTA_GENERAL.GET_BUSINESS_GROUP_ID) and the event's own BUSINESS_GROUP_ID further constrain the result set.

Underlying Base Objects

The documented base objects referenced by APPS.OTV_SCHEDULED_EVENTS span several schemas and object types, reflecting the cross-functional nature of training data:

Key Columns

The columns most relevant to reporting and integration include:

Common Use Cases and Queries

The view is typically used for open-enrolment catalogues, event status dashboards, and downstream integration feeds. A representative query retrieving scheduled events and their decoded status is:

SELECT TITLE, COURSE_START_DATE, SCHEDULED_EVENT_STATUS, OTA_GET_PLACES_AVAILABLE, VENDOR_NAME, STANDARD_PRICE, CURRENCY_NAME FROM APPS.OTV_SCHEDULED_EVENTS WHERE BUSINESS_GROUP_ID = :p_bg_id ORDER BY COURSE_START_DATE;

Because the view already restricts results to currently open scheduled events with status N, P, or F, queries should not re-add those predicates; analysts typically filter further by TRAINING_CENTER_ID, LANGUAGE_ID, or SECURE_EVENT_FLAG. Note that the outer joins on vendor and currency cause NULLs where no vendor or currency is assigned. The reliance on TRUNC(SYSDATE) means the same query returns different rows on different days, which must be accounted for in scheduled extracts and reconciliation.