Results for “booking_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OTA_BOOKING_STATUS_HISTORIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OTA product family, Oracle Learning Management, and is documented as a view that lists all information about a student's booking status history. In the OTA data model, a booking represents a learner's enrolment against a course, offering, or class. Every transition that a booking makes through its lifecycle — submitted, waitlisted, confirmed, cancelled, completed, and similar states — is recorded as a row in the booking status history. This view exposes those transactional history records together with the descriptive and translatable names of the status types that were applied.
The view exists primarily to support reporting, enquiry screens, and integration extracts that need to present booking status transitions in a readable form. Because it resolves the status type identifier into a user-facing name in the session language, it is the appropriate source for concurrent programs, Oracle Reports, Oracle XML Publisher templates, and BI Publisher data models that display learner progression through the booking workflow. It is not a table, so it carries no storage of its own and cannot be updated directly; all maintenance is performed against the underlying status history table by the OTA application logic.
Underlying Base Objects
The view is defined over three base objects, accessed through APPS synonyms:
- OTA_BOOKING_STATUS_HISTORIES — the transactional table holding one row per status change applied to a booking. It supplies the booking identifier, the status type identifier, the effective start date, the changer, and free-text comments.
- OTA_BOOKING_STATUS_TYPES — the base status type definition table, supplying the internal status type classification (STATUS_TYPE), such as whether the status represents a confirmed, cancelled, or completed state.
- OTA_BOOKING_STATUS_TYPES_TL — the translatable, language-specific table that supplies the translated status type name (BOOKING_STATUS_TYPE_NAME). It is joined on the language returned by USERENV('LANG'), so the view returns descriptions in the current session language.
The join conditions link all three objects on BOOKING_STATUS_TYPE_ID, with the translation table additionally filtered by LANGUAGE = USERENV('LANG'). The view therefore behaves as an equi-join of the history fact with its status type dimension and its translated label. Because the translation join is language-dependent, results differ between sessions with different NLS language settings.
Key Columns
- ROW_ID — the physical row identifier of the history record, carried through from the base table. It provides a stable handle for the individual history row.
- BOOKING_ID — the identifier of the learner booking to which this status change belongs. It is the principal join key back to the booking tables.
- BOOKING_STATUS_TYPE_ID — the numeric identifier of the status type applied. It joins to OTA_BOOKING_STATUS_TYPES and its translations.
- BOOKING_STATUS_TYPE_NAME — the translated, user-facing name of the status type in the session language. This is typically the value shown on enquiry screens and reports.
- STATUS_TYPE — the internal classification of the status type, used by OTA processing to determine how a booking in that state should behave.
- OBJECT_VERSION_NUMBER — the optimistic locking version of the history row, used by the application framework to detect concurrent updates.
- START_DATE — the effective date on which the status change took effect. It provides the chronological ordering of a booking's history.
- CHANGED_BY — the identifier of the application user who performed the status change. This is the "changed_by" attribute of interest when auditing who moved a booking into a given state.
- COMMENTS — free-text remarks captured at the time of the status change.
Common Use Cases and Queries
Typical uses include auditing who changed a booking's status, reconstructing a learner's enrolment timeline, and feeding data warehouses with status transition facts. To list the complete status history for a single booking in chronological order:
SELECT booking_id, booking_status_type_name, status_type, start_date, changed_by, comments FROM apps.ota_booking_status_histories_v WHERE booking_id = :p_booking_id ORDER BY start_date;
To identify all bookings whose status was changed by a specific user within a date range:
SELECT booking_id, booking_status_type_name, start_date, comments FROM apps.ota_booking_status_histories_v WHERE changed_by = :p_user_id AND start_date BETWEEN :p_from_date AND :p_to_date ORDER BY start_date DESC;
To summarise the volume of each status transition across a period for reporting purposes:
SELECT booking_status_type_name, COUNT(*) FROM apps.ota_booking_status_histories_v WHERE start_date BETWEEN :p_from_date AND :p_to_date GROUP BY booking_status_type_name ORDER BY 2 DESC;
Because BOOKING_STATUS_TYPE_NAME is language-dependent, extracts intended for multilingual environments should capture the NLS language of the session alongside the results, or restrict to a known language, to ensure consistent labelling across runs.
-
View to list all information about a Students Booking Status History.
APPS.OTA_BOOKING_STATUS_HISTORIES_V·↳ OTA_BOOKING_STATUS_HISTORIES·↳ OTA_BOOKING_STATUS_TYPES·↳ OTA_BOOKING_STATUS_TYPES_TL·Explore OTA module →
-
A booking status history records status of changes to a student enrollment.
-
APPS.OTA_TRAINING_COST_LEVELS_V·↳ OTA_ACTIVITY_DEFINITIONS·↳ OTA_ACTIVITY_VERSIONS·↳ OTA_DELEGATE_BOOKINGS·Explore OTA module →
-
APPS.OTA_TRAINING_COST_LEVELS_V·↳ OTA_ACTIVITY_DEFINITIONS·↳ OTA_ACTIVITY_VERSIONS·↳ OTA_DELEGATE_BOOKINGS·Explore OTA module →
-
View: PER_BOOKINGS_V 12.1.1
Used to support user interface
APPS.PER_BOOKINGS_V·↳ PER_ALL_PEOPLE_F·↳ PER_BOOKINGS·↳ PER_EVENTS·Explore PER module →
-
View: PER_BOOKINGS_V3 12.2.2
Used to support user interface
APPS.PER_BOOKINGS_V3·↳ PER_ALL_PEOPLE_F·↳ PER_BOOKINGS·↳ PER_EVENTS·Explore PER module →
-
View to list all information about a Students Booking Status History.
APPS.OTA_BOOKING_STATUS_HISTORIES_V·↳ OTA_BOOKING_STATUS_HISTORIES·↳ OTA_BOOKING_STATUS_TYPES·↳ OTA_BOOKING_STATUS_TYPES_TL·Explore OTA module →
-
View: OTFV_COST_TRANSFER 12.1.1
Business view template from which the flexfield view is generated.
APPS.OTFV_COST_TRANSFER·↳ GL_CODE_COMBINATIONS·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·Explore OTA module →
-
An student booking (delegate booking) records an enrollment onto a scheduled, program or one time event.
-
A booking status history records status of changes to a student enrollment.
-
Event booking details.
-
Bulk Enrollment request member hold the data of the leaner whom is requested to be enrolled into Class, Learning Path or Learning Certification via Bulk Enrollment.
-
View: PER_BOOKINGS_V2 12.2.2
Used to support user interface
APPS.PER_BOOKINGS_V2·↳ FND_SESSIONS·↳ HR_API·↳ HR_GENERAL·Explore PER module →
-
View: PER_BOOKINGS_V2 12.1.1
Used to support user interface
APPS.PER_BOOKINGS_V2·↳ FND_GLOBAL·↳ FND_SESSIONS·↳ HR_API·Explore PER module →
-
View to show the Finance information related to an Event Association
APPS.OTA_EVENT_ASSOCIAT_BILLING_V·↳ AR_LOOKUPS·↳ FND_GLOBAL·↳ HR_API·Explore OTA module →
-
Event booking details.
-
APPS.OTA_TRAINING_PLAN_COSTS_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·↳ OTA_DELEGATE_BOOKINGS·Explore OTA module →
-
A resource allocation records a supplied resource to a student on an event.
-
View: PER_BOOKINGS_V 12.2.2
Used to support user interface
APPS.PER_BOOKINGS_V·↳ PER_ALL_PEOPLE_F·↳ PER_BOOKINGS·↳ PER_EVENTS·Explore PER module →
-
View: PER_BOOKINGS_V3 12.1.1
Used to support user interface
APPS.PER_BOOKINGS_V3·↳ PER_ALL_PEOPLE_F·↳ PER_BOOKINGS·↳ PER_EVENTS·Explore PER module →
-
View: OTFV_COST_TRANSFER 12.2.2
Business view template from which the flexfield view is generated.
APPS.OTFV_COST_TRANSFER·↳ GL_CODE_COMBINATIONS·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_BIS·Explore OTA module →
-
View to show the Finance information related to an Event Association
APPS.OTA_EVENT_ASSOCIAT_BILLING_V·↳ AR_LOOKUPS·↳ HR_API·↳ HR_GENERAL·Explore OTA module →
-
A plan cost is a recorded measure against the training plan.
-
APPS.OTA_TRAINING_PLAN_COSTS_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·↳ OTA_DELEGATE_BOOKINGS·Explore OTA module →
-
A resource allocation records a supplied resource to a student on an event.
-
View: OTA_FINANCE_LINES_V 12.2.2
View to list all information for Finance Lines.
APPS.OTA_FINANCE_LINES_V·↳ AR_LOOKUPS·↳ HR_API·↳ HR_GENERAL·Explore OTA module →
-
An student booking (delegate booking) records an enrollment onto a scheduled, program or one time event.
-
A finance line records each financial transaction with a customer or supplier.
-
A finance line records each financial transaction with a customer or supplier.
-
A plan cost is a recorded measure against the training plan.
-
View: OTA_FINANCE_LINES_V 12.1.1
View to list all information for Finance Lines.
APPS.OTA_FINANCE_LINES_V·↳ AR_LOOKUPS·↳ FND_GLOBAL·↳ HR_API·Explore OTA module →
-
View to list all Student and Customer Enrollment.
APPS.OTA_DELEGATE_BOOKINGS_V·↳ FND_PROFILE·↳ FND_USER·↳ HR_ALL_ORGANIZATION_UNITS_TL·Explore OTA module →
-
View to list all Student and Customer Enrollment.
APPS.OTA_DELEGATE_BOOKINGS_V·↳ FND_PROFILE·↳ FND_USER·↳ HR_ALL_ORGANIZATION_UNITS_TL·Explore OTA module →
-
PACKAGE: APPS.OTA_ILEARNING2 12.2.2
-
VIEW: HR.PER_BOOKINGS# 12.2.2
-
PACKAGE: APPS.OTA_ILEARNING2 12.1.1