Results for “ecx_external_retry”

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

Overview

ECX_EXTERNAL_RETRY is a transactional logging table owned by the ECX schema within the Oracle E-Business Suite XML Gateway module. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, the table stores the outbound logs for messages that have been resent through the XML Gateway messaging infrastructure. When an outbound business event message fails to reach its external destination, the XML Gateway administrator may resend it; each such retry attempt generates a row in this table, giving administrators and support teams an audit trail of remedial delivery actions.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. This suggests the table is best understood as a descriptive satellite attached to a core message or error hub, rather than as an independent hub or a link resolving many-to-many relationships. The table exists primarily to record the circumstances surrounding retry activity, not to define new business entities.

Key Information Stored

The documented physical schema for ECX_EXTERNAL_RETRY in 12.2.2 contains five columns: MSGID, RETRY_MSGID, STATUS, ERROR_ID, and TIME_STAMP. The primary key is enforced by the constraint ECX_EXTERNAL_RETRY_PK over RETRY_MSGID, and a unique index ECX_EXTERNAL_RETRY_U1 also exists on RETRY_MSGID, making this column the single business-key candidate as well as the surrogate identifier.

• RETRY_MSGID — The primary key and unique business-key candidate. This identifier distinguishes each individual retry event from all others in the table.
• MSGID — Identifies the original outbound message whose delivery is being reattempted, linking the retry activity back to the message with which the user is concerned.
• STATUS — Records the state or disposition of the retry attempt, allowing administrators to determine whether the resent message succeeded, failed, or remains pending.
• ERROR_ID — A foreign key referencing ECX_ERROR_MSGS, capturing the error context that prompted the retry. This column is the sole documented foreign key relationship.
• TIME_STAMP — Captures the date and time the retry log entry was created, which is essential for chronological reporting and troubleshooting sequences of events.

Common Use Cases and Queries

The primary use case is troubleshooting outbound XML Gateway integrations. Integration analysts query this table to determine whether a failed outbound message was subsequently resent, when the retry occurred, and whether it succeeded. A typical query joins the retry log to the error message table to present the failure reason alongside the retry outcome:

• SELECT r.RETRY_MSGID, r.MSGID, r.STATUS, r.TIME_STAMP, e.ERROR_ID FROM ECX.ECX_EXTERNAL_RETRY r, ECX.ECX_ERROR_MSGS e WHERE r.ERROR_ID = e.ERROR_ID;
• Filtering by TIME_STAMP to produce a daily or weekly report of resend volume for operational monitoring.
• Grouping by STATUS to measure retry success rates and identify integrations with chronically unreliable endpoints.
• Correlating MSGID values with the originating message tables to trace a business transaction end-to-end.

Related Objects

The documented relationship data identifies one direct dependency: ECX_EXTERNAL_RETRY.ERROR_ID references ECX_ERROR_MSGS. Beyond this, the table participates in the wider XML Gateway message-tracking ecosystem, where the MSGID column logically associates retry records with the original outbound message definitions and their associated delivery logs. Administrative monitoring and troubleshooting within the ECX module typically involves ECX_ERROR_MSGS, the message definition and outbound log tables maintained by the XML Gateway, and the standard concurrent programs that manage outbound message processing and resubmission. These related objects collectively provide the context needed to interpret retry activity recorded in ECX_EXTERNAL_RETRY.