Results for “ext_process_id”

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

Overview

ECX_EXT_PROCESSES is the XML Gateway configuration table that holds external transaction definitions within the ECX product module of Oracle E-Business Suite 12.1.1 and 12.2.2. Each row defines an external process — the logical unit that tells the XML Gateway how to receive, validate, and route a specific inbound business document from an external system. Because the XML Gateway is the entry point for inbound transactions such as purchase orders, invoices, and inventory movements arriving over AQ or HTTP, ECX_EXT_PROCESSES effectively acts as the registry of accepted inbound interfaces for the instance. The table resides in the ECX schema with a VALID status and is seeded and maintained through the XML Gateway Define External Processes form rather than by direct DML. In Data Vault terms, the mined foreign-key structure suggests a hub-leaning classification: EXT_PROCESS_ID is a durable business identifier referenced by dependent tables, so the object behaves like a hub whose descriptive attributes could be modelled as an attached satellite.

Key Information Stored

The table is documented with thirteen columns. The surrogate primary key is the EXT_PROCESS_ID column, enforced through ECX_EXT_PROCESSES_PK and the system-generated constraint SYS_C00516354. Two unique indexes provide business-key candidates. ECX_ECX_PROCESSES_U2 covers (EXT_PROCESS_ID, ZD_EDITION_NAME), and ECX_EXT_PROCESSES_U1 covers the multi-column business key (TRANSACTION_ID, STANDARD_ID, DIRECTION, EXT_TYPE, EXT_SUBTYPE, ZD_EDITION_NAME). That five-part key is the practical identity of an external process: a transaction type, its business standard (for example OAG or custom XML), the flow direction, and the external type/subtype classification. QUEUE_NAME records the AQ queue to which incoming messages are enqueued. The audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN track row provenance. ZD_EDITION_NAME is the editioning column introduced with EBS 12.2 online patching, supporting edition-based redefinition.

Common Use Cases and Queries

Typical uses include auditing which external processes are configured for an instance, confirming the queue name used by an inbound interface, and troubleshooting why a transaction is rejected at the gateway. The join to ECX_TP_DETAILS resolves a process to its trading-partner mapping. For example:

• List all processes and queues: SELECT EXT_PROCESS_ID, EXT_TYPE, EXT_SUBTYPE, TRANSACTION_ID, STANDARD_ID, DIRECTION, QUEUE_NAME FROM ECX.ECX_EXT_PROCESSES ORDER BY TRANSACTION_ID;
• Find processes by business key: SELECT EXT_PROCESS_ID, QUEUE_NAME FROM ECX.ECX_EXT_PROCESSES WHERE TRANSACTION_ID = :txn AND STANDARD_ID = :std AND DIRECTION = :dir AND EXT_TYPE = :type;
• Resolve trading-partner mappings: SELECT p.EXT_PROCESS_ID, p.TRANSACTION_ID, d.* FROM ECX.ECX_EXT_PROCESSES p JOIN ECX.ECX_TP_DETAILS d ON d.EXT_PROCESS_ID = p.EXT_PROCESS_ID;
• Edition-aware reporting on 12.2: append WHERE ZD_EDITION_NAME = SYS_CONTEXT('USERENV','DB_EDITION') or filter by edition explicitly.

Related Objects

The most significant dependent object is ECX_TP_DETAILS, which carries the EXT_PROCESS_ID foreign key back to this table and stores trading-partner level configuration for each external process. The primary key index ECX_EXT_PROCESSES_PK and the unique indexes ECX_ECX_PROCESSES_U2 and ECX_EXT_PROCESSES_U1 enforce identity and business-key integrity. The XML Gateway runtime and its concurrent programs consume these definitions when enqueuing and dispatching inbound messages, and the Define External Processes setup form maintains the rows. Additional ECX tables that store transaction type and standard definitions are referenced indirectly through the EXT_TYPE, EXT_SUBTYPE, TRANSACTION_ID, and STANDARD_ID values, making ECX_EXT_PROCESSES the central linking point between gateway configuration, partner mappings, and inbound AQ processing.