Search Results ota_events_fk2

Overview

OTA.OTA_EVENTS is the central scheduling and delivery table within the Oracle E-Business Suite Training Administration (OTA) module. It represents every event that the enterprise schedules, enrolls learners into, or books resources against. Four distinct event categories are supported by the single physical structure: scheduled events (a specific instance of an activity version that accepts enrollments and resource bookings), sessions (units of time within a scheduled event for which resources are booked independently), development events (mechanisms for allocating employee time and resources to create or enhance training activities), and programs (grouped events scheduled together, on which students enroll collectively). The row carries both the administrative envelope of an event — status, currency, pricing, attendance limits, timezone, and location — and the descriptive context, including title, comments, and a twenty-segment DFF (EVT_INFORMATION1 through EVT_INFORMATION20).

In Data Vault modeling terms, the FK topology mined from the documented constraints suggests OTA_EVENTS behaves as a hub: EVENT_ID is the surrogate anchor, and the surrounding non-unique foreign key indexes (activity version, offering, organization, training center, location, parent event) form the surrounding link and satellite relationships. This is offered as a modeling suggestion derived from the index structure rather than a declared classification.

Key Information Stored

The documented physical schema contains 73 columns. The columns of primary significance are:

• EVENT_ID — surrogate primary key, enforced by unique index OTA_EVENTS_PK on tablespace APPS_TS_TX_IDX.
• LINE_ID — business-key candidate; unique index OTA_EVENTS_UK3.
• OFFERING_ID — business-key candidate and foreign key to OTA_OFFERINGS; unique index OTA_EVENTS_UK4.
• ACTIVITY_VERSION_ID — foreign key to OTA_ACTIVITY_VERSIONS, identifying the academic version being delivered.
• EVENT_TYPE — discriminator distinguishing scheduled event, session, development event, or program.
• PARENT_EVENT_ID — self-referencing foreign key expressing event-to-session or program-to-event hierarchies.
• BUSINESS_GROUP_ID, ORGANIZATION_ID, ORG_ID — multi-org and business-group ownership.
• PROJECT_ID, TRAINING_CENTER_ID, LOCATION_ID, VENDOR_ID, OWNER_ID, LANGUAGE_ID — non-unique indexed references into the surrounding master data.
• COURSE_START_DATE, COURSE_END_DATE, COURSE_START_TIME, COURSE_END_TIME, DURATION, DURATION_UNITS, TIMEZONE — scheduling envelope.
• EVENT_STATUS, USER_STATUS, PUBLIC_EVENT_FLAG, SECURE_EVENT_FLAG, EVENT_AVAILABILITY — lifecycle and visibility state.
• STANDARD_PRICE, PRICE_BASIS, CURRENCY_CODE — commercial attributes.
• Standard WHO columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE and the OBJECT_VERSION_NUMBER concurrency token.

Common Use Cases and Queries

Typical reporting requirements include identifying all scheduled events for an activity version, rolling up sessions to their parent scheduled event, and driving enrollment or resource booking reports. A representative query joining on the documented keys:

• Event list by activity version:
  SELECT e.event_id, e.title, e.event_status, e.course_start_date FROM ota_events e WHERE e.activity_version_id = :p_activity_version_id AND e.event_type = 'SCHEDULED';
• Sessions under a scheduled event, using the self-referencing key:
  SELECT s.event_id, s.course_start_date FROM ota_events s WHERE s.parent_event_id = :p_event_id;
• Enrollment counts per offering (joining the UK4 business key):
  SELECT e.offering_id, COUNT(a.event_id) FROM ota_events e, ota_attempts a WHERE a.event_id = e.event_id GROUP BY e.offering_id;
• Resource utilization by training center and location, joining on the documented FK indexes to produce capacity and conflict analysis.

Because OTA_EVENTS_FK2 indexes BUSINESS_GROUP_ID and OTA_EVENTS_N51 indexes LANGUAGE_ID, multilingual and multi-business-group extractions should filter through these indexed paths to avoid full scans on APPS_TS_TX_DATA.

Related Objects

The documented foreign key relationships and inbound references establish the following key dependencies:

• OTA_ACTIVITY_VERSIONS — parent of ACTIVITY_VERSION_ID; the catalog definition of the training being delivered.
• OTA_OFFERINGS — parent of OFFERING_ID; the commercial packaging of events.
• OTA_EVENTS (self-reference) — PARENT_EVENT_ID models program-to-event and event-to-session containment.
• CSS_DEF_LANGUAGES_B — LANGUAGE_ID reference for language-enabled delivery.
• OTA_ATTEMPTS — inbound by EVENT_ID; learner enrollment attempts against the event.
• OTA_RESOURCE_BOOKINGS — inbound by EVENT_ID; resource reservations tied to the event.
• OTA_DELEGATE_BOOKINGS and OTA_BOOKING_DEALS — inbound by EVENT_ID; commercial booking management.
• OTA_PROGRAM_MEMBERSHIPS — inbound on both EVENT_ID and PROGRAM_EVENT_ID, expressing program composition.
• OTA_CONFERENCES, OTA_EVENT_ASSOCIATIONS, OTA_ACT_CAT_INCLUSIONS, OTA_TRAINING_PLAN_COSTS — additional inbound dependents supporting conference delivery, event associations, catalog inclusion, and planned cost rollups.