Results for “priority_level”

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

Overview

OTA_BKNG_JUSTIFICATIONS_B is a foundational configuration table within the Oracle E-Business Suite Learning Management (OTA) module. It supports the waitlist optimization feature by allowing administrators to define booking justification names, each associated with an enrollment priority level. When learners enroll in a class, they may select an applicable justification, which in turn drives the default priority assigned to their enrollment or waitlist position. This mechanism enables organizations to enforce fair and policy-driven seat allocation when class capacity is exceeded.

The table resides in the OTA schema and is classified as VALID in the ETRM 12.2.2 physical schema, containing eleven documented columns. From a Data Vault modeling perspective, the heuristic classification is standalone, meaning the table is not mined as a dependent link or satellite via foreign key structure. It functions conceptually as a reference or lookup hub, owning its own surrogate primary key and serving as the target of dependent transactional references rather than referencing other hubs itself.

Key Information Stored

The table stores administrative definitions for enrollment justifications and their associated ranking behavior. The most significant columns include:

• BOOKING_JUSTIFICATION_ID — The surrogate primary key, uniquely identifying each justification record. It is enforced by the unique index OTA_BKNG_JUSTIFICATIONS_B_PK and serves as the business-key candidate documented in the metadata.
• PRIORITY_LEVEL — The enrollment priority assigned to the justification, used by waitlist optimization to rank or default learner enrollments.
• BUSINESS_GROUP_ID — The multi-tenant partitioning key that scopes the justification to a specific business group, supporting data security and organizational isolation.
• OBJECT_VERSION_NUMBER — The optimistic locking column used by the Oracle Applications framework to detect concurrent updates.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Effective dating columns that control when a justification is valid for selection by learners and administrators.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — Standard WHO audit columns capturing creation and modification provenance.

The primary key BOOKING_JUSTIFICATION_ID is the sole documented unique index; no alternate unique business key is provided, so justification names are not enforced as unique at the database level within the documented schema.

Common Use Cases and Queries

Administrators and developers query this table to report on active justifications and their priority mappings, to validate enrollment behavior, and to reconcile waitlist rankings. A typical pattern retrieves active justifications for a business group:

• SELECT booking_justification_id, priority_level FROM ota_bkng_justifications_b WHERE business_group_id = :p_bg_id AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
• Joining to OTA_DELEGATE_BOOKINGS on BOOKING_JUSTIFICATION_ID to analyze which justifications drive actual enrollment outcomes.
• Reporting priority-level distribution to assess whether waitlist optimization yields balanced seat allocation.

Because the table is effective-dated, reports should always filter on the active date range to avoid returning obsolete justification definitions.

Related Objects

The principal dependent object is OTA_DELEGATE_BOOKINGS, which references this table through the column BOOKING_JUSTIFICATION_ID (foreign key from OTA_DELEGATE_BOOKINGS.BOOKING_JUSTIFICATION_ID to OTA_BKNG_JUSTIFICATIONS_B). This relationship makes the justification table a lookup source for enrollment transactions. Related objects also include the OTA_DELEGATE_BOOKINGS parent enrollment structures, the waitlist optimization configuration components that consume PRIORITY_LEVEL, and standard Learning Management enrollment APIs that surface justification values in the learner self-service enrollment flow. Administrators and integrators should treat OTA_BKNG_JUSTIFICATIONS_B as a controlled reference table, maintaining it through the Learning Management administrative setup rather than direct DML, to preserve the integrity of the priority-assignment logic.