Results for “ota_chat_users”

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

Overview

OTA_CHAT_USERS is a transactional table in the Oracle E-Business Suite Learning Management (OTA) product module. As its name and ETRM description indicate, the table records the participants who have joined a chat session — most commonly a live, instructor-led or collaborative learning event delivered through Oracle iLearning / Oracle Learning Management. Each row represents a single participation record linking a chat instance to the person and contact who joined it, and it also captures the login moment through the LOGIN_DATE column.

The table resides in the OTA schema and is documented as VALID in ETRM for both 12.1.1 and 12.2.2. The documented physical schema lists 11 columns and one unique index, OTA_CHAT_USERS_UK1, defined on the combination of CHAT_ID, PERSON_ID, and CONTACT_ID. This composite business key enforces the rule that a given person and contact can appear at most once per chat.

From a Data Vault modeling perspective, the metadata's heuristic classification is standalone. Based on the FK-derived structure, OTA_CHAT_USERS behaves primarily as a link-style association between a chat entity and a person/contact identity, with LOGIN_DATE and the standard audit columns functioning as satellite-style descriptive attributes. This classification is offered as a modeling suggestion rather than a documented architectural fact.

Key Information Stored

The most significant columns, drawn exclusively from the documented schema, are as follows.

• CHAT_ID — Identifier of the chat session. Part of the composite unique key and the primary linkage to the chat activity.
• PERSON_ID — Identifier of the person (learner, instructor, or participant) who joined the chat. Part of the composite unique key.
• CONTACT_ID — Identifier of the contact associated with the participant. Part of the composite unique key.
• BUSINESS_GROUP_ID — Operating unit / business group context, supporting multi-org data segregation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OTA framework to prevent concurrent-update conflicts.
• LOGIN_DATE — The timestamp at which the participant joined (logged into) the chat, the principal business fact of this table.
• CREATED_BY, CREATION_DATE — Standard audit columns recording the creating user and creation timestamp.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification details and the login under which it occurred.

There is no separate single-column surrogate primary key documented; the unique constraint OTA_CHAT_USERS_UK1 (CHAT_ID, PERSON_ID, CONTACT_ID) serves as the business-key candidate that uniquely identifies each participation row.

Common Use Cases and Queries

Typical uses include chat attendance reporting, instructor participation tracking, and auditing of collaborative learning sessions. A common query lists all participants for a given chat:

• SELECT PERSON_ID, CONTACT_ID, LOGIN_DATE FROM OTA_CHAT_USERS WHERE CHAT_ID = :chat_id ORDER BY LOGIN_DATE;
• Counting distinct participants per chat, useful for attendance metrics: SELECT CHAT_ID, COUNT(DISTINCT PERSON_ID) FROM OTA_CHAT_USERS GROUP BY CHAT_ID;
• Joining to person or contact master data (via PERSON_ID / CONTACT_ID) to report participant names and demographics.
• Filtering by BUSINESS_GROUP_ID to scope reporting to a specific operating unit.
• Using CREATION_DATE or LAST_UPDATE_DATE for reconciliation, incremental extracts, and audit trails.

Related Objects

The documented relationship data classifies OTA_CHAT_USERS as standalone, so no explicit FK relationships were mined. Based on the columns present, the most significant related objects are:

• OTA chat/session definition tables, joined on CHAT_ID, which define the chat occurrence.
• Person and contact master tables in the Oracle HR / TCA model, joined on PERSON_ID and CONTACT_ID, resolving participant identity.
• Business group / operating unit setup entities, joined on BUSINESS_GROUP_ID.
• Other OTA Learning Management activity tables that share the same audit and OBJECT_VERSION_NUMBER conventions.
• OTA public views and the Learning Management concurrent programs and APIs that consume participant records for attendance reporting.