Search Results booking_status




Overview
Explore in AI Chat

Overview

OTFV_EVENTS_WITH_VENUE is a Business Intelligence System (BIS) view owned by the APPS schema within Oracle E-Business Suite. It belongs to the Oracle Training Administration (OTA) product family under the Enterprise Training and Resource Management (ETRM) module, and its FND Design Data reference is OTA.OTFV_EVENTS_WITH_VENUE. The view presents a consolidated, denormalized listing of training events for which a venue resource has been booked, joining event header information, translatable event titles, suppliable venue resources, and resource booking transactions into a single queryable structure. Its principal role is to serve reporting, analytical, and integration requirements — particularly for administrators and developers who need to determine which events have venue bookings, when those bookings were made, and their current booking status — without having to navigate the underlying OTA transactional tables directly. Because it is exposed as a public synonym (PUBLIC.OTFV_EVENTS_WITH_VENUE), it is accessible to any database user granted the appropriate privileges, making it suitable for custom reports, BI Publisher data models, and downstream interfaces.

Underlying Base Objects

The view is defined over several documented base objects. OTA_EVENTS and OTA_EVENTS_TL supply the event header and translated title data. OTA_RESOURCE_BOOKINGS provides the actual booking records, including booking dates, required date ranges, status, and comments. OTA_SUPPLIABLE_RESOURCES and OTA_SUPPLIABLE_RESOURCES_TL supply the venue resource identity and its translatable descriptions. Two packages, HR_BIS and OTA_GENERAL, are also referenced, indicating that the view leverages shared business logic — such as security or descriptive-flexfield resolution — rather than relying purely on table joins. This dependency on HR_BIS is significant in a multi-organization context, as it enforces the organizational security model applied across HR and OTA. The view is itself referenced by a PUBLIC synonym of the same name, confirming that it is intended as a stable, externally consumable interface rather than an internal-only construct.

Key Columns

The view exposes twelve columns. EVENT_TITLE (VARCHAR2 80) carries the event name. VENUE_NAME (VARCHAR2 400) holds the venue resource name, while PRIMARY_VENUE (VARCHAR2 4000) indicates the primary venue association. DATE_OF_BOOKING records when the booking was created. BOOKING_STATUS (VARCHAR2 4000) is the column most commonly searched — it reflects the current state of the resource booking (for example, confirmed or cancelled) and is essential for filtering active versus inactive venue commitments. REQUIRED_FROM and REQUIRED_TO define the date range over which the venue is required. BOOKING_COMMENTS (VARCHAR2 2000) stores free-text notes attached to the booking. RESOURCE_BOOKING_ID uniquely identifies the booking row and is the natural join key back to OTA_RESOURCE_BOOKINGS. SUPPLIED_RESOURCE_ID identifies the specific supplied resource instance. EVENT_ID and OFFERING_ID link the row back to the parent event and its offering, enabling further joins to event and offering detail tables.

Common Use Cases and Queries

Typical uses include auditing venue utilization, reconciling bookings against event schedules, and feeding booking data into third-party scheduling systems. A frequent requirement is to list all confirmed venue bookings within a date window:

  • SELECT event_title, venue_name, date_of_booking, booking_status FROM apps.otfv_events_with_venue WHERE booking_status = 'CONFIRMED' AND required_from >= SYSDATE;
  • SELECT event_id, offering_id, resource_booking_id, booking_comments FROM apps.otfv_events_with_venue WHERE event_id = :p_event_id;
  • SELECT venue_name, COUNT(*) FROM apps.otfv_events_with_venue GROUP BY venue_name ORDER BY 2 DESC;

Because BOOKING_STATUS is a derived VARCHAR2(4000) value driven by lookup logic in the underlying packages, report authors should resolve its display meaning through the appropriate OTA lookup rather than hard-coding literals. The view remains valid in both 12.1.1 and 12.2.2, and its public synonym ensures compatibility across custom reporting layers.