Search Results resource_booked

Overview

OTFV_TRAINING_EVENTS is an APPS-owned Business Intelligence System (BIS) view registered under the FND Design Data application OTA (Oracle Training Administration). It exposes a denormalized, reporting-oriented projection of Oracle EBS Training Administration event data, consolidating event header information from the base transactional tables together with related descriptive, financial, and organizational attributes. The view is intended primarily for read-only reporting and integration rather than transactional maintenance, which is consistent with its classification as a BIS view.

The object is valid on both Oracle EBS 12.1.1 and 12.2.2. The name of the view and the presence of the PUBLIC_EVENT column explain why a search for "public_event" surfaces this object: PUBLIC_EVENT is the flag indicating whether a training event is open to enrollment beyond a restricted audience. In the context of the R12 OTA schema, this view provides a single flat source for event listing, catalog reporting, and downstream extracts without requiring the report author to join the several base entities manually.

Underlying Base Objects

The documented dependency list shows the view is defined over a mix of synonymed base tables, views, and packaged logic. The principal transactional source is OTA_EVENTS, with translatable descriptive text resolved from OTA_EVENTS_TL. Activity and version attributes are drawn from OTA_ACTIVITY_DEFINITIONS, OTA_ACTIVITY_DEFINITIONS_TL, OTA_ACTIVITY_VERSIONS, and OTA_ACTIVITY_VERSIONS_TL, while categorization is resolved through OTA_CATEGORY_USAGES and OTA_CATEGORY_USAGES_TL. Offering-level data is supplied by OTA_OFFERINGS.

Financial and organizational context is joined from PA_PROJECTS, PO_VENDORS (itself a view), HR_ALL_ORGANIZATION_UNITS_TL, and PER_ALL_PEOPLE_F. Several packages participate in the derivation of display values: HR_BIS, OTA_EVT_SHD, OTA_GENERAL, and OTA_UTILITY. Because the view references these packages and synonymed objects, its runtime behavior depends on the standard OTA and HR security context, including business group and security profile resolution.

Key Columns

The view exposes over forty columns spanning identity, scheduling, capacity, and financial dimensions. Event identification and description are carried by EVENT_ID, BUSINESS_GROUP_ID, BUSINESS_GROUP_NAME, EVENT_TITLE, and EVENT_COMMENTS. Scheduling attributes include COURSE_START_DATE, COURSE_END_DATE, COURSE_START_TIME, COURSE_END_TIME, TIME_ZONE, DURATION, DURATION_UNITS, and the enrollment window columns ENROLLMENT_START_DATE and ENROLLMENT_END_DATE.

Capacity and access controls are represented by MINIMUM_ATTENDEES, MAXIMUM_ATTENDEES, MAXIMUM_INTERNAL_ATTENDEES, RESOURCE_BOOKED, SECURED_EVENT, ONLINE_FLAG, and the column of interest, PUBLIC_EVENT. Financial columns include STANDARD_PRICE, PRICE_BASIS, ACTUAL_COST, BUDGET_COST, BUDGET_COST_CURRENCY, and INVOICE_AMOUNT. Organizational and project context is provided by ORGANIZATION_NAME, EVENT_CENTER, OWNER_NAME, CATEGORY_NAME, PROJECT_NAME, PROJECT_NUMBER, and SUPPLIER_NAME. The _DF column carries descriptive flexfield context.

Common Use Cases and Queries

Typical usage includes catalog extracts of publicly enrollable events, capacity and utilization reporting, and reconciliation of event cost against budgeted amounts. The following example returns open public events within a date range, ordered by start date:

• SELECT event_id, event_title, course_start_date, course_end_date, standard_price, maximum_atten

Sample statement:

• SELECT event_id, event_title, course_start_date, course_end_date, maximum_attendees, standard_price FROM apps.otfv_training_events WHERE public_event = 'Y' AND business_group_id = :p_bg_id AND course_start_date BETWEEN :p_from AND :p_to ORDER BY course_start_date;

Additional scenarios include filtering by SECURED_EVENT for access-controlled offerings, grouping by ORGANIZATION_NAME or EVENT_CENTER for delivery-center dashboards, and using ACTUAL_COST versus BUDGET_COST with BUDGET_COST_CURRENCY for cost variance analysis. Because the view is registered as a BIS view and joins translatable tables, queries should constrain BUSINESS_GROUP_ID and rely on the session's language environment to resolve translated titles properly.