Search Results attended_ext_student_count

Overview

APPS.OTFV_ENROLLED_EVENTS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite Oracle Training Administration (OTA) module, part of the Enterprise Training and Requirements Management (ETRM) product family. It is documented under FND Design Data OTA.OTFV_ENROLLED_EVENTS with a status of VALID, and its ETRM metadata is maintained consistently across EBS 12.1.1 and 12.2.2. The view presents enrollment-level information for internal and external students enrolled on a specific class, aggregated with their enrollment and attendance statuses. Because it is a BIS view, it is intended primarily for reporting, analytics, and integration scenarios rather than for transactional processing. Users who search for the column requested_enrollment will find it exposed here as a NUMBER column, alongside related enrollment count columns such as ATTENDED_ENROLLMENT, PLACED_ENROLLMENT, and WAITLISTED_ENROLLMENT. The view therefore acts as a denormalized reporting surface over the OTA enrollment and booking model, allowing report authors to retrieve student, class, course, and booking information without joining the underlying normalized tables manually.

Underlying Base Objects

The view is owned by APPS and is defined over a substantial set of synonym-referenced base objects. Core OTA training objects include OTA_EVENTS and OTA_EVENTS_TL (the class/event definition and its translations), OTA_ACTIVITY_VERSIONS and OTA_ACTIVITY_VERSIONS_TL, OTA_OFFERINGS, OTA_PERFORMANCES, OTA_LEARNING_OBJECTS, OTA_DELEGATE_BOOKINGS, OTA_BOOKING_STATUS_TYPES and OTA_BOOKING_STATUS_TYPES_TL. HR and person data are drawn from PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_JOBS, PER_JOB_EXTRA_INFO, PER_ADDRESSES, HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL, and HR_LOCATIONS_ALL_TL. External student and customer data come from the HZ schema objects, including HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_ORG_CONTACTS, HZ_RELATIONSHIPS, HZ_CUST_ACCT_SITES, HZ_PARTY_SITES, and HZ_LOCATIONS. Supporting PL/SQL packages referenced by the view include HR_BIS, OTA_GENERAL, OTA_LO_UTILITY, OTA_TDB_BUS, and OTA_UTILITY. This combination shows that the view consolidates internal employee records and external customer/contact records into a single enrollment reporting model.

Key Columns

The view exposes identity and contextual columns including BUSINESS_GROUP_NAME, PERSON_NAME, CUSTOMER_NAME, ASSIGNMENT_NUMBER, ASSIGNMENT_ORGANIZATION, ASSIGNMENT_LOCATION, ASSIGNMENT_JOB, and ASSIGNMENT_JOB_CATEGORY. Class and course context is provided by EVENT_TITLE, EVENT_COMMENTS, COURSE_START_DATE, COURSE_END_DATE, TRAINING_CENTER, ORGANIZATION_NAME, ACTIVITY_NAME, LANGUAGE, and DATE_BOOKING_PLACED. Enrollment status columns include BOOKING_STATUS, BOOKING_STATUS_TYPE, CURRENT_EMPLOYEE_FLAG, and INTERNAL_BOOKING_FLAG, which distinguish internal students from external ones. Attendance and outcome data are represented by ATTENDANCE_RESULT, FAILURE_REASON, SUCCESSFUL_ATTENDANCE_FLAG, TOTAL_TRAINING_TIME, PLAYER_STATUS, TEST_SCORE, NUMBER_OF_MODULES_COMPLETED, and TOTAL_MODULES. The searched column REQUESTED_ENROLLMENT is a NUMBER indicating the count of requested enrollments for the event, and it sits alongside ATTENDED_ENROLLMENT, PLACED_ENROLLMENT, and WAITLISTED_ENROLLMENT as part of the view's capacity and demand metrics. Related aggregate columns include NUMBER_OF_PLACES, NUMBER_OF_SUCCESSFUL_PLACES, CONFIRMED_INT_STUDENT_COUNT, CONFIRMED_EXT_STUDENT_COUNT, ATTENDED_INT_STUDENT_COUNT, ATTENDED_EXT_STUDENT_COUNT, NON_ATTENDED_INT_STUDENT_COUNT, NON_ATTENDED_EXT_STUDENT_COUNT, CANCELLED_INT_STUDENT_COUNT, CANCELLED_EXT_STUDENT_COUNT, SUCC_ATT_INT_STUDENT_COUNT, SUCC_ATT_EXT_STUDENT_COUNT, NON_SUCC_ATT_INT_STUDENT_COUNT, NON_SUCC_ATT_EXT_STUDENT_COUNT, TRAINING_TARGET_TYPE, DURATION, and DURATION_UNITS.

Common Use Cases and Queries

Typical uses include class roster reporting, enrollment demand analysis, attendance tracking, and reconciliation of internal versus external student participation. A simple query retrieving classes with pending requested enrollments might be:

• SELECT event_title, course_start_date, training_center, requested_enrollment, placed_enrollment, waitlisted_enrollment FROM apps.otfv_enrolled_events WHERE requested_enrollment > 0 ORDER BY course_start_date;
• SELECT person_name, customer_name, internal_booking_flag, booking_status, attendance_result, successful_attendance_flag FROM apps.otfv_enrolled_events WHERE event_title = :event_title;
• SELECT organization_name, SUM(requested_enrollment), SUM(attended_enrollment) FROM apps.otfv_enrolled_events GROUP BY organization_name;

Because the view is read-only and built for reporting, it should not be used for data updates. For performance, filter on indexed base attributes such as dates, organizations, or event identifiers where possible, and be aware that the large number of underlying joins, including HR and HZ tables, can make unrestricted queries expensive. Where additional detail is required beyond the exposed columns, report authors should join back to the OTA_EVENTS, OTA_DELEGATE_BOOKINGS, or PER_ALL_PEOPLE_F base objects using the keys already represented in the view.