Search Results event_duration_units




Overview
Explore in AI Chat

Overview

OTFV_HR_RESTRICTED_EVENTS is an APPS-owned business view template in the Oracle E-Business Suite Learning Management module (OTA). It is the source definition from which the Oracle Training Administration flexfield view is generated, and it exposes training event and event-association data restricted to the structures an HR business group controls. In Oracle EBS 12.1.1 and 12.2.2 the object carries a VALID status in the ETRM repository and is classified as a VIEW.

Because it is a business view template rather than a directly maintained entity, the view exists to project descriptive training-event attributes — status, scheduling, pricing, and audience targeting — into a form suitable for HR-facing reporting and integration. The description string embedded in the definition (_DF:OTA:OTA_EVENTS:EVT and _DF:OTA:OTA_EVENT_ASSOCIATIONS:TEA) identifies the two descriptor flexfields the generated view supplies. For the term event_user_status, the relevant projection is the column EVENT_USER_STATUS, which decodes OTA_EVENTS.USER_STATUS against the EVENT_USER_STATUS lookup type.

Underlying Base Objects

The view joins a defined set of base synonyms, views, and packages. Documented dependencies are:

Key Columns

Common Use Cases and Queries

Typical usage is a reporting query that filters on user status or business group. Because the coded columns are already decoded, the results can be presented without additional lookup joins:

  • List events by user status within a business group.
  • Audit restricted events (SECURE_EVENT = 'Yes') and their audience.
  • Report enrollment windows and attendee thresholds for scheduled offerings.
SELECT business_group_name,
       event_title,
       event_start_date,
       event_status,
       event_user_status
FROM   apps.otfv_hr_restricted_events
WHERE  event_user_status = 'Confirmed'
ORDER  BY event_start_date;

All access should be through the APPS schema or a synonym granting the equivalent privileges, and filters should be applied on the decoded columns rather than the underlying lookup codes.