Search Results ecx_out_process_vl




Overview
Explore in AI Chat

Overview

ECX_OUT_PROCESS_VL is an APPS-owned database view within the Oracle E-Business Suite XML Gateway (ECX) module. Its documented purpose is to present the Status for Outbound Messages — a consolidated, query-friendly projection of the outbound message lifecycle as processed by the XML Gateway. Rather than requiring report authors and integrators to join the raw logging and retry tables individually, ECX_OUT_PROCESS_VL exposes generation (outbound processing), delivery (external transmission), and retry status in a single row per outbound message, correlated by the internal message identifier OUT_MSGID.

The view is defined with the suffix _VL, which in EBS convention denotes a view whose underlying tables carry MLS (translated) columns; the view selects the language-appropriate values. It occupies the same reporting layer as the other XML Gateway diagnostic views and is commonly used for monitoring, reconciliation, and troubleshooting of outbound transactions such as purchase orders, invoices, and advance ship notices transmitted to trading partners.

Underlying Base Objects

The view text is a UNION of two SELECT statements. The first branch joins ECX_OUTBOUND_LOGS to ECX_EXTERNAL_LOGS, ECX_EXTERNAL_RETRY, ECX_DOCLOGS, and ECX_ERROR_MSGS. The second branch covers the case where an external log exists without a corresponding retry record, supplying NULL placeholders for the retry columns. The documented referenced base objects are:

  • ECX_OUTBOUND_LOGS (OUT) — the driving table, holding generation status, logfile, and the OUT_MSGID key.
  • ECX_EXTERNAL_LOGS (EXT) — external delivery status and timestamp; outer-joined on OUT_MSGID.
  • ECX_EXTERNAL_RETRY (RETRY) — retry status, retry message ID, and retry timestamp; joined on OUT_MSGID.
  • ECX_DOCLOGS (DOC) — protocol type and protocol address for the transmitted document; outer-joined on OUT_MSGID.
  • ECX_ERROR_MSGS (ERR1, ERR2, ERR3) — error message text and parameters for each of the three status streams, outer-joined on ERROR_ID.
  • ECX_TP_HEADERS — trading partner header information referenced by the view's metadata.
  • ECX_DEBUG (PACKAGE) — supplies the ECX_DEBUG.GETMESSAGE function used to format error text and parameters into readable messages.

Key Columns

Common Use Cases and Queries

Typical uses include monitoring outbound interface health, identifying messages that failed generation or delivery, and reviewing retry behavior. A basic status listing by document:

SELECT document_number, transaction_type, generation_status,
       delivery_status, retry_status, delivery_timestamp
FROM   ecx_out_process_vl
WHERE  generation_status = 'ERROR';

Trailing a specific message through all three stages:

SELECT out_msgid, generation_status, delivery_status, retry_status,
       retry_timestamp, protocol_address
FROM   ecx_out_process_vl
WHERE  out_msgid = :p_msg_id;

Reporting on retries for a partner site over a period:

SELECT party_id, party_site_id, transaction_type, retry_status,
       retry_timestamp
FROM   ecx_out_process_vl
WHERE  retry_status IS NOT NULL
AND    retry_timestamp >= :p_from_date;

Because the view formats error text through ECX_DEBUG.GETMESSAGE, the GENERATION_MESSAGE, DELIVERY_MESSAGE, and RETRY_MESSAGE columns return human-readable diagnostics suitable for direct presentation in concurrent program output or BI Publisher reports, without additional decoding logic in the report query.