Search Results ota_open_fc_enrollments




Overview
Explore in AI Chat

Overview

OTA_OPEN_FC_ENROLLMENTS is a transactional table in the OTA (Oracle Training Administration / Learning Management) schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. Its documented purpose is to store the enrollment records for all category-based chat sessions and forums delivered through the Learning Management open forum and chat framework. Each row represents a single enrollment linking a learner (or their contact record) to a specific chat or forum offering, enabling administrators and learners to track participation in collaborative, non-catalog learning activities.

Because the table consists almost entirely of foreign key references to the parent chat and forum entities plus the enrolled person, the ETRM metadata's heuristic Data Vault classification places this object as a link table. In a Data Vault 2.0 modeling exercise, OTA_OPEN_FC_ENROLLMENTS would typically be represented as a link between the hub for forums (OTA_FORUMS_B) and the hub for chats (OTA_CHATS_B), with the enrollment identity acting as the link key. This is a modeling suggestion only; the physical schema remains a conventional third-normal-form EBS table.

Key Information Stored

The table is documented with 12 columns. The most significant are described below.

  • ENROLLMENT_ID — The surrogate primary key, enforced by the unique index OTA_OPEN_FC_ENROLLMENTS_PK. It uniquely identifies each enrollment and is the single business-key candidate documented for this table.
  • FORUM_ID — Foreign key to OTA_FORUMS_B. Identifies the forum offering to which the enrollment applies. Null for enrollments that relate only to a chat.
  • CHAT_ID — Foreign key to OTA_CHATS_B. Identifies the chat offering to which the enrollment applies. Null for enrollments that relate only to a forum.
  • PERSON_ID — The enrolled learner, referencing the person record. This is the primary means of identifying the participant on the person side.
  • CONTACT_ID — Optional contact reference used when enrollment is recorded against a contact rather than an internal person.
  • BUSINESS_GROUP_ID — The HR business group (operating unit) that owns the enrollment. Multi-org/security queries rely on this column.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework (OAF) to detect concurrent updates.
  • CREATED_BY, CREATION_DATE — Standard who-columns recording the creating user and timestamp.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard who-columns recording the most recent modification, its author, and the login session.

The who-columns are the standard EBS audit trail and should be included in any reconciliation or incremental extraction logic.

Common Use Cases and Queries

Typical reporting scenarios include listing all enrollments for a given forum or chat, counting participants per offering, and reconciling enrollments to the underlying learner population.

  • Enrollments for a forum: SELECT e.enrollment_id, e.person_id, e.creation_date FROM ota_open_fc_enrollments e WHERE e.forum_id = :p_forum_id;
  • Enrollments for a chat: similarly filter on e.chat_id.
  • Participant count per offering: SELECT forum_id, COUNT(*) FROM ota_open_fc_enrollments GROUP BY forum_id;
  • Joining to parent offerings: join OTA_FORUMS_B on enrollment.forum_id = forums_b.forum_id and OTA_CHATS_B on enrollment.chat_id = chats_b.chat_id to resolve names and dates.
  • Security-scoped extracts: filter by BUSINESS_GROUP_ID to respect operating-unit security.
  • Incremental feeds: use LAST_UPDATE_DATE as the high-water mark, with OBJECT_VERSION_NUMBER to detect in-flight changes.

Because the row count is relatively modest, this table is generally safe to query directly in operational reporting and can be joined to person and HR views for learner demographics.

Related Objects

  • OTA_FORUMS_B — Parent forum entity; joined via FORUM_ID.
  • OTA_CHATS_B — Parent chat entity; joined via CHAT_ID.
  • OTA_FORUMS_TL and OTA_CHATS_TL — Translation tables providing forum and chat names by language.
  • PER_ALL_PEOPLE_F — Person records for the enrolled learner, joined via PERSON_ID.
  • HR_ALL_ORGANIZATION_UNITS / PER_BUSINESS_GROUPS — Resolves BUSINESS_GROUP_ID to an operating unit name.
  • OTA_OPEN_FC_ENROLLMENTS_PK — The primary key index, used by all lookups on ENROLLMENT_ID.

These relationships make OTA_OPEN_FC_ENROLLMENTS a central link between the chat/forum catalog and the learner population in Learning Management.