Search Results message_id_1




Overview
Explore in AI Chat

Overview

The CS_FORUM_MSG_MSGS table is a Service (CS) module data object in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores forum message messages. It resides in the CS schema and is documented with a VALID status in the ETRM repository. The table functions primarily as a resolution or linkage entity that associates two forum messages, most commonly representing a reply-to-thread or parent-child relationship between message records. Administrators and developers encounter this object when diagnosing threaded discussion structures in Oracle Service forums, when reconciling forum content to its underlying message base, or when building reports on customer service collaboration activity.

Based on the heuristic Data Vault classification mined from the foreign key structure, the object is best modeled as a link. The table carries no natural descriptive attributes beyond its standard who-columns and the flexible attribute set, and its two foreign keys both point to CS_FORUM_MESSAGES_B, which strongly suggests a many-to-many or parent-child junction pattern. This classification is a modeling suggestion rather than a documented Oracle designation.

Key Information Stored

The table contains 24 documented columns. The most significant are the composite identifiers, audit columns, and the standard OLTP flex and security fields:

The surrogate structure is composite: the primary key is defined as CS_FORUM_MSG_MSGS_PK (MESSAGE_ID_1, MESSAGE_ID_2). A unique index, CS_FORUM_MSG_MSGS_U1 (MESSAGE_ID_1, MESSAGE_ID_2), mirrors the primary key and represents the business-key candidate. There is no single-column surrogate key; identity is derived entirely from the pairing of the two message identifiers.

Common Use Cases and Queries

Typical uses include retrieving all messages linked to a given forum message, tracing reply structures, and auditing forum activity by security group. A representative join pattern resolves both ends of the linkage against the base message table:

  • Find linked messages: SELECT m1.SUBJECT, m2.SUBJECT FROM CS_FORUM_MSG_MSGS l JOIN CS_FORUM_MESSAGES_B m1 ON m1.MESSAGE_ID = l.MESSAGE_ID_1 JOIN CS_FORUM_MESSAGES_B m2 ON m2.MESSAGE_ID = l.MESSAGE_ID_2;
  • Count links per message: SELECT MESSAGE_ID_1, COUNT(*) FROM CS_FORUM_MSG_MSGS GROUP BY MESSAGE_ID_1;
  • Security-scoped extract: add WHERE SECURITY_GROUP_ID = :p_security_group_id to any query to enforce org isolation.

Reporting scenarios include forum thread analytics, service-request resolution tracking, and reconciliation of forum content against source messages. Concurrency programs and DFF-driven extracts can query ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Related Objects

The following objects are the most significant dependencies and join partners:

  • CS_FORUM_MESSAGES_B — Referenced twice, via MESSAGE_ID_1 and MESSAGE_ID_2; the primary join target.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs access partitioning.
  • CS_FORUM_MESSAGES_TL — Translation table typically joined through CS_FORUM_MESSAGES_B for display text.
  • CS_FORUM_B — Parent forum definition, joined indirectly through CS_FORUM_MESSAGES_B.
  • FND_FLEX_VALUES / FND_FLEX_VALUES_TL — Standard lookup targets for ATTRIBUTE segment values.
  • FND_USER — Resolves CREATED_BY and LAST_UPDATED_BY to user identities.

These relationships should be confirmed against the current instance, as additional views and API layers may reference this table.