Results for “event_title”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OTFV_EVENTS_WITHOUT_VENUE is an Oracle E-Business Suite database view owned by the APPS schema and validated under the OTA (Learning Management) product. Per the ETRM metadata, it is classified as a "business view template from which the flexfield view is generated," meaning it serves as the foundational definition layer for a descriptive flexfield-enabled reporting view rather than as a standalone transactional entity. The view exposes a filtered subset of learning events: those for which no confirmed venue resource booking exists.

In the context of EBS 12.1.1 and 12.2.2, the view isolates events that have no completed physical-location assignment. The predicate excludes any event whose EVENT_ID appears in a subquery joining OTA_EVENTS, OTA_SUPPLIABLE_RESOURCES, and OTA_RESOURCE_BOOKINGS where RESOURCE_TYPE = 'V' (venue) and booking STATUS = 'C' (confirmed). It further restricts results to events whose EVENT_TYPE is neither 'PROGRAMME' nor 'AD HOC', and enforces multi-tenant isolation through the NVL(OTA_GENERAL.GET_BUSINESS_GROUP_ID, ...) business group filter. The view is declared WITH READ ONLY, so it cannot be used for DML.

Underlying Base Objects

The documented referenced objects are OTA_EVENTS (base event table, accessed via synonym), OTA_EVENTS_TL (the translated attributes table), OTA_GENERAL (the package supplying the business group context), OTA_RESOURCE_BOOKINGS, and OTA_SUPPLIABLE_RESOURCES. The projected view text selects only from the OTA_EVENTS alias EVT; OTA_EVENTS_TL is referenced in the documented object list and is typically joined by flexfield views generated from this template to resolve language-specific TITLE values, while OTA_SUPPLIABLE_RESOURCES and OTA_RESOURCE_BOOKINGS appear exclusively in the NOT IN subquery. OTA_GENERAL is invoked only as a function call within the WHERE clause, not as a joined table.

Key Columns

• EVENT_ID — The primary key of the learning event from OTA_EVENTS. This is the column most frequently used for joining to other OTA tables such as OTA_EVENT_OFFERINGS, OTA_ATTENDEES, or booking records, and is the value returned for users searching on "event_id."
• EVENT_TITLE — The event title sourced from EVT.TITLE. In translated flexfield views generated from this template, this value is resolved against OTA_EVENTS_TL.
• OFFERING_ID — The offering identifier from OTA_EVENTS, linking the event to its parent offering record.

All three columns are exposed with the same names they carry in the base table, with OFFERING_ID substituted for the source label. No additional column aliases or computed expressions are documented.

Common Use Cases and Queries

The principal use case is identifying learning events that still require a venue to be booked or confirmed, supporting scheduling and logistics reporting. A second use case is validating venue coverage before publishing a course catalog, and a third is auditing event types that bypass the standard venue workflow.

A minimal lookup by event identifier follows:

• SELECT event_id, event_title, offering_id FROM apps.otfv_events_without_venue WHERE event_id = :p_event_id;

To list all venue-less events for reporting:

• SELECT event_id, offering_id, event_title FROM apps.otfv_events_without_venue ORDER BY event_id;

Because the view is read-only and applies the business group filter automatically, callers running under a valid OTA session need only supply their own additional predicates. For joins, use EVENT_ID as the correlation key to OTA_EVENTS or to offering-level tables, and reference the view primarily as a filtering mechanism rather than as a source of descriptive attributes.