Search Results source_object

Overview

CS_MESSAGES_V is a Service (CS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents "all messages and their corresponding attributes," consolidating the transactional message records held in CS_MESSAGES with decoded lookup values and user attribution. The view is a reporting and integration convenience layer: rather than joining the base message table to multiple lookup views and FND_USER at query time, consumers can select directly from CS_MESSAGES_V to retrieve human-readable classifications and the identity of the user who created each message.

The view is important because message records in the Service module are stored with coded values for action, priority, response, and source object type. CS_MESSAGES_V resolves these codes into meaningful descriptions, so it is well suited to operational dashboards, escalation reports, and outbound integration extracts that require legible message context without embedding lookup logic in each query.

Underlying Base Objects

The documented metadata identifies four referenced base objects: CS_MESSAGES (SYNONYM, resolving to the physical message table), CS_LOOKUPS (VIEW), FND_USER (SYNONYM), and the FND_GLOBAL package. The view text joins CS_MESSAGES to four aliased instances of CS_LOOKUPS (CSLK1 through CSLK4), each filtered on a distinct LOOKUP_TYPE, and to FND_USER (aliased USR) on the condition MSG.CREATED_BY = USR.USER_ID.

All lookup joins are outer joins (indicated by the (+) operator), meaning a message row is never dropped when a corresponding lookup entry is missing; the decoded column simply returns null. The join to FND_USER is an inner join, so only messages whose CREATED_BY value resolves to a valid FND_USER record are returned. The ROWID of the base CS_MESSAGES row is exposed as ROW_ID.

Key Columns

• MESSAGE_ID — Primary identifier of the message record.
• ROW_ID — ROWID of the underlying CS_MESSAGES row.
• OBJECT_ID / OBJECT_EXT_ID / OBJECT_TYPE_CODE / SOURCE_OBJECT — Internal and external identifiers and decoded type of the source business object the message relates to.
• SENDER / RECEIVER — Parties to the message.
• PRIORITY — Decoded from MESSAGE_PRIORITY lookup.
• ACTION_TYPE — Decoded from MESSAGE_ACTION_REQUEST lookup.
• RESPONSE / RESPONDER / RESPONSE_DATE / RESPONDER_COMMENT — Response details, with RESPONSE decoded from MESSAGE_RESPONSE lookup.
• ENTERED_BY — The FND_USER.USER_NAME of the user recorded in CS_MESSAGES.CREATED_BY. This is the column most commonly used when searching for "entered_by," since it returns the display user name rather than the numeric CREATED_BY identifier.
• DATE_SENT, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit and timing columns.
• EXPAND_ROLES, CONFIRMATION, MESSAGE — Message body and behavioral flags.

Common Use Cases and Queries

A frequent requirement is to identify the user who entered a given message. Because the view exposes ENTERED_BY as a user name, filtering on it is straightforward:

• SELECT MESSAGE_ID, ENTERED_BY, DATE_SENT, PRIORITY, ACTION_TYPE FROM CS_MESSAGES_V WHERE ENTERED_BY = 'OPERATIONS_USER';

Reporting on outstanding or responded messages by priority is equally common:

• SELECT MESSAGE_ID, OBJECT_TYPE_CODE, PRIORITY, RESPONSE, RESPONSE_DATE FROM CS_MESSAGES_V WHERE RESPONSE IS NULL ORDER BY PRIORITY;

For integration extracts, selections keyed on the source object provide correlated message histories:

• SELECT OBJECT_ID, OBJECT_EXT_ID, MESSAGE, ENTERED_BY FROM CS_MESSAGES_V WHERE OBJECT_EXT_ID = :ext_object_id;

Because the view performs the lookup decoding and user join internally, these queries remain concise and consistent across 12.1.1 and 12.2.2, where the documented object metadata is unchanged.