Results for “expand_roles”

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

Overview

CS_MESSAGES is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores information about messages sent from service requests and other documents. It acts as the transactional record of outbound and inbound communications associated with service activity, capturing who sent a message, who received it, its priority and action context, and any response received. The table is owned by the CS schema and is documented as VALID in the ETRM repository, with 25 physical columns.

From a Data Vault modeling perspective, the mined foreign-key structure suggests CS_MESSAGES behaves as a link entity. Its foreign keys—SOURCE_OBJECT_INT_ID referencing CS_INCIDENTS_ALL_B and CSD_REPAIRS, plus SECURITY_GROUP_ID referencing FND_SECURITY_GROUPS—position the table as a connector between service documents and the messaging/notification activity they generate. This is a heuristic classification offered as a modeling suggestion rather than a documented EBS designation.

Key Information Stored

The table’s surrogate primary key is MESSAGE_ID, enforced by the CS_MESSAGES_PK constraint. A unique index, CS_MESSAGES_U1, also exists on MESSAGE_ID, making it the documented business-key candidate for row-level identification.

• MESSAGE_ID — surrogate primary key and unique business-key candidate; the row identifier for each message record.
• SOURCE_OBJECT_TYPE_CODE — identifies the type of document that originated the message (service request, repair order, and so on).
• SOURCE_OBJECT_INT_ID — the internal identifier of the source document; foreign key to CS_INCIDENTS_ALL_B and CSD_REPAIRS.
• SOURCE_OBJECT_EXT_ID — the externally visible document number associated with the source object.
• DATE_SENT — timestamp indicating when the message was dispatched.
• NOTIFICATION_ID — links the message to the notification mechanism that delivered it.
• SENDER / SENDER_ROLE — the party who sent the message and their functional role.
• RECEIVER — the intended recipient of the message.
• PRIORITY — the urgency classification assigned to the message.
• ACTION_CODE — the action or business event that triggered the message.
• MESSAGE — the message body or content text.
• RESPONDER / RESPONSE_DATE / RESPONSE / RESPONDER_COMMENT — the return-communication fields capturing who replied, when, the response content, and any associated comment.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group access partitioning.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework/ADF layer.

Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) provide audit tracking.

Common Use Cases and Queries

Typical uses include auditing communications tied to service requests, tracking response turnaround on notifications, and reporting on message volume and priority by source document type. A representative query joining to the incident source object:

• SELECT m.message_id, m.source_object_type_code, m.date_sent, m.sender, m.receiver, m.priority, m.action_code FROM cs.cs_messages m WHERE m.source_object_int_id = :incident_id ORDER BY m.date_sent DESC; — retrieves the message history for a given service request.
• SELECT m.source_object_type_code, m.action_code, m.priority, COUNT(*) FROM cs.cs_messages m WHERE m.date_sent BETWEEN :start_date AND :end_date GROUP BY m.source_object_type_code, m.action_code, m.priority; — message volume reporting by type and priority.
• Response analysis joining responder fields to measure acknowledgment rates and average response latency using RESPONSE_DATE against DATE_SENT.

Because the table carries SECURITY_GROUP_ID, reporting queries should filter by the appropriate security group to respect multi-org data access rules.

Related Objects

• CS_INCIDENTS_ALL_B — joined via CS_MESSAGES.SOURCE_OBJECT_INT_ID = CS_INCIDENTS_ALL_B.INCIDENT_ID; links messages to service requests.
• CSD_REPAIRS — joined via CS_MESSAGES.SOURCE_OBJECT_INT_ID = CSD_REPAIRS.REPAIR_LINE_ID; links messages to repair orders.
• FND_SECURITY_GROUPS — joined via CS_MESSAGES.SECURITY_GROUP_ID; enforces access partitioning.
• CS_MESSAGES_PK / CS_MESSAGES_U1 — primary key constraint and unique index governing row identity on MESSAGE_ID.
• Notification infrastructure — NOTIFICATION_ID associates each message with the notification delivery record used by Service workflows.

Developers and report authors should treat CS_MESSAGES as the canonical audit trail for service-request messaging, joining through SOURCE_OBJECT_INT_ID to resolve the originating document.