Search Results ecx_tp_headers

Overview

The ECX_TP_HEADERS table is a core data object within the Oracle E-Business Suite XML Gateway module (ECX). It serves as the master repository for Trading Partner header information, which is fundamental to configuring and executing electronic data interchange (EDI) and XML-based B2B transactions. In the context of Oracle EBS 12.1.1 and 12.2.2, this table stores the primary definition of a trading partner entity—which could be a customer, supplier, or bank—as configured for inbound and outbound document exchanges. Each record acts as a parent header, to which detailed protocol and document-specific setup (stored in related tables like ECX_TP_DETAILS) is linked, enabling the complex routing and transformation of business documents.

Key Information Stored

While the provided metadata does not list all columns, the primary and foreign key relationships reveal the essential data structure. The central column is TP_HEADER_ID, the unique primary key identifier for each trading partner header record. A critical foreign key is PARTY_ID, which links the trading partner to the universal party definition in the HZ_PARTIES table (TCA architecture) and, for suppliers, to the PO_VENDORS table. This linkage integrates XML Gateway setup with the core Oracle Trading Community Architecture and Procurement entities. Other typical columns in this table, based on its function, would include fields for the trading partner name, transaction type, and active status flags, though these are inferred from standard implementation patterns.

Common Use Cases and Queries

This table is primarily accessed for setup, maintenance, and troubleshooting of trading partner connections. Common scenarios include generating a list of all configured trading partners for a specific party, validating the existence of a header before creating detail records, and diagnosing integration failures by tracing the header setup. A frequent query pattern joins ECX_TP_HEADERS to HZ_PARTIES to retrieve a human-readable list:

• SELECT htp.TP_HEADER_ID, hp.PARTY_NAME FROM ECX.ECX_TP_HEADERS htp, APPS.HZ_PARTIES hp WHERE htp.PARTY_ID = hp.PARTY_ID;

Another critical use case involves verifying the complete trading partner setup by joining to ECX_TP_DETAILS to ensure protocol mappings exist for a given header.

Related Objects

The ECX_TP_HEADERS table sits at the top of a hierarchy of related XML Gateway configuration tables, as indicated by its foreign keys. Key dependencies include:

• ECX_TP_DETAILS: Stores the detailed protocol, document, and transformation mappings for each trading partner header (TP_HEADER_ID).
• ECX_XREF_DTL / ECX_XREF_DTL_B: Reference this table for trading partner cross-referencing data.
• HZ_PARTIES: The master source for the trading partner's party definition (PARTY_ID).
• PO_VENDORS: Provides the supplier-specific attributes when the trading partner is a vendor.

These relationships underscore that ECX_TP_HEADERS is the pivotal link between the EBS core party data and the specific technical execution parameters for B2B integration.