Results for “ecx_msg_logs”

44 results




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

Overview

ECX_MSG_LOGS is a core transaction-logging table owned by the ECX schema within the Oracle E-Business Suite XML Gateway module. Its documented purpose is to contain the inbound and outbound message logs generated by the XML Gateway runtime as it processes business documents exchanged between EBS and external trading partners or internal integration endpoints. Every message routed through the XML Gateway — whether arriving from a supplier, customer, or middleware layer, or departing from an EBS application module — leaves a corresponding audit record in this table, making it the principal historical evidence of XML message traffic across the instance.

The table is physically defined with only three documented columns: LOG_ID, TRIGGER_ID, and ERROR_ID. This narrow structure reflects its role as a lightweight pointer or status record rather than a full payload store; the substantive message content and processing detail typically reside in companion ECX objects. Under the heuristic Data Vault classification derived from the foreign-key structure, ECX_MSG_LOGS is modeled as satellite-leaning. This classification is a modeling suggestion: functionally, the table behaves as a descriptive satellite attached to a message or transaction hub, carrying context about a single message event (its trigger origin and any associated error) rather than defining an independent business key of its own.

Key Information Stored

The documented schema of ECX_MSG_LOGS in ETRM 12.2.2 comprises the following significant attributes:

  • LOG_ID — The surrogate primary key of the table, enforced through the ECX_MSG_LOGS_PK constraint and additionally supported by the unique index ECX_MSG_LOGS_U1. This value uniquely identifies each message log entry and is the column used by downstream processes and investigative queries to reference a specific logged message event.
  • TRIGGER_ID — Identifies the trigger or event that caused the message log entry to be created. In XML Gateway terms, this links the log to the mechanism that invoked message processing, allowing analysts to distinguish, for example, messages generated by a specific business event, concurrent program, or inbound transmission path.
  • ERROR_ID — A foreign key to ECX_ERROR_MSGS. When populated, it indicates that the message encounter failed processing and directs the reader to the detailed error description recorded in the referenced error table. A NULL or unset ERROR_ID generally signifies that the message completed without a recorded error.

Because only three columns are documented, the table should be treated as a compact index of message activity. The business-key candidate is LOG_ID (via the unique index ECX_MSG_LOGS_U1), while TRIGGER_ID and ERROR_ID act as relationship-bearing attributes that provide the join paths into the surrounding XML Gateway data model.

Common Use Cases and Queries

Support and integration teams commonly use ECX_MSG_LOGS to reconcile message traffic, investigate failed XML transmissions, and produce operational reporting on inbound and outbound volumes. A typical diagnostic query retrieves all log entries associated with errors and joins them to the error message detail:

  • Querying failed messages: SELECT l.log_id, l.trigger_id, e.* FROM ecx.ecx_msg_logs l, ecx.ecx_error_msgs e WHERE l.error_id = e.error_id;
  • Reviewing activity for a specific trigger: SELECT log_id, error_id FROM ecx.ecx_msg_logs WHERE trigger_id = :p_trigger_id ORDER BY log_id;
  • Counting error versus successful messages by grouping on whether ERROR_ID is NULL.

These patterns support root-cause analysis of interface failures, auditing of partner message exchanges, and periodic reporting on XML Gateway throughput. Since the table is satellite-leaning, it is best joined to its hub (message/trigger) and to ECX_ERROR_MSGS rather than queried in isolation.

Related Objects

The documented foreign-key metadata establishes the primary relationship for this object:

  • ECX_ERROR_MSGS — Referenced through ECX_MSG_LOGS.ERROR_ID; supplies the error text and diagnostics for failed messages and is the most frequent join partner.
  • ECX_MSG_LOGS_PK — The primary-key constraint on LOG_ID.
  • ECX_MSG_LOGS_U1 — The unique index on LOG_ID, serving as the documented business-key candidate.

The TRIGGER_ID column further implies relationships to the XML Gateway transaction/trigger definition objects (for example ECX_TRANSACTIONS and ECX_TRIGGERS) that define what caused each logged message. Together these objects form the reference chain used to interpret any row in ECX_MSG_LOGS.