Search Results required_from




Overview
Explore in AI Chat

Overview

OTFV_EVENTS_WITH_VENUE is a read-only business view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OTA (Oracle Learning Management) product family. The view functions as a business view template from which a flexfield view is generated, meaning it is primarily intended to expose event scheduling data in a flattened, reporting-ready form that can be extended through descriptive flexfield integration. It presents one row per resource booking of type venue ('V'), combining the parent learning event title with the name of the physical or supplied venue resource that has been reserved, together with booking-placement and status details. Because the view joins transactional booking data to resource master data and applies HR_BIS decode lookups for human-readable flag and status values, it is well suited to operational reporting on where and when a learning event is scheduled, and to integration scenarios where downstream systems require a consolidated event/venue feed without navigating the underlying normalized tables.

Underlying Base Objects

The view is defined over three principal base objects joined in a single SELECT, and it also invokes supporting packages and language-enabled synonyms.

The documented synonym list also references OTA_EVENTS_TL, OTA_SUPPLIABLE_RESOURCES_TL (translation tables underlying multilingual names), and the OTA_SUPPLIABLE_RESOURCES synonym. The view is defined WITH READ ONLY, so no DML is permitted against it.

Key Columns

  • VENUE_NAME — the name of the supplied venue resource (TSR.NAME), the column most commonly searched for. Because it originates from a translatable resource table, it reflects the session language where translations exist.
  • EVENT_TITLE — the title of the learning event (EVT.TITLE).
  • PRIMARY_VENUE — decoded YES/NO indicator from the booking's primary venue flag, identifying the main venue among multiple bookings.
  • BOOKING_STATUS — decoded value from the RESOURCE_BOOKING_STATUS lookup, expressing the state of the venue booking.
  • DATE_BOOKING_PLACED / REQUIRED_FROM / REQUIRED_TO — when the booking was created and the requested booking window. Note that the documented column list shows DATE_OF_BOOKING while the view text aliases it DATE_BOOKING_PLACED; consumers should verify the actual alias in their release.
  • RESOURCE_BOOKING_ID / SUPPLIED_RESOURCE_ID — keys for the booking and the venue resource.
  • EVENT_ID / OFFERING_ID — keys linking back to the event and its offering.

Common Use Cases and Queries

Typical scenarios include venue utilization reporting, conflict checking across events, and exporting an event-to-venue map to scheduling systems. A basic query filters by venue name:

  • SELECT event_title, venue_name, primary_venue, booking_status, required_from, required_to FROM apps.otfv_events_with_venue WHERE venue_name LIKE '%CONFERENCE%';
  • SELECT venue_name, COUNT(*) FROM apps.otfv_events_with_venue GROUP BY venue_name ORDER BY 2 DESC;
  • SELECT event_title, venue_name, required_from, required_to FROM apps.otfv_events_with_venue WHERE event_id = :event_id AND primary_venue = 'Yes';

Run these in the APPS schema context (or with APPS synonyms) so the OTA_GENERAL business group predicate resolves correctly; otherwise rows outside the caller's business group are excluded, which can appear as missing data if the session is established under an unexpected group.