Search Results event_currency_code




Overview
Explore in AI Chat

Overview

OTA_RESOURCE_BOOKINGS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the OTA (Oracle Learning Management / Training Administration) product family. Its documented purpose is simply to list all resource bookings maintained by the application. In ETRM terms, a resource booking represents the reservation of a supplied resource — such as a venue, trainer, or consumable item — against a scheduled event or activity version. The view consolidates the transactional booking record with descriptive attributes of the resource, the parent event, and any associated finance line, producing a single denormalized row per booking. Because it exposes both surrogate keys and decoded meanings, it is well suited to ad hoc SQL reporting, custom concurrent programs, Discoverer workbooks, and inbound or outbound integration extracts. The view is documented as VALID in both 12.1.1 and 12.2.2, and the metadata confirms the presence of the PRIMARY_VENUE_FLAG column referenced in the user's search, plus ROLE_TO_PLAY, DELEGATES_PER_UNIT, and the TRB_INFORMATION1 through TRB_INFORMATION20 descriptive flexfield columns.

Underlying Base Objects

The view is defined over several base tables and supporting objects. The primary transactional table is OTA_RESOURCE_BOOKINGS (TRB), which supplies the booking identity, status, quantities, required dates and times, contact details, primary venue indicator, role, and the information flexfield segments. Resource definition attributes — resource type, consumable flag, currency, cost, cost unit, and supplied resource identifier — come from OTA_SUPPLIABLE_RESOURCES and its translation table OTA_SUPPLIABLE_RESOURCES_TL. Event context (title, course start and end date and time, training centre, currency, language, location) is drawn from OTA_EVENTS and OTA_EVENTS_TL. Activity version detail is obtained from OTA_ACTIVITY_VERSIONS_TL, vendor information from PO_VENDORS, and finance transfer data from OTA_FINANCE_LINES. Lookups for resource type, booking status, training centre, and trainer participation are resolved via HR_LOOKUPS and the HR_GENERAL.DECODE_FND_COMM_LOOKUP function. The booking person's user name is joined from FND_USER. Both OTA_OFFERINGS and HR_API appear in the documented dependency list, reflecting the view's integration with offering structure and HR person resolution.

Key Columns

Common Use Cases and Queries

Typical reporting scenarios include identifying the primary venue for each event, auditing venue and trainer utilisation, reconciling booked versus required dates, and extracting bookings not yet transferred to finance. The following query lists primary venue bookings with their event context:

SELECT event_id,
       title,
       course_start_date,
       srt_name,
       required_date_from,
       required_date_to
FROM   apps.ota_resource_bookings_v
WHERE  primary_venue_flag = 'Y'
AND    status = 'CONFIRMED';

To examine trainer bookings by role, filter on ROLE_TO_PLAY and resource type; to support cost reconciliation, select rows where TRANSFER_STATUS is null or indicates a pending transfer, joining MONEY_AMOUNT and CURRENCY_CODE to the finance interface. Because the view already resolves lookup meanings and translation names, it eliminates the need for manual joins to HR_LOOKUPS and the _TL tables in most operational reports, though joins to OTA_EVENTS or OTA_OFFERINGS may still be required when additional scheduling or offering attributes are needed.