Search Results content_player_status

Overview

OTA_DELEGATE_BOOKINGS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Learning Management module (OTA). Its documented purpose is to list all Student and Customer Enrollment records — that is, delegate bookings captured against learning activities — by denormalizing the underlying OTA_DELEGATE_BOOKINGS table together with the person, customer, organization, and booking-status attributes needed for presentation. In EBS 12.1.1 and 12.2.2 the object is reported with a VALID status, so it can be queried directly by custom reports, concurrent programs, OBIEE extracts, and integration interfaces without depending on private internal structures.

The view resolves the two distinct enrollment populations that Learning Management supports: internal delegates (employees, where CUSTOMER_ID is null and the person attributes are drawn from the PER tables) and external delegates (customer contacts, where CUSTOMER_ID is populated and the attributes come from the HZ customer-model tables). A set of DECODE expressions throughout the view text implements this branch logic, including a Japan-specific branch keyed on the business group legislation code.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view references the following documented objects: the synonym OTA_DELEGATE_BOOKINGS (the primary driving table), OTA_BOOKING_STATUS_TYPES_TL for status names, OTA_EVENTS and OTA_EVENTS_TL, OTA_ACTIVITY_VERSIONS_TL, OTA_BOOKING_DEALS, OTA_FINANCE_HEADERS and OTA_FINANCE_LINES, and the packages OTA_TDB_BUS and OTA_GENERAL. Person and assignment data come from the synonyms PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and PER_ADDRESSES, with PER_BUSINESS_GROUPS and HR_ALL_ORGANIZATION_UNITS_TL supplying business group and organization context. Customer-side data is drawn from HZ_PARTIES, HZ_ORG_CONTACTS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_RELATIONSHIPS. Supporting utility objects include the synonyms FND_USER and the package FND_PROFILE, plus the package HR_GENERAL, whose DECODE_LOOKUP and DECODE_AR_LOOKUP functions translate codes such as TITLE and CONTACT_TITLE into display values.

Key Columns

• BOOKING_ID / BOOKING_STATUS_TYPE_ID — the delegate booking identifier and its status type; the status name is resolved through OTA_BOOKING_STATUS_TYPES_TL as BST.NAME.
• CUSTOMER_ID / CUSTOMER_NAME — populated for customer (external) enrollments; null identifies an internal student enrollment. The DECODE that yields 'O'/'C' and 'OR'/'CU' derives from this column and is commonly used as a built-in enrollment-type discriminator.
• DELEGATE_PERSON_ID, DELEGATE_ASSIGNMENT_ID, DELEGATE_CONTACT_ID — the delegate identity keys for the employee, assignment, or customer-contact paths respectively.
• Delegate name and number columns — first name, last name, full name, applicant number, employee number, and title, each resolved conditionally for internal versus external delegates, with Japan-specific person-information columns used when the business group legislation code is 'JP'.
• SPONSOR_PERSON_ID, SPONSOR_ASSIGNMENT_ID, CONTACT_ID — the sponsoring person or contact for the booking, with parallel name and number derivations.
• ORGANIZATION_ID / organization name — the delegate or customer organization, resolved via HR_ALL_ORGANIZATION_UNITS_TL.
• BUSINESS_GROUP_ID — the operating business group, which also drives legislation-dependent formatting.

Because the view is built with DECODE and package-function calls rather than a simple join projection, several columns carry placeholder or sentinel values (for example, -1 or '****') when the related person or organization record is absent. Report logic should treat these as "not applicable" rather than as real data.

Common Use Cases and Queries

Typical uses include enrollment rosters per learning event, delegate status tracking, customer-versus-employee enrollment breakdowns, and finance reconciliation against OTA_FINANCE_HEADERS and OTA_FINANCE_LINES. A search on "date_status_changed" often reflects a requirement to report when a booking's status last changed; the view's exposed status columns (BOOKING_STATUS_TYPE_ID and the resolved name) provide the status dimension for such reporting, while the audit date itself is normally sourced from the underlying booking or status-history data rather than from this view. A representative query for delegate names and statuses is:

• SELECT booking_id, customer_id, delegate_person_id, booking_status_type_id FROM apps.ota_delegate_bookings_v WHERE customer_id IS NULL;
• SELECT booking_id, customer_name, booking_status_type_id FROM apps.ota_delegate_bookings_v WHERE customer_id IS NOT NULL AND business_group_id = :p_bg_id;
• SELECT booking_id, organization_id, delegate_person_id FROM apps.ota_delegate_bookings_v WHERE booking_status_type_id = :p_status ORDER BY booking_id;

Queries should filter on BUSINESS_GROUP_ID or the organization columns to keep result sets scoped, and should join back to OTA_DELEGATE_BOOKINGS when audit or date-changed attributes not exposed by the view are required.