Results for “ecx_tp_headers”

50+ results




Overview
Explore in AI Chat

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

Overview

ECX_TP_HEADERS is a core configuration table within the ECX schema, belonging to the Oracle XML Gateway product in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores Trading Partner header information, which defines the parties authorized to exchange XML business documents with the E-Business Suite through the XML Gateway infrastructure. Each row establishes a trading partner relationship that drives inbound and outbound transaction processing, controlling how documents are validated, transformed, and routed. In a heuristic Data Vault modeling sense, this table leans toward a satellite classification: it holds descriptive attributes about a party or vendor and derives context from the HZ_PARTIES and PO_VENDORS hubs it references via PARTY_ID.

Key Information Stored

The table contains ten documented columns, anchored by the surrogate primary key TP_HEADER_ID, which is enforced by ECX_TP_HEADERS_PK and supported by the unique index ECX_TP_HEADERS_U2. Business-key uniqueness is captured separately by ECX_TP_HEADERS_U1 across the combination of PARTY_ID, PARTY_SITE_ID, and PARTY_TYPE, ensuring a single trading partner header per party, site, and party type.

  • TP_HEADER_ID — surrogate primary key and parent key for all dependent detail and cross-reference rows.
  • PARTY_ID — foreign key identifying the trading partner; references HZ_PARTIES (and conceptually PO_VENDORS for supplier-facing parties).
  • PARTY_TYPE — classifies the trading partner role (for example, customer or supplier), forming part of the business key.
  • PARTY_SITE_ID — the specific party site associated with the header, completing the business-key combination.
  • COMPANY_ADMIN_EMAIL — administrative contact address used for XML Gateway notifications and error handling.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN capture the standard EBS who/when tracking for each trading partner record.

Common Use Cases and Queries

ECX_TP_HEADERS is queried chiefly during trading partner setup and troubleshooting of XML Gateway message flows. A common pattern joins the header to the party and site tables to resolve a partner's identity:

  • SELECT h.tp_header_id, h.party_id, h.party_site_id, h.party_type FROM ecx.ecx_tp_headers h WHERE h.party_id = :party_id; — retrieve all headers for a given party.
  • Joining ECX_TP_DETAILS to enumerate the document-level mappings configured beneath each header.
  • Joining ECX_XREF_DTL to inspect cross-reference (code conversion) mappings scoped to a trading partner.
  • Reporting on COMPANY_ADMIN_EMAIL to audit notification routing across all active partners.
  • Reconciling HZ_PARTIES records that lack a trading partner header, to detect configuration gaps before enabling a document flow.

Related Objects

The object participates in a well-defined referential web documented in the ETRM metadata:

  • HZ_PARTIES — parent hub referenced through ECX_TP_HEADERS.PARTY_ID, providing party identity.
  • PO_VENDORS — alternate reference on PARTY_ID for supplier trading partners.
  • ECX_TP_DETAILS — child table linked by ECX_TP_DETAILS.TP_HEADER_ID; holds trading partner detail (document) configuration.
  • ECX_XREF_DTL — child table linked by ECX_XREF_DTL.TP_HEADER_ID; stores cross-reference detail mappings.
  • ECX_XREF_DTL_B — companion cross-reference child linked by ECX_XREF_DTL_B.TP_HEADER_ID.

Together these objects form the XML Gateway trading partner configuration layer, with ECX_TP_HEADERS acting as the parent header driving all dependent detail and cross-reference records.