Results for “ece_tp_headers_u2”

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

Overview

ECE_TP_HEADERS is a core table within the Oracle e-Commerce Gateway (EC) module, a component of Oracle E-Business Suite available in releases 12.1.1 and 12.2.2. The table stores the trading partner address entity, meaning it holds the header-level definition of each trading party with which the enterprise exchanges electronic business documents, such as EDI purchase orders, invoices, advance ship notices, and remittance advices. In the e-Commerce Gateway data model, this table occupies the master or header position for trading partner configuration: it defines who the partner is, how they are contacted, and how their addresses are structured, while line-level or transactional detail is held elsewhere.

From a Data Vault modeling perspective, the FK relationship structure suggests this table behaves as a hub-leaning entity. It carries a single surrogate primary key (TP_HEADER_ID) and a small set of stable business identifiers, and it is referenced by downstream tables rather than accumulating high-frequency descriptive change on its own. Modelers designing an analytical vault around e-Commerce Gateway data may therefore treat ECE_TP_HEADERS as a hub of trading partner identities, with any address or contact volatility optionally split into a satellite.

Key Information Stored

The table is owned by the EC schema and, as documented in the ETRM 12.2.2 physical schema, contains 46 columns. The most significant are summarized below.

• TP_HEADER_ID — the surrogate primary key, enforced by ECE_TP_HEADERS_PK and also exposed through unique index ECE_TP_HEADERS_U1. This is the identifier referenced by child tables.
• TP_CODE and TP_GROUP_ID — the business-key candidate, enforced by unique index ECE_TP_HEADERS_U2. Together they identify a trading partner code uniquely within its trading partner group.
• TP_GROUP_ID — foreign key to ECE_TP_GROUP, placing the partner within a defined group of trading partners.
• ORG_ID — operating unit context, supporting multi-org partitioning of trading partner definitions.
• TP_DESCRIPTION — the descriptive name of the trading partner.
• TP_REFERENCE_EXT1 and TP_REFERENCE_EXT2 — extended reference attributes for partner-specific identifiers.
• TP_CONTACT_NAME and TP_CONTACT_JOB_TITLE — primary contact details for the partner.
• ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, CITY, STATE, PROVINCE, COUNTRY, POSTAL_CODE — the structured mailing address of the trading partner.
• PHONE, FAX, EMAIL — communication channels associated with the partner.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle flexfield column set for descriptive, context-sensitive extensions.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns capturing the process that last wrote the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO-column audit trail.

Common Use Cases and Queries

Typical uses include listing configured trading partners for an operating unit, validating that an inbound or outbound EDI document maps to a known partner, and reporting partner contact and address information for compliance or logistics purposes.

A representative query joins the header to its group and child detail records:

• SELECT h.tp_code, h.tp_description, h.city, h.country, g.group_name FROM ece_tp_headers h, ece_tp_group g WHERE h.tp_group_id = g.tp_group_id AND h.org_id = :org_id;
• SELECT h.tp_code, d.* FROM ece_tp_headers h, ece_tp_details d WHERE h.tp_header_id = d.tp_header_id;

Reporting scenarios commonly group partners by country or group, or expose the flexfield attributes for integration with downstream master data systems.

Related Objects

The FK metadata identifies the principal relationships surrounding this table.

• ECE_TP_GROUP — referenced via ECE_TP_HEADERS.TP_GROUP_ID; the parent grouping of trading partners.
• ECE_TP_DETAILS — child table referencing ECE_TP_HEADERS.TP_HEADER_ID, holding line-level trading partner detail.
• AP_BANK_BRANCHES — references ECE_TP_HEADERS.TP_HEADER_ID, linking bank branch records to trading partner headers for payment-related EDI flows.

These three objects constitute the primary join surface for ECE_TP_HEADERS, with ECE_TP_GROUP providing group context and ECE_TP_DETAILS and AP_BANK_BRANCHES depending on the header identity for their own configuration and transaction processing.