Search Results student_full_name




Overview
Explore in AI Chat

Overview

OTFV_ENROLLMENT_STATUS_HISTORY is an Oracle Application Object Library (APPS) business view owned by the APPS schema and shipped as part of the OTA – Learning Management module. It is a business view template from which the flexfield view is generated, exposing the historical progression of enrollment (booking) statuses for learners within the Oracle E-Business Suite environment. In releases 12.1.1 and 12.2.2 the view is delivered with STATUS = VALID, and its primary role is to flatten the relationship between booking status history records, delegate booking (enrollment) details, event delivery data, learner identity, and organization information into a single stable cursor suitable for reporting, Oracle Discoverer / BI Publisher integrations, and HRMS business intelligence extraction. The view is commonly invoked when users search for enrollment activity keyed on attributes such as date_booking_placed, which is surfaced directly from OTA_DELEGATE_BOOKINGS.

Underlying Base Objects

The view text joins several documented base objects. The central driving table is OTA_BOOKING_STATUS_HISTORIES (alias BSH), which stores the sequence of status changes applied to a booking. It is joined to OTA_BOOKING_STATUS_TYPES (BST) on BOOKING_STATUS_TYPE_ID to resolve the status name, active flag, and default flag. The enrollment itself is sourced from OTA_DELEGATE_BOOKINGS (TDB), which supplies DATE_BOOKING_PLACED, TOTAL_TRAINING_TIME, CONTENT_PLAYER_STATUS, SCORE, COMPLETED_CONTENT, and TOTAL_CONTENT. Event delivery data is drawn from OTA_EVENTS (EVT), the learner from PER_ALL_PEOPLE_F (PER) using FULL_NAME, the offering from OTA_OFFERINGS, and the activity structure from OTA_ACTIVITY_VERSIONS (TAV), OTA_ACTIVITY_DEFINITIONS (TAD), and their translated (_TL) counterparts. Organization names are resolved from HR_ALL_ORGANIZATION_UNITS_TL (ORGT for the learner organization and BGRT for the business group). The list of documented referenced objects also includes OTA_ACTIVITY_DEFINITIONS_TL, OTA_ACTIVITY_VERSIONS_TL, OTA_BOOKING_STATUS_TYPES_TL, OTA_EVENTS_TL, OTA_GENERAL, OTA_LEARNING_OBJECTS, OTA_PERFORMANCES, and the HR_BIS package, which performs lookup decoding. Customer-related columns (CUSTOMER_NAME, CUSTOMER_ID) are always NULL because the WHERE clause filters TDB.CUSTOMER_ID IS NULL, restricting the view to delegate (person) enrollments.

Key Columns

Common Use Cases and Queries

Typical scenarios include enrollment audit reporting, learner status aging analysis, and reconciliation of training completed against booking dates. Because the view already resolves lookups and HR names, it is frequently used in place of direct joins to OTA tables. A representative query filtering on the searched column is:

SELECT student_full_name,
       enrollment_status,
       date_booking_placed,
       event_title,
       course_start_date,
       total_training_time
FROM   apps.otfv_enrollment_status_history
WHERE  TRUNC(date_booking_placed) BETWEEN :p_start AND :p_end
  AND  business_group_id = :p_bg_id
ORDER BY date_booking_placed DESC;

Additional uses include grouping counts of enrollments by status over time, identifying learners who have booked but not completed training (NUMBER_OF_MODULES_COMPLETED < TOTAL_MODULES), or extracting ACTIVITY_NAME and ACTIVITY_TYPE for certification tracking. Because CUSTOMER_NAME and CUSTOMER_ID are NULL by design, consumers requiring external customer enrollment data should query the underlying base tables rather than this delegate-focused view.