Results for “time_stamp”

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

Overview

The ECX.ECX_OUTBOUND_LOGS table is a core logging object within the Oracle E-Business Suite XML Gateway module (product code ECX). It stores the audit trail of outbound business transactions processed by the XML Gateway engine, capturing dispatch events generated when Oracle EBS modules publish XML messages to external trading partners, middleware, or integration endpoints. In release 12.1.1 and 12.2.2, the table remains VALID and is owned by the ECX schema.

The table carries a heuristic Data Vault classification of link, inferred from its foreign key topology. Under this modeling suggestion, ECX_OUTBOUND_LOGS functions as an associative record connecting a business party (customer or supplier) to a logged outbound event, rather than as an immutable hub of identities or a descriptive satellite. Each row therefore exhibits transactional, event-oriented behavior, qualifying the table as a fact-like log rather than a master reference.

Key Information Stored

The table contains 13 documented columns. The surrogate primary key is TRIGGER_ID, enforced by constraint ECX_OUTBOUND_LOGS_PK and reinforced by unique index ECX_OUTBOUND_LOGS_U1. TRIGGER_ID is also the strongest documented business-key candidate. The most significant columns include:

• TRIGGER_ID — Surrogate/unique identifier of the outbound log entry.
• TRANSACTION_TYPE — High-level category of the outbound transaction.
• TRANSACTION_SUBTYPE — Further classification within the transaction type.
• PARTY_ID — Foreign key identifying the trading partner; resolves to HZ_PARTIES or PO_VENDORS.
• PARTY_SITE_ID — Site-level identifier for the trading partner location.
• PARTY_TYPE — Indicates whether the party is a customer or supplier context.
• DOCUMENT_NUMBER — Business document number associated with the outbound message.
• PROCESS_ID — Correlation identifier for the processing run.
• STATUS — Outcome state of the outbound dispatch.
• ERROR_ID — Foreign key to ECX_ERROR_MSGS when a failure is recorded.
• OUT_MSGID — Outbound message identifier.
• LOGFILE — Reference to the generated log output.
• TIME_STAMP — Timestamp of the log record.

Common Use Cases and Queries

Typical operational scenarios include reconciliation of outbound messages, delivery failure triage, and partner-volume reporting. A representative query joins the error table:

SELECT l.TRIGGER_ID, l.TRANSACTION_TYPE, l.STATUS, e.ERROR_MESSAGE
FROM   ECX.ECX_OUTBOUND_LOGS l, ECX.ECX_ERROR_MSGS e
WHERE  l.ERROR_ID = e.ERROR_ID
AND    l.TIME_STAMP >= SYSDATE - 7;

Partner-centric reporting uses the party foreign keys:

SELECT l.PARTY_ID, COUNT(*) 
FROM   ECX.ECX_OUTBOUND_LOGS l
WHERE  l.STATUS = 'ERROR'
GROUP BY l.PARTY_ID;

Related Objects

• ECX_ERROR_MSGS — joined via ECX_OUTBOUND_LOGS.ERROR_ID.
• HZ_PARTIES — joined via ECX_OUTBOUND_LOGS.PARTY_ID.
• PO_VENDORS — joined via ECX_OUTBOUND_LOGS.PARTY_ID.
• ECX_OUTBOUND_LOGS_PK / ECX_OUTBOUND_LOGS_U1 — primary key constraint and unique index on TRIGGER_ID.