Results for “ecx_transactions”

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

Overview

ECX_TRANSACTIONS is a repository table within the Oracle E-Business Suite XML Gateway module (ECX). It stores internal transaction definitions that describe how the XML Gateway framework processes inbound and outbound business documents. Each row represents a transaction type that the XML Gateway engine uses to map an incoming XML message, such as a purchase order or invoice, to the appropriate Oracle EBS interface or API, and conversely to generate outbound XML payloads from application data.

The ETRM metadata classifies ECX_TRANSACTIONS as standalone using a heuristic Data Vault assessment mined from its foreign key structure. In Data Vault modeling terms, this suggests treating ECX_TRANSACTIONS as a standalone hub-like entity or reference table rather than a link or dependent satellite; the absence of inbound or outbound foreign key relationships implies it functions primarily as a master definition list referenced conceptually by other ECX configuration objects rather than being constrained by them.

Key Information Stored

The metadata documents two primary keys — ECX_TRANSACTIONS_PK and SYS_C00407834 — both defined on the single column TRANSACTION_ID. The surrogate key is therefore TRANSACTION_ID, which uniquely identifies each transaction definition. No alternate unique index or business-key candidate columns are documented in the supplied metadata beyond this primary key constraint.

Transaction definition tables of this class in XML Gateway typically hold attributes that name the transaction, specify its direction (inbound or outbound), and link it to a business event, interface, or document type. In the case of ECX_TRANSACTIONS, the documentation excerpt is minimal and confirms only the TRANSACTION_ID column as the identifying attribute. Other descriptive columns such as transaction short name, display name, direction flag, and status flag are generally present in the full table definition but are not enumerated in the metadata provided and should be validated against the ETRM column listing or the ALL_TAB_COLUMNS data dictionary view before use in custom queries.

Common Use Cases and Queries

ECX_TRANSACTIONS supports configuration, diagnostics, and reporting activities around XML Gateway processing. Typical scenarios include identifying which transaction definitions exist in the instance, troubleshooting an XML message that failed to map to an interface, and auditing which transactions feed a particular outbound integration. A basic query pattern is:

• SELECT transaction_id FROM ecx_transactions WHERE transaction_id = :p_id;
• Join ECX_TRANSACTIONS to ECX-related mapping or parameter tables on TRANSACTION_ID to retrieve processing details.
• Report the full set of defined transactions to confirm coverage of inbound purchase order, invoice, or outbound notification integrations.

Because the metadata does not document descriptive columns beyond TRANSACTION_ID, report authors should first inspect the table definition with a query against ALL_TAB_COLUMNS for owner='ECX' and table_name='ECX_TRANSACTIONS'. This confirms which descriptive attributes are available in the target EBS release (12.1.1 versus 12.2.2) before embedding them in custom concurrent programs or BI Publisher reports.

Related Objects

The metadata states the table is standalone with no documented foreign key relationships to other ECX objects. In practice, ECX_TRANSACTIONS is referenced conceptually by the XML Gateway transaction configuration and mapping components that resolve individual transaction identifiers at runtime. Related objects that commonly depend on or reference the transaction definition include:

• ECX_OUTBOUND_LOGS and ECX_INBOUND_LOGS, which record message processing keyed to a transaction identifier.
• ECX_XML_DOCUMENTS and related XML Gateway mapping tables, which drive message transformation.
• ECX_TRANSACTION_TYPES or similarly named lookup tables, where present in the instance.
• ECX Parameters and ECX_PROFILE_OPTION-style configuration tables that govern XML Gateway behaviour.
• APIs such as ECX_XMLGATEWAY_PKG and ECX_UTL_* packages that consume transaction identifiers during message dispatch.

Because the documented FK relationships are absent, join predicates to these objects must be validated against actual column definitions in the target instance rather than assumed from primary-key structure alone.