Results for “ecx_inbound_logs”

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

Overview

The ECX_INBOUND_LOGS table is a core logging structure within the Oracle E-Business Suite XML Gateway module (product code ECX). It resides in the ECX schema and holds the inbound transaction logs generated as XML messages are received, validated, and processed by the XML Gateway runtime. In Oracle EBS 12.1.1 and 12.2.2, XML Gateway provides the messaging infrastructure that allows external trading partners and internal applications to exchange business documents—such as purchase orders, invoices, and advanced shipment notices—through a standard XML interface. Every inbound message that traverses this interface is recorded here, making the table the primary audit and diagnostic record for inbound message flow.

The table is a valid, documented object with a defined primary key (ECX_INBOUND_LOGS_PK) on the TRIGGER_ID column. Based on a heuristic Data Vault classification derived from the foreign-key structure, this table is best modeled as a satellite. It records the descriptive and status attributes of inbound processing events around a central trigger identity, with a dependent reference to error information. This classification should be treated as a modeling suggestion rather than a strict architectural requirement.

Key Information Stored

The table contains seven documented columns. The most significant are summarized below.

• TRIGGER_ID — the surrogate primary key and the unique business-key candidate (enforced by unique index ECX_INBOUND_LOGS_U1 and by ECX_INBOUND_LOGS_PK). It uniquely identifies each inbound processing event.
• MSGID — the message identifier associated with the inbound XML document, used to correlate the log entry with the originating message envelope.
• PROCESS_ID — identifies the processing context or transaction run in which the inbound message was handled.
• STATUS — the processing outcome of the inbound message (for example, success, failure, or intermediate state), serving as the primary filter for monitoring queries.
• ERROR_ID — a foreign-key reference to ECX_ERROR_MSGS, populated when processing encounters an error and linking the log entry to its detailed error text.
• LOGFILE — the name or path of the associated log file produced during processing.
• TIME_STAMP — the date and time the log entry was created, supporting chronological ordering and interval reporting.

Common Use Cases and Queries

The table is most frequently used for troubleshooting failed inbound messages, monitoring message volumes, and auditing partner traffic. A typical diagnostic query joins the log to the error message table to retrieve failure detail:

• SELECT l.TRIGGER_ID, l.MSGID, l.STATUS, l.TIME_STAMP, e.* FROM ECX_INBOUND_LOGS l, ECX_ERROR_MSGS e WHERE l.ERROR_ID = e.ERROR_ID AND l.STATUS IS NOT NULL ORDER BY l.TIME_STAMP DESC;
• Filter by time window to measure inbound volumes: WHERE TIME_STAMP BETWEEN :start_date AND :end_date.
• Group by STATUS to produce success-versus-failure summary counts.

These patterns support operational dashboards, SLA monitoring, and reconciliation of messages received against downstream business documents.

Related Objects

• ECX_ERROR_MSGS — referenced through the foreign key ECX_INBOUND_LOGS.ERROR_ID → ECX_ERROR_MSGS, supplying error descriptions and codes.
• Other ECX XML Gateway transaction and transaction-type tables that share the inbound processing framework.
• Concurrent program and log infrastructure that produces the referenced LOGFILE entries.
• Applications that consume the processed inbound document, correlated via MSGID or PROCESS_ID.

Because TRIGGER_ID is the sole documented key, joins to related objects should be driven by ERROR_ID, MSGID, or PROCESS_ID where those identifiers exist in the target object.