Search Results ece_address_tp

Overview

ECE_ADDRESS_TP is a reporting and integration view in the Oracle E-Business Suite e-Commerce Gateway (EC) module. It presents a consolidated, denormalized picture of customer address information joined with the trading partner header that owns each address record. The view is used primarily to expose the relationship between a physical address maintained in Receivables and the trading partner configuration used for outbound and inbound e-Commerce Gateway transactions. It is not implemented as a physical or materialized object in the database; per the ETRM metadata, it is documented as a view with no implemented base in the reference database, meaning it exists as a definitional query rather than a stored artifact surfaced through the deployment.

The suffix "TP" in the object name indicates that the view is oriented toward trading partner data. Each row corresponds to an address (RA_ADDRESSES_ALL) enriched with trading partner header attributes such as TP_HEADER_ID, TP_REFERENCE_EXT1, and TP_REFERENCE_EXT2. Because the search term reported by the user is tp_header_id, this view is the natural access point when an address must be traced back to its owning trading partner header record.

Underlying Base Objects

Two documented base objects are joined in the view definition:

• RA_ADDRESSES_ALL — the Receivables addresses table, aliased RAD. It supplies the address_id, customer_id, original system reference, and the address component columns (ADDRESS1 through ADDRESS4, CITY, POSTAL_CODE, COUNTRY, STATE, PROVINCE, COUNTY).
• ECE_TP_HEADERS — the e-Commerce Gateway trading partner headers table, aliased ETH. It supplies tp_header_id, tp_reference_ext1, and tp_reference_ext2.

The join is expressed as RAD.TP_HEADER_ID = ETH.TP_HEADER_ID (+). This is Oracle's legacy outer-join syntax, meaning RA_ADDRESSES_ALL is the driving (preserved) table and ECE_TP_HEADERS is the optional side. Addresses that are not linked to any trading partner header still appear, with the ETH-derived columns (TP_HEADER_ID, TP_REFERENCE_EXT1, TP_REFERENCE_EXT2) returned as NULL. This behavior is important for reconciliation reporting, since it allows identification of customer addresses that have no trading partner association.

Key Columns

• ADDRESS_ID — Unique identifier of the address in RA_ADDRESSES_ALL; the row key on the address side.
• CUSTOMER_ID — The customer or party that owns the address.
• TP_HEADER_ID — The e-Commerce Gateway trading partner header identifier linking the address to a partner. This is the column most frequently used to filter or join, particularly in the user's query context.
• ORIG_SYSTEM_REFERENCE — The originating-system key for the address, useful when addresses are imported from an external system.
• ADDRESS1–ADDRESS4, CITY, POSTAL_CODE, COUNTRY, STATE, PROVINCE, COUNTY — Standard address component fields used for formatting and validation in outbound documents.
• TP_LOCATION_CODE_EXT — Exposes the ECE_TP_LOCATION_CODE column, the trading partner location code associated with the address.
• TP_REFERENCE_EXT1 / TP_REFERENCE_EXT2 — Extension reference attributes carried from the trading partner header, commonly used to map partner-specific codes or identifiers onto address output.

Common Use Cases and Queries

Typical usage includes verifying which trading partner header governs a given customer address, troubleshooting outbound e-Commerce Gateway address output where the wrong partner header or location code is applied, and identifying addresses with no trading partner association.

To retrieve all addresses for a specific trading partner:

SELECT address_id, customer_id, address1, city, tp_location_code
FROM   ece_address_tp
WHERE  tp_header_id = :p_tp_header_id;

To find addresses lacking a trading partner header (NULL on the outer-joined side):

SELECT address_id, customer_id, orig_system_reference
FROM   ece_address_tp
WHERE  tp_header_id IS NULL;

To join the view back to the header for a complete partner/address listing:

SELECT e.tp_header_id, e.tp_reference_ext1, a.address1, a.city
FROM   ece_address_tp e
WHERE  e.tp_reference_ext1 IS NOT NULL;

Because the object is documented as not implemented in the database, availability depends on the specific environment; consultants should confirm the view exists before relying on it in custom reports or extensions.