Results for “error_text”

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

Overview

OKC_QUE_ERROR_TEXT_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Contracts Core (OKC) module. It exposes message-stack error information generated by the Contracts Core concurrent and workflow processing infrastructure, presenting a simplified, denormalized projection of the underlying message table. The view's purpose is to provide a stable, query-friendly interface for retrieving diagnostic text associated with queued message errors, allowing developers, support analysts, and integration specialists to identify and troubleshoot message processing failures without navigating the raw base table directly.

Because the object is defined as a VIEW and carries a VALID status in the ETRM 12.2.2 metadata, it is treated as a supported, referenceable object rather than a transient construct. The view surfaces message identifiers, sequence numbers, message names and numbers, and the human-readable error text in a single flat result set, which makes it suitable for ad hoc querying, diagnostics, and lightweight reporting against Contracts Core messaging activity.

Underlying Base Objects

The view is defined over a single documented base object: OKC_AQMSGSTACKS, referenced through a synonym. OKC_AQMSGSTACKS functions as the message-stack repository for Contracts Core, capturing entries as messages are pushed onto or processed from the application queue. The view performs a column-selection projection over this table, mapping the internal column names to consumer-friendly aliases.

No joins to other tables are documented; the view is a straightforward SELECT over the base object with column renaming only. This one-to-one relationship means row counts and filtering behavior in the view mirror the base table, and the view inherits any data retention or purge characteristics applied to OKC_AQMSGSTACKS.

Key Columns

• ID — Aliased from AQE_ID; the unique identifier of the message-stack entry. Serves as the primary correlation key for a specific error record.
• MSG_SEQ_NO — Sequence number of the message within the stack, indicating ordering of messages as they were enqueued or processed.
• MESSAGE_NAME — The internal name of the message, used to distinguish message types in the queue-processing framework.
• MESSAGE_NUMBER — The numeric identifier associated with the message, typically corresponding to an Oracle message dictionary number for lookup and translation.
• ERROR_TEXT — The human-readable message text. Note the ETRM column listing names this column ERROR_TEXT even though the view text aliases MESSAGE_TEXT; in practice both refer to the rendered error content that support personnel read directly.

Common Use Cases and Queries

Typical usage centers on diagnosing failures in Contracts Core message processing. A support analyst might list the most recent errors by descending message sequence number, or filter by MESSAGE_NAME to isolate a specific message type.

Example — retrieve the latest error entries:

• SELECT id, msg_seq_no, message_name, message_number, error_text FROM okc_que_error_text_v ORDER BY msg_seq_no DESC;

Example — target a specific message type:

• SELECT id, msg_seq_no, error_text FROM okc_que_error_text_v WHERE message_name = :p_message_name ORDER BY msg_seq_no;

Example — correlate an entry back to its base record:

• SELECT v.id, v.error_text FROM okc_que_error_text_v v WHERE v.id = :p_aqe_id;

Because the view is read-only in nature and inherits base-table access, queries should apply appropriate filters to avoid full scans of message-stack history. Ensure the executing responsibility has access to the APPS-owned object and that standard EBS security and audit practices are observed.