Results for “ota_booking_status_types_pk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OTA_BOOKING_STATUS_TYPES is a reference and setup table in the Oracle E-Business Suite Learning Management module (product code OTA). It stores the list of user-defined booking status types that an enterprise may assign to learner enrollments and bookings, together with the corresponding system status semantics. In ETRM terminology, a "booking" is an enrollment of a learner (or delegate) in a course, class, or offering; the status type defines the business meaning of that enrollment state, such as pending, confirmed, waitlisted, cancelled, or completed. Administrators define these statuses per business group, and the application uses them to drive workflow transitions, eligibility rules, and reporting classifications across the learning lifecycle.

Heuristic Data Vault classification mined from the foreign-key structure places this object as hub-leaning: it is a relatively stable, business-keyed entity that acts as the parent or reference point for several transactional child tables. Under a Data Vault modeling suggestion, OTA_BOOKING_STATUS_TYPES would be modelled as a hub keyed on the business key, with the descriptive and auditing attributes carried in an attached satellite. The table is owned by the OTA schema and is documented as VALID in ETRM for 12.1.1 and 12.2.2.

Key Information Stored

The physical schema in ETRM 12.2.2 documents 36 columns. The most significant are:

• BOOKING_STATUS_TYPE_ID — the surrogate primary key, enforced by OTA_BOOKING_STATUS_TYPES_PK. All child tables reference this column.
• NAME and BUSINESS_GROUP_ID — together they form the unique business key, enforced by OTA_BOOKING_STATUS_TYPES_UK2. The user search term "ota_booking_status_types_uk2" corresponds directly to this index. NAME holds the user-visible status label; BUSINESS_GROUP_ID scopes the definition to a specific operating unit or business group, so the same status name may exist independently across groups.
• TYPE — identifies the system status category that the user-defined status maps to, enabling the application to treat custom statuses consistently.
• ACTIVE_FLAG — controls whether the status remains available for assignment.
• DEFAULT_FLAG — designates the status applied by default when a new booking is created.
• PLACE_USED_FLAG — indicates whether a booking in this status consumes a seat or place in the class.
• DESCRIPTION and COMMENTS — free-text documentation for administrators and end users.
• OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard EBS audit columns.
• BST_INFORMATION_CATEGORY and BST_INFORMATION1 through BST_INFORMATION20 — a descriptive flexfield segment set (the DFF is named BST_INFORMATION), allowing customers to capture additional site-specific attributes without schema changes.

Common Use Cases and Queries

Typical usage includes setup validation, status-driven reporting, and reconciliation of enrollment populations. A common query lists all active statuses for a business group, resolving the default:

• SELECT booking_status_type_id, name, type, default_flag FROM ota_booking_status_types WHERE business_group_id = :p_bg AND active_flag = 'Y';
• Looking up the surrogate key by business key, the pattern used whenever an interface or API must convert a status name into its ID: SELECT booking_status_type_id FROM ota_booking_status_types WHERE name = :p_name AND business_group_id = :p_bg;
• Counting bookings per status by joining to OTA_BOOKING_STATUS_HISTORIES or the delegate booking table on BOOKING_STATUS_TYPE_ID, useful for enrollment funnel reports.
• Identifying statuses that do not consume a place (PLACE_USED_FLAG = 'N') for capacity and waitlist analysis.

Because the DFF columns are available, reporting layers can also surface BST_INFORMATION segments when customer-specific metadata is populated.

Related Objects

The FK metadata documents three dependent tables that reference BOOKING_STATUS_TYPE_ID:

• OTA_BOOKING_STATUS_EXCL — stores exclusion rules between status types (for example, statuses that cannot coexist), joining via OTA_BOOKING_STATUS_EXCL.BOOKING_STATUS_TYPE_ID.
• OTA_BOOKING_STATUS_HISTORIES — records the chronological status transitions of bookings, joining via OTA_BOOKING_STATUS_HISTORIES.BOOKING_STATUS_TYPE_ID; the principal source for audit and duration reporting.
• OTA_DELEGATE_BOOKINGS — holds delegate-level bookings whose current status references this table via OTA_DELEGATE_BOOKINGS.BOOKING_STATUS_TYPE_ID.

In practice, these statuses also surface through the Learning Management booking and enrollment APIs and concurrent programs that create or transition bookings, all of which must resolve a NAME/BUSINESS_GROUP_ID pair to a valid BOOKING_STATUS_TYPE_ID before writing transactional rows.