Search Results ecx_tp_details

Overview

The ECX_TP_DETAILS table is a core data repository within the Oracle E-Business Suite (EBS) XML Gateway (ECX) module, present in both the 12.1.1 and 12.2.2 versions. It functions as the central table for storing detailed configuration and execution parameters for trading partner transactions. While the ECX_TP_HEADERS table defines the primary trading partner relationship, ECX_TP_DETAILS holds the specific, actionable instructions that govern how individual document types (e.g., purchase orders, invoices) are processed, transformed, and transmitted for a given partner. Its role is critical in enabling the automated, bidirectional exchange of business documents between Oracle EBS and external entities.

Key Information Stored

The table's primary key is TP_DETAIL_ID, a unique identifier for each trading partner detail record. Its structure is defined by a network of foreign key relationships that link it to other essential ECX configuration tables. The most significant columns include TP_HEADER_ID, which ties the detail record to its parent definition in ECX_TP_HEADERS. The MAP_ID column references the ECX_MAPPINGS table, specifying the transformation map to apply to the document payload. The EXT_PROCESS_ID links to ECX_EXT_PROCESSES, identifying any external program to execute during processing. Furthermore, the HUB_USER_ID connects to ECX_HUB_USERS for authentication, and the ROUTING_ID supports hierarchical routing configurations through a self-referencing foreign key within the same table.

Common Use Cases and Queries

This table is primarily queried for troubleshooting, auditing, and reporting on trading partner setups. A common scenario involves diagnosing document transmission failures by examining the detailed configuration for a specific partner and document type. Administrators often run queries to list all configured details for a trading partner or to verify mapping assignments. A typical SQL pattern retrieves detail records along with descriptive information from related tables:

• SELECT d.tp_detail_id, h.tp_code, d.map_id, m.map_code FROM ecx_tp_details d, ecx_tp_headers h, ecx_mappings m WHERE d.tp_header_id = h.tp_header_id AND d.map_id = m.map_id(+) AND h.tp_code = '&PARTNER_CODE';

Another critical use case is during the cloning or migration of trading partner configurations from one instance to another, where data from ECX_TP_DETAILS must be extracted and applied consistently.

Related Objects

ECX_TP_DETAILS is a central hub within the XML Gateway schema, with dependencies to several key configuration tables, as documented in its foreign keys. The primary parent table is ECX_TP_HEADERS. It also has mandatory relationships with ECX_MAPPINGS (for data transformation logic) and ECX_EXT_PROCESSES (for external execution). The link to ECX_HUB_USERS manages security credentials for document exchange hubs. The table's self-referencing foreign key on ROUTING_ID enables complex routing rule chains. Consequently, this table is frequently joined with these objects in operational views and supporting APIs that manage the lifecycle of XML Gateway transactions.