Results for “message_action_request”

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

Overview

APPS.CS_MESSAGES_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data application CS (Service). Its status is VALID and its view type is documented as Internal, carrying the standard Oracle restriction: "Warning: Oracle Internal Use Only — Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs." The view exposes the message and notification records generated by Oracle Service for service requests and repairs, including sender, receiver, message body, priority, and response tracking. Functionally, it is a read-oriented presentation layer over the CS messaging base tables, used by Service and Depot Repair flows to display and correlate inbound/outbound messages tied to source objects. It is not a public integration endpoint; external systems should not be pointed at it directly.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, CS_MESSAGES_V is defined over the following referenced base objects:

• CS_MESSAGES (referenced via SYNONYM) — the primary base table holding message records.
• CS_LOOKUPS (VIEW) — the Service lookup view, resolved for code meanings such as source object type and action type.
• FND_USER (SYNONYM) — used to resolve Who columns (CREATED_BY, LAST_UPDATED_BY) to user names.
• FND_GLOBAL (PACKAGE) — supplies session context such as user id and login id used in the view logic.

The view therefore joins message header data to lookup and user metadata, and is layered on the same synonymous table used by the Service messaging APIs. Because it relies on FND_GLOBAL, its behaviour is session-dependent, which is consistent with an internal view intended to be called from within concurrent programs and forms.

Key Columns

• MESSAGE_ID, ROW_ID — unique message identifier and rowid from the base table.
• SOURCE_OBJECT_TYPE_CODE / OBJECT_TYPE_CODE — identifies whether the message pertains to a service request or a repair.
• OBJECT_ID, OBJECT_EXT_ID — internal and user-visible identifiers of the source object (e.g., the SR or repair order).
• SENDER, RECEIVER — names of the sending and receiving parties.
• PRIORITY — message priority (VARCHAR2 80).
• MESSAGE — the message body, up to 2000 characters.
• DATE_SENT — date the message was sent.
• RESPONDER, RESPONSE_DATE, RESPONSE, RESPONDER_COMMENT — recipient response tracking.
• ACTION_TYPE — the action the recipient is requested to take.
• EXPAND_ROLES, CONFIRMATION — flags controlling whether messages fan out to all role members and whether a confirmation is returned to the sender.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Who columns.

Common Use Cases and Queries

Typical uses include auditing message traffic for a service request, verifying whether a response was captured, and reporting notification volumes by priority or action type. Because it is an internal view, queries are normally executed with APPS credentials for support and diagnostics rather than from external endpoints.

SELECT message_id,
       sender,
       receiver,
       date_sent,
       priority,
       action_type,
       response,
       response_date
FROM   apps.cs_messages_v
WHERE  object_ext_id = :p_sr_number
ORDER  BY date_sent DESC;

SELECT source_object_type_code,
       priority,
       COUNT(*) msg_count
FROM   apps.cs_messages_v
WHERE  date_sent >= TRUNC(SYSDATE) - 30
GROUP  BY source_object_type_code, priority
ORDER  BY msg_count DESC;

The user-supplied search string appears to reference an external HTTP messaging gateway endpoint (a PHP "sendmsg" utility with OTP parameters). That URI is unrelated to the EBS dictionary object: CS_MESSAGES_V is an internal Service data view and does not expose, or integrate with, any such external HTTP API. Referencing such an endpoint in the context of this view would be a data-source mismatch, and credentials embedded in a URL should be treated as exposed and rotated.