Results for “ota_chats_b_pk”

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

Overview

OTA_CHATS_B is the base table for the chat feature within the Oracle E-Business Suite Learning Management module (OTA). It stores the definitional header records for chat sessions, which are used to support online, real-time communication between one or more users. Chats may be associated with a category or class, positioning the table as a scheduling and configuration anchor for interactive learning events. The table resides in the OTA schema and is documented as VALID in both EBS 12.1.1 and 12.2.2.

Based on the foreign key topology, the heuristic Data Vault classification for this object is hub-leaning. This suggests a modeling approach in which OTA_CHATS_B functions as a central hub keyed by CHAT_ID, with dependent transactional and descriptive detail distributed to satellite and link tables such as OTA_CHATS_TL (translations), OTA_CHAT_MESSAGES (message content), and OTA_OPEN_FC_ENROLLMENTS (learner association). This classification is a modeling suggestion derived from the referential structure, not a mandated design.

Key Information Stored

The table contains fourteen documented columns. The most significant are:

• CHAT_ID — Surrogate primary key and the sole unique index (OTA_CHATS_B_PK). It uniquely identifies each chat definition and is the join column referenced by all dependent tables.
• BUSINESS_GROUP_ID — Multi-organization / business group discriminator that scopes rows to an operating unit or HR business group context.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF framework to detect concurrent updates.
• PUBLIC_FLAG — Indicates whether the chat is publicly accessible or restricted.
• START_DATE_ACTIVE and END_DATE_ACTIVE — The date range during which the chat is active and available.
• START_TIME_ACTIVE and END_TIME_ACTIVE — The intra-day active window for the chat session.
• TIMEZONE_CODE — Time zone governing the active date and time boundaries.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking record provenance and modification history.

Only CHAT_ID is documented as a unique index, so it is the sole business-key candidate at the base-table level; descriptive business identifiers are held in the translation table.

Common Use Cases and Queries

Typical uses include listing active chats for a class, auditing chat configuration, and reporting on chat schedules. A representative query retrieves currently active chats within a business group:

• Join OTA_CHATS_B to OTA_CHATS_TL on CHAT_ID to obtain display names and descriptions in the desired language.
• Filter on START_DATE_ACTIVE, END_DATE_ACTIVE, START_TIME_ACTIVE, and END_TIME_ACTIVE relative to SYSDATE, adjusting for TIMEZONE_CODE, to identify live or upcoming sessions.
• Filter on PUBLIC_FLAG to separate public from restricted chats.
• Aggregate OTA_CHAT_MESSAGES rows grouped by CHAT_ID to measure participation volume.
• Join to OTA_OPEN_FC_ENROLLMENTS on CHAT_ID to correlate chats with open flexible-credit enrollments.

Related Objects

The following objects reference OTA_CHATS_B via CHAT_ID and represent its principal dependencies:

• OTA_CHATS_TL — Translation table holding language-specific chat names and descriptions; joined on CHAT_ID.
• OTA_CHAT_MESSAGES — Stores individual chat messages; joined on CHAT_ID.
• OTA_OPEN_FC_ENROLLMENTS — Associates chats with open enrollment records; joined on CHAT_ID.
• OTA_EVENT_ASSOCIATIONS — Links chats to events; joined on CHAT_ID.

Together these tables form the chat subsystem within Learning Management, with OTA_CHATS_B acting as the central definitional anchor.