Search Results msg_seq_no




Overview
Explore in AI Chat

Overview

APPS.OKC_QUE_ERROR_TEXT_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It exposes error text information that has been accumulated on the Advanced Queue (AQ) message stack for the Oracle Contracts (OKC) module. In EBS, contract-related operations frequently rely on concurrent programs, bulk processing, and outbound/inbound messaging that leverage Oracle Advanced Queuing. When a queued message fails, diagnostic information is captured and pushed onto an internal message stack. This view provides a simplified, read-only projection of that stack, allowing functional and technical users to inspect error messages associated with queued contract events without querying the raw staging table directly.

Because the view is defined as a straightforward projection with column aliasing, it plays a supporting role in troubleshooting and integration monitoring rather than acting as a transactional interface. Users searching for "message_number" are typically performing diagnostics against queued contract events and require the numeric message identifier alongside the message name and text.

Underlying Base Objects

The view is defined over a single base object, accessed through a synonym: OKC_AQMSGSTACKS. The documented view text is a SELECT statement that reads from OKC_AQMSGSTACKS and renames several columns for clarity:

Because the view is a direct projection with no joins, filters, or aggregations, its content mirrors the rows held in OKC_AQMSGSTACKS at query time. The synonym resolves to the OKC-owned base table in the standard EBS configuration, though the view itself is registered under the APPS schema for consistent access control and cross-module readability.

Key Columns

  • ID (AQE_ID): The unique identifier of the advanced queue error/message record. This is the primary correlation key for a specific stack entry.
  • MSG_SEQ_NO: The sequence number of the message within the stack, indicating ordering of messages as they were enqueued or encountered.
  • MESSAGE_NAME: The symbolic name of the message, corresponding to the message dictionary entry.
  • MESSAGE_NUMBER: The numeric identifier of the message. This is the column retrieved by users who search for "message_number" and is the key used to join to message lookup tables such as FND_NEW_MESSAGES when additional message text or translations are required.
  • MESSAGE_TEXT: The actual error or informational text associated with the queued message, generally the human-readable content surfaced to the end user or support analyst.

Common Use Cases and Queries

Typical scenarios include diagnosing failed contract concurrent programs, verifying outbound message contents, and correlating an error surfaced in the UI with its underlying numeric message identifier. The following examples illustrate common access patterns.

Listing recent queue error messages:

  • SELECT id, msg_seq_no, message_name, message_number, message_text FROM apps.okc_que_error_text_v ORDER BY id, msg_seq_no;

Locating a specific message by its numeric identifier:

  • SELECT id, message_name, message_number, message_text FROM apps.okc_que_error_text_v WHERE message_number = :p_message_number;

Joining to the message repository for translated text:

  • SELECT v.id, v.message_number, v.message_text, m.message_text AS dictionary_text FROM apps.okc_que_error_text_v v, fnd_new_messages m WHERE v.message_number = m.message_number AND m.language_code = USERENV('LANG');

These queries support functional troubleshooting and integration monitoring and should be executed in a read-only fashion given the diagnostic nature of the view.