Search Results dev_event_type




Overview
Explore in AI Chat

Overview

APPS.OTA_EVENTS_V is a reporting and integration view within the Oracle E-Business Suite (EBS) OTA (Oracle Training Administration) module. It exposes scheduled training event data — the individual deliveries of a course or activity — in a denormalized, human-readable form, resolving foreign-key identifiers into descriptive meanings wherever possible. The view is defined in the APPS schema and is intended for concurrent programs, Oracle Reports, OBIEE/XML Publisher extracts, and custom integrations that need to consume event records without joining the underlying transactional tables. Because it draws on both base synonyms and PL/SQL packages, it is a read-only construct; no DML is permitted against it. Its presence in both 12.1.1 and 12.2.2 reflects the stability of the OTA data model across these releases, with the 12.2.2 OAF-based UI continuing to rely on the same underlying event schema.

Underlying Base Objects

The view is defined over OTA_EVENTS (SYNONYM), the transactional master table for scheduled events, and OTA_EVENTS_TL, its translation table supplying the multi-language title. It uses OUTER-joined lookups via HR_LOOKUPS (VIEW) indirectly through the HR_GENERAL package. OTA_EVT_SHD (PACKAGE) supplies the RESOURCE_BOOKING_FLAG derived value through the OTA_EVT_SHD.RESOURCE_BOOKING_FLAG function, and OTA_GENERAL provides the hr_org_name helper for the organization name. OTA_UTILITY provides get_lang_name, OTA_OFFERINGS_VL exposes offering-level data, and OTA_ACTIVITY_VERSIONS / OTA_ACTIVITY_DEFINITIONS_TL supply activity context. Additionally, PA_PROJECTS_ALL, PO_VENDORS, and HR_API are referenced as supporting sources. The view is therefore best understood as a presentation layer over OTA_EVENTS_TL, OTA_EVENTS, and lookup decode logic, rather than a simple single-table projection.

Key Columns

Common Use Cases and Queries

Typical uses include event catalogs, enrolment reports, capacity/utilisation analysis, and integrations into learning management portals. The DEVELOPMENT_EVENT_TYPE_MEANING column is frequently filtered or grouped to distinguish development versus non-development events.

  • List all development events and their decoded type: 
    SELECT event_id, title, course_start_date,
       development_event_type, development_event_type_meaning
FROM   apps.ota_events_v
WHERE  development_event_type IS NOT NULL;
  • Active events by organization and centre: 
    SELECT organization_name, centre_meaning, title, event_status
FROM   apps.ota_events_v
WHERE  course_start_date >= SYSDATE
ORDER BY organization_name, course_start_date;
  • Enrolment capacity analysis: 
    SELECT title, minimum_attendees, maximum_attendees,
       maximum_internal_attendees, public_event_flag
FROM   apps.ota_events_v
WHERE  event_status = 'PLANNED';

Because the view invokes PL/SQL functions (RESOURCE_BOOKING_FLAG, hr_org_name, decode_fnd_comm_lookup) per row, performance-sensitive extracts should constrain the driving set, and should prefer materialising results into a custom table when high-volume reporting is required.