Results for “ecx_out_process_v”

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

Overview

The view ECX_OUT_PROCESS_V belongs to the XML Gateway (ECX) module of Oracle E-Business Suite and exposes the end-to-end processing status of outbound XML messages. Within the ETRM documentation it is titled "Status for Outbound Messages," reflecting its role as a consolidated diagnostic and reporting surface for the disposition of messages generated by the XML Gateway engine. The view joins the outbound generation log, the external delivery log, and the external retry log, so that a single row presents the lifecycle of an outbound transaction from generation through delivery and, where applicable, retry.

The view is especially relevant to users who search on retry_status. Because the retry attempt is logged separately from the original dispatch, administrators and support analysts frequently need to determine whether a message that failed delivery has been retried, and with what result. ECX_OUT_PROCESS_V surfaces that information directly through the RETRY_STATUS, RETRY_MESSAGE, and RETRY_TIMESTAMP columns, alongside the parallel generation and delivery columns.

Underlying Base Objects

The view is defined over six tables using outer joins so that a row is retained even when a particular stage (delivery or retry) has not occurred:

• ECX_OUTBOUND_LOGS (aliased OUT) — the primary outbound message log, supplying the trigger identifier, document reference, transaction classification, party information, generation status, and the outbound message ID (OUT_MSGID).
• ECX_EXTERNAL_LOGS (aliased EXT) — records the external delivery attempt, joined on OUT_MSGID, providing delivery status and timestamp.
• ECX_EXTERNAL_RETRY (aliased RETRY) — records retry attempts against the outbound message, joined on MSGID = OUT_MSGID, providing retry status, error reference, and timestamp.
• ECX_ERROR_MSGS (aliased ERR1, ERR2, ERR3) — the error message repository, joined by ERROR_ID to each of the three preceding logs to resolve human-readable error text for the generation, delivery, and retry stages respectively.

All error-message joins are outer joins (ERROR_ID(+)), so messages without a recorded error still appear in the result set. The documented metadata lists no implemented base objects for this database instance; the view text nonetheless confirms the dependencies above.

Key Columns

• TRIGGER_ID — identifier of the XML Gateway transaction trigger that produced the message.
• DOCUMENT_ID / DOCUMENT_NUMBER — the source business document that generated the outbound message.
• TRANSACTION_TYPE, TRANSACTION_SUBTYPE — classification of the outbound transaction.
• PARTY_ID, PARTY_SITE_ID — the trading partner and site to which the message is addressed.
• GENERATION_STATUS, GENERATION_MESSAGE, GENERATION_TIMESTAMP, GENERATION_LOGFILE — outcome of XML generation, including the logfile location for troubleshooting.
• OUT_MSGID — the outbound message identifier used to correlate the delivery and retry records.
• DELIVERY_STATUS, DELIVERY_MESSAGE, DELIVERY_TIMESTAMP — outcome of the external transport attempt.
• RETRY_STATUS, RETRY_MESSAGE, RETRY_TIMESTAMP — the retry state, resolved error text, and retry time; these are the columns most commonly queried when diagnosing repeat failures.

Common Use Cases and Queries

The most frequent use case is identifying outbound messages whose retry has not resolved a delivery failure, or whose retry status is still pending or errored. A representative query is:

• SELECT DOCUMENT_NUMBER, TRANSACTION_TYPE, GENERATION_STATUS, DELIVERY_STATUS, RETRY_STATUS, RETRY_MESSAGE, RETRY_TIMESTAMP FROM ECX_OUT_PROCESS_V WHERE RETRY_STATUS IS NOT NULL AND RETRY_STATUS <> 'SUCCESS';
• SELECT TRIGGER_ID, OUT_MSGID, DELIVERY_STATUS, RETRY_STATUS FROM ECX_OUT_PROCESS_V WHERE DELIVERY_STATUS = 'ERROR' OR RETRY_STATUS = 'ERROR';
• SELECT PARTY_ID, COUNT(*) FROM ECX_OUT_PROCESS_V GROUP BY PARTY_ID; to profile outbound volume by trading partner.

Because generation, delivery, and retry statuses are colocated, the view is also suited to operational dashboards and reconciliation reports that compare the state of every outbound message across all three stages.