Search Results processing_logfile

Overview

ECX_IN_PROCESS_V is a reporting view within the Oracle E-Business Suite XML Gateway module (ECX). Its documented purpose is to expose the status of inbound messages that have entered the XML Gateway processing pipeline. In integration architectures, XML Gateway receives XML business documents from external trading partners, transforms them, and delivers them to Oracle EBS interfaces for processing. Because these messages are processed asynchronously, integration developers and support staff require a means of polling and auditing the state of each inbound message. ECX_IN_PROCESS_V serves that requirement by presenting a consolidated, denormalized snapshot of inbound documents joined to their processing status and any associated error message text.

Although the ETRM metadata records that this view is "Not implemented in this database," the underlying definition and column layout are documented and reflect the standard XML Gateway data model. In a functioning environment the view is a lightweight read-only construct intended for queries and reporting rather than for transactional updates.

Underlying Base Objects

The view is defined over three XML Gateway base tables:

• ECX_DOCLOGS — the document log, holding the header-level attributes of each XML document received or sent, including document number, transaction type, party information, and message identifiers.
• ECX_INBOUND_LOGS — the inbound processing log, holding the runtime status, timestamp, logfile reference, and error identifier for each inbound message.
• ECX_ERROR_MSGS — the error message repository, keyed by ERROR_ID, supplying human-readable message text.

ECX_DOCLOGS is the driving table. ECX_INBOUND_LOGS is joined on MSGID, and ECX_ERROR_MSGS is joined on ERROR_ID. Both joins are outer joins (denoted by the (+) operator), so documents that have not yet generated a processing record or an error entry remain visible in the result set. This outer-join design is significant: it allows the view to report inbound documents that are pending, in process, successful, or failed without dropping rows.

Key Columns

• TRIGGER_ID — the unique identifier of the inbound processing trigger event.
• DOCUMENT_NUMBER and DOCUMENT_ID — identify the XML document being processed.
• TRANSACTION_TYPE and TRANSACTION_SUBTYPE — classify the business document (for example, an order or a receipt).
• PARTY_ID, PARTY_SITE_ID, PARTY_TYPE — identify the trading partner and location that originated the message.
• INTERNAL_CONTROL_NUMBER — a control reference used to correlate the message with internal processing.
• PROCESSING_STATUS (aliased from INT.STATUS) — the central column for the user's search; it conveys the current state of the inbound message.
• PROCESSING_MESSAGE (ERR.MESSAGE) — descriptive error text when the message fails or encounters an exception.
• PROCESSING_TIMESTAMP — when the status was last recorded.
• PROCESSING_LOGFILE — a reference to the logfile holding detailed runtime diagnostics.
• OUT_MSGID and MSGID — message identifiers linking the inbound and any related outbound traffic.

Common Use Cases and Queries

The primary use case is monitoring the inbound XML Gateway queue. Integration teams query the view to find messages that remain in process or that have failed, and support staff use PROCESSING_MESSAGE to triage errors without opening the raw logfiles.

To list all failed inbound messages with their error text:

• SELECT document_number, transaction_type, processing_status, processing_message, processing_timestamp FROM ecx_in_process_v WHERE processing_status = 'ERROR';

To review messages for a specific trading partner:

• SELECT document_number, party_id, processing_status, processing_timestamp FROM ecx_in_process_v WHERE party_id = :party_id ORDER BY processing_timestamp DESC;

To identify long-running or stalled messages, filter on PROCESSING_TIMESTAMP against a threshold and inspect PROCESSING_LOGFILE. Because the view is read-only and built on outer joins, it is safe for ad hoc queries and can be embedded in custom concurrent programs, OAF pages, or BI Publisher reports that surface XML Gateway processing health.