Search Results ota_frm_notif_subscribers




Overview
Explore in AI Chat

Overview

OTA_FRM_NOTIF_SUBSCRIBERS is a transactional table in the Oracle E-Business Suite Learning Management module (OTA schema). It records the subscription preferences of learners who have opted to receive notifications when another user posts a message or replies within a specific discussion forum. Each row therefore represents a single subscription commitment made by a learner to a thread or forum-level notification feed, forming the operational backbone of forum alerting behavior within Oracle Learning Management.

From a Data Vault modeling perspective, the FK structure suggests this table is satellite-leaning. Its grain is defined by the combination of forum, person, and contact, and its attributes are descriptive and time-stamped, which is characteristic of a satellite entity attached to a hub or link representing the learner-forum relationship. This classification is offered as a heuristic modeling suggestion rather than a documented Oracle construct.

Key Information Stored

The table contains ten documented columns. The business identity of a subscription is captured by the composite unique index OTA_FRM_NOTIF_SUBSCRIBERS_UK1, spanning FORUM_ID, PERSON_ID, and CONTACT_ID. This unique key enforces that a given learner (or learner contact) can subscribe only once to a given forum, preventing duplicate notification records.

  • FORUM_ID — Identifies the discussion forum to which the subscription applies; the primary foreign key reference to OTA_FORUMS_B.
  • PERSON_ID — The learner (person) associated with the subscription; a business-key component of the unique index.
  • CONTACT_ID — The contact record for the learner; part of the composite unique key and relevant where subscriptions are associated with a specific contact identity.
  • BUSINESS_GROUP_ID — Multi-tenant discriminator (operating unit / business group) under which the subscription is created.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/ADF framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE — Audit columns capturing the user and timestamp of record insertion.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent modification and session context.

Common Use Cases and Queries

Typical scenarios include determining which learners are subscribed to a given forum (for notification fan-out), auditing subscription counts per forum, and identifying learners with no active forum notifications. A common query enumerates subscribers for a specific forum:

  • SELECT PERSON_ID, CONTACT_ID FROM OTA.OTA_FRM_NOTIF_SUBSCRIBERS WHERE FORUM_ID = :forum_id;
  • Join to OTA_FORUMS_B to enrich subscriptions with forum names and descriptions.
  • Aggregate counts per FORUM_ID to gauge participation for a reporting dashboard.
  • Filter by BUSINESS_GROUP_ID to scope reports to a single operating unit in multi-org deployments.

Related Objects

The documented foreign key ties FORUM_ID to OTA_FORUMS_B, which holds the base forum definitions. Related notification and messaging objects in the OTA Learning Management schema — such as forum message and reply tables, and person/contact tables in the HR/PER schemas — complete the notification flow. Integration with Oracle Workflow or the Notification Mailer consumes these subscription rows to deliver alerts. The unique index OTA_FRM_NOTIF_SUBSCRIBERS_UK1 is the primary access path when validating subscriber existence prior to insert or delete operations.