Results for “application_id”

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

Overview

OTA_BOOKING_STATUS_EXCL is a configuration table in the Oracle EBS Learning Management (OTA) module. It defines booking status exclusions that restrict users operating under specific responsibilities from handling enrollments that carry certain booking statuses. In practical terms, the table acts as a negative filter: rather than granting access, it removes access to enrollments in designated statuses for designated responsibilities, enforcing segregation of duties and workflow control within the learning management enrollment life cycle.

Under a heuristic Data Vault classification mined from its foreign key structure, this table leans toward a satellite object. It lacks the multi-entity reference pattern typical of a link table and does not function as a standalone hub; instead it holds descriptive exclusion attributes attached to a combination of responsibility and booking status context. This classification should be treated as a modeling suggestion rather than a documented property of the physical schema.

Key Information Stored

The documented physical schema for 12.2.2 lists three columns in the OTA schema. The primary key, OTA_BOOKING_STATUS_EXCL_PK, is a composite business key rather than a generated surrogate, defined over all three columns:

• APPLICATION_ID — Identifies the Oracle EBS application (product) context under which the exclusion applies, scoping the rule to the correct application registration.
• RESPONSIBILITY_ID — References the responsibility granted to a user. It identifies the responsibility whose users are prevented from handling the excluded booking statuses.
• BOOKING_STATUS_TYPE_ID — References OTA_BOOKING_STATUS_TYPES, identifying the booking status that is excluded for the given application and responsibility combination.

Because the primary key spans all three columns, no separate surrogate identifier exists in the documented metadata. The unique index OTA_BOOKING_STATUS_EXCL_PK is the sole documented business-key candidate, and it enforces uniqueness of each APPLICATION_ID / RESPONSIBILITY_ID / BOOKING_STATUS_TYPE_ID triple, preventing duplicate exclusion rules from being defined for the same combination. The table contains no descriptive or denormalized columns; it is a pure intersection of configuration values.

Common Use Cases and Queries

Administrators and functional consultants query this table to audit which responsibilities are barred from acting on enrollments in particular statuses, and to troubleshoot enrollment actions that appear disabled for a given user. Because exclusions are evaluated at runtime by the enrollment workflow, verifying the rules is a frequent diagnostic step when users report missing buttons or blocked transactions.

A typical query resolves responsibility and status identifiers into readable names:

• Join OTA_BOOKING_STATUS_EXCL to FND_RESPONSIBILITY (via RESPONSIBILITY_ID and APPLICATION_ID) to list the responsibilities affected by exclusions.
• Join to OTA_BOOKING_STATUS_TYPES on BOOKING_STATUS_TYPE_ID to display the excluded status names.
• Filter by APPLICATION_ID to scope results to the Learning Management application in a multi-application instance.

Reporting use cases include producing a matrix of responsibility versus excluded booking status for security reviews, and comparing exclusion rules across environments during a clone or migration to ensure configuration parity. A standard pattern is a three-way join: OTA_BOOKING_STATUS_EXCL e, OTA_BOOKING_STATUS_TYPES t, and FND_RESPONSIBILITY r, selecting responsibility name and status name for reporting.

Related Objects

The following objects are most significant in relation to this table, based on documented key relationships and module dependencies:

• OTA_BOOKING_STATUS_TYPES — Referenced by the foreign key OTA_BOOKING_STATUS_EXCL.BOOKING_STATUS_TYPE_ID; supplies the valid status values eligible for exclusion.
• FND_APPLICATION — Source of the APPLICATION_ID context that scopes each exclusion rule.
• FND_RESPONSIBILITY — Source of the RESPONSIBILITY_ID used to identify the responsibility to which the exclusion applies.
• OTA_ENROLLMENTS / OTA_BOOKINGS — The transactional enrollment and booking records whose statuses are subject to these exclusions at runtime.
• OTA_BOOKING_STATUS_EXCL_PK — The composite unique index enforcing key integrity on the three documented columns.

Together these objects form the enforcement chain: the exclusion table maps responsibilities to forbidden statuses, the status types table defines those statuses, and the enrollment transactions apply the resulting restrictions during user activity.