Results for “ecx_doclogs”

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

Overview

ECX_DOCLOGS is a core table owned by the ECX (XML Gateway) schema in Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. The table stores the document logs generated for inbound, outbound, and passthrough messages processed by the XML Gateway. Every XML message transacted through the gateway — whether received from an external trading partner, dispatched from EBS to an external system, or passed through without transformation — produces a corresponding log row, making ECX_DOCLOGS the primary audit and diagnostic repository for B2B and application-to-application message traffic.

The table carries a documented physical schema of 64 columns in 12.2.2. Its relationship structure is dense and reference-heavy: the primary key MSGID is referenced by AR_DOCUMENT_TRANSFERS through both CONFIRMATION_MSGID and DOCUMENT_MSGID, and by ECX_EXTERNAL_LOGS through OUT_MSGID, while ECX_DOCLOGS itself holds foreign-key pointers outward. Mined from the FK topology, the heuristic Data Vault classification is hub-leaning, suggesting that MSGID functions as a durable business key around which message lifecycle data is organized; a link or satellite treatment would be appropriate for the referencing relationships and the mutable status/log attributes respectively. This classification should be treated as a modeling suggestion rather than an Oracle-documented designation.

Key Information Stored

The table is anchored by MSGID, the surrogate primary key defined by ECX_DOCLOGS_PK and additionally enforced by unique index ECX_DOCLOGS_U1, which qualifies it as the primary business-key candidate for the message record. The most significant columns include:

• MSGID — unique message identifier; primary key and join key to dependent tables.
• MESSAGE_TYPE, MESSAGE_STANDARD, TRANSACTION_TYPE, TRANSACTION_SUBTYPE — classify the document (for example, the business document category and its XML standard) and drive gateway processing rules.
• DOCUMENT_NUMBER, ITEM_TYPE, ITEM_KEY, ACTIVITY_ID — the business document reference and its originating work item context.
• PARTYID, PARTY_SITE_ID, PARTY_TYPE — the trading partner identity; PARTYID carries foreign keys to both HZ_PARTIES and PO_VENDORS, reflecting the dual customer/supplier partner model.
• PROTOCOL_TYPE, PROTOCOL_ADDRESS, USERNAME, PASSWORD — the transport and authentication details used to exchange the message.
• DIRECTION, STATUS, TIME_STAMP — whether the message was inbound, outbound, or passthrough, its current processing state, and the log timestamp.
• OUT_MSGID — pointer to a related output message, mirroring the ECX_EXTERNAL_LOGS relationship.
• PAYLOAD, LOGFILE — the message content and the associated log file reference.
• EVENT_NAME, EVENT_KEY, ORIG_REFERENCE_ID, CB_EVENT_NAME, CB_EVENT_KEY — business-event and callback correlation data used by workflow and Oracle Event processing.
• BLOCK_MODE, INTERNAL_CONTROL_NUMBER — control flags governing message handling.

Generic ATTRIBUTE1–5 and FIELD1–30 columns provide extensible, DFF-style storage for customer-specific data.

Common Use Cases and Queries

The most frequent operational use is troubleshooting failed or stalled XML Gateway transactions by filtering on STATUS and DIRECTION within a time window:

• SELECT msgid, document_number, status, time_stamp FROM ecx_doclogs WHERE direction = 'IN' AND status <> 'SUCCESS' AND time_stamp > SYSDATE - 1;
• Partner activity reporting via SELECT partyid, COUNT(*) FROM ecx_doclogs GROUP BY partyid, joined to HZ_PARTIES for partner names.
• Message volume and latency trending by TRANSACTION_TYPE and TIME_STAMP, useful for capacity and SLA monitoring.
• Correlating an AR receipt or invoice transfer to its gateway message by joining AR_DOCUMENT_TRANSFERS.CONFIRMATION_MSGID or DOCUMENT_MSGID to ECX_DOCLOGS.MSGID.
• Rediscovering outbound payloads through the OUT_MSGID link to ECX_EXTERNAL_LOGS, or replaying a message using its stored PAYLOAD.
• Audit and compliance extracts that reconcile inbound and outbound message counts against expected trading-partner activity.

Because of the payload and log-file columns, full-table scans should be avoided; queries should filter on MSGID, PARTYID, DOCUMENT_NUMBER, or TIME_STAMP, and selection lists should exclude PAYLOAD unless the content is genuinely required.

Related Objects

The following objects have the most significant documented relationships to ECX_DOCLOGS:

• AR_DOCUMENT_TRANSFERS — references ECX_DOCLOGS twice, via CONFIRMATION_MSGID and DOCUMENT_MSGID; the primary integration point for Receivables document transmission.
• ECX_EXTERNAL_LOGS — references ECX_DOCLOGS through OUT_MSGID, linking gateway messages to their external log entries.
• HZ_PARTIES — target of the ECX_DOCLOGS.PARTYID foreign key; supplies trading-partner identity for customer-side traffic.
• PO_VENDORS — also referenced through ECX_DOCLOGS.PARTYID, supplying supplier identity for procurement-side traffic.
• ECX_DOCLOGS_PK and ECX_DOCLOGS_U1 — the primary key and unique index that enforce MSGID uniqueness and anchor joins from all dependent objects.

Together these relationships position ECX_DOCLOGS as the hub of XML Gateway message tracking, with AR_DOCUMENT_TRANSFERS and ECX_EXTERNAL_LOGS acting as the principal downstream consumers of its MSGID key.