Results for “message_parameters”

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

Overview

ECX_ERROR_MSGS is a table in the ECX schema (XML Gateway product) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the error messages generated during XML Gateway transaction processing, serving as a centralized repository of diagnostic text that is referenced by the various log and retry tables in the ECX module. When an inbound or outbound XML transaction fails — whether due to mapping errors, document validation failures, connectivity issues, or processing exceptions — a corresponding error record is typically written to this table and referenced by the affected transaction log.

Based on its foreign key topology, the ETRM metadata classifies ECX_ERROR_MSGS as hub-leaning under a heuristic Data Vault model. This reflects that five separate ECX tables reference its primary key, making it a natural reference or lookup hub for error information. Note that this classification is a modeling suggestion derived from FK structure rather than an Oracle-documented designation; treat it as a guide for analytical modeling rather than a physical design fact.

Key Information Stored

The documented physical schema (ETRM 12.2.2) contains three columns: ERROR_ID, MESSAGE, and MESSAGE_PARAMETERS. The table is small in column count but referenced heavily by the transaction subsystem, so understanding each column is essential.

• ERROR_ID — The surrogate primary key of the table, enforced by the unique index ECX_ERROR_MSGS_PK. It is also the business-key candidate (the unique index ECX_ERROR_MSGS_U1 is defined on the same column). Every error record is uniquely identified by this value, and it is the column propagated as a foreign key into the logging tables.
• MESSAGE — The error message text itself. In Oracle EBS messaging conventions this typically holds either the message name or a message skeleton used with token substitution.
• MESSAGE_PARAMETERS — The parameter values substituted into the message template when the message is rendered or displayed. This permits a single message definition to be reused across multiple transactions with different contextual details (document number, trading partner, stack detail, and so on).

No additional columns are documented for this table in the ETRM metadata, and there is no ORG_ID or multi-org column, which is consistent with ECX Gateway tables being non-org-specific.

Common Use Cases and Queries

The predominant use case is troubleshooting failed XML Gateway transactions. Because ECX_INBOUND_LOGS, ECX_OUTBOUND_LOGS, ECX_EXTERNAL_LOGS, ECX_EXTERNAL_RETRY, and ECX_MSG_LOGS all carry ERROR_ID, a support analyst can pull the failure reason for any transaction log entry by joining back to this table.

A representative query for inbound failures:

• SELECT l.MSG_ID, l.ERROR_ID, e.MESSAGE, e.MESSAGE_PARAMETERS FROM ECX_INBOUND_LOGS l, ECX_ERROR_MSGS e WHERE l.ERROR_ID = e.ERROR_ID AND l.STATUS = 'ERROR';

For outbound processing, the equivalent join uses ECX_OUTBOUND_LOGS. For retry analysis, join ECX_EXTERNAL_RETRY to ECX_ERROR_MSGS on ERROR_ID to determine why messages are being reprocessed. Reporting scenarios include aggregating error frequency by MESSAGE to identify the most common failure causes, and auditing error history over a date range by combining this table with the timestamp columns of the referencing log tables.

Related Objects

The following tables reference ECX_ERROR_MSGS through the ERROR_ID foreign key and are the most significant related objects:

• ECX_INBOUND_LOGS — Inbound transaction log; references ECX_ERROR_MSGS.ERROR_ID for inbound processing failures.
• ECX_OUTBOUND_LOGS — Outbound transaction log; references ECX_ERROR_MSGS.ERROR_ID for outbound processing failures.
• ECX_EXTERNAL_LOGS — Log for externally initiated or exchanged messages; references ECX_ERROR_MSGS.ERROR_ID.
• ECX_EXTERNAL_RETRY — Retry tracking for external transactions; references ECX_ERROR_MSGS.ERROR_ID.
• ECX_MSG_LOGS — General message log; references ECX_ERROR_MSGS.ERROR_ID.

The primary key index ECX_ERROR_MSGS_PK and the unique index ECX_ERROR_MSGS_U1 both anchor on ERROR_ID, so any query filtering by that column benefits from index access. Together these objects form the diagnostic backbone of the XML Gateway, with ECX_ERROR_MSGS acting as the shared reference hub for error text across all transaction directions.