Search Results party_site_name

Overview

ECX_TP_HEADERS_V is a consolidated reporting view owned by the APPS schema in Oracle E-Business Suite (validated on 12.1.1 and 12.2.2). It belongs to the ECX — XML Gateway product family and resolves the trading partner header definitions stored in ECX_TP_HEADERS into a business-friendly result set by joining each partner to its party/vendor/site master data. In other words, while ECX_TP_HEADERS holds the raw trading partner configuration (party identifiers, site identifiers, administrator e-mail, and audit columns), ECX_TP_HEADERS_V enriches those rows with human-readable names and addresses plus an ORG_ID, making the view suitable for reporting, integration diagnostics, and XML Gateway troubleshooting rather than for transactional processing.

Underlying Base Objects

The documented view text defines three UNION ALL-style branches, one per partner category. For customers (ETPH.PARTY_TYPE = 'C'), the view joins HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_CUST_ACCT_SITES to obtain the party name, the composed site address, and ORG_ID. For suppliers (PARTY_TYPE = 'S'), it joins PO_VENDORS and PO_VENDOR_SITES to obtain the vendor name, site address, and ORG_ID. A third branch is present in the source (truncated in the documentation excerpt) that resolves bank branch partners, and the documented 12.2.2 base-object list confirms the presence of CE_BANK_BRANCHES_V. All branches share ECX_LOOKUP_VALUES (lookup_type 'PARTY_TYPE') to translate the partner type code into a description, and ECX_TP_HEADERS as the primary driving object. The object list also references FND_GLOBAL, HR_GENERAL, and HR_LOCATIONS, which are typically invoked by the underlying HZ/PO views and packages rather than directly by ECX_TP_HEADERS_V. Note that HZ_* and ECX_TP_HEADERS appear as synonyms in 12.2.2, while PO_VENDORS, PO_VENDOR_SITES, CE_BANK_BRANCHES_V, and ECX_LOOKUP_VALUES are views.

Key Columns

• TP_HEADER_ID — Surrogate key from ECX_TP_HEADERS identifying the trading partner header row.
• PARTY_TYPE — Decoded description of the partner classification (e.g., Customer, Supplier, Bank) from ECX_LOOKUP_VALUES.
• PARTY_ID — Identifier of the party, vendor, or bank branch master record, depending on branch.
• PARTY_SITE_ID — Identifier of the party site, vendor site, or bank branch site.
• PARTY_NAME — Customer party name, vendor name, or bank branch name.
• PARTY_SITE_NAME — Concatenation of address lines, city, state/region, and postal code into a single descriptive string. This is the column most often located by the search term "party_site_name".
• COMPANY_ADMIN_EMAIL — Contact e-mail configured for the trading partner.
• ORG_ID — Operating unit context, sourced from HZ_CUST_ACCT_SITES or PO_VENDOR_SITES as applicable.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include validating trading partner setup before enabling an outbound XML Gateway transaction, reconciling partner headers against customer or supplier master data, and producing audit extracts of e-mail contacts and site addresses. Because PARTY_SITE_NAME is a concatenated, non-indexed expression, queries should filter on PARTY_ID, PARTY_SITE_ID, or ORG_ID first and use PARTY_SITE_NAME only for display or fuzzy searching.

• List all configured customer partners:
  SELECT tp_header_id, party_name, party_site_name, company_admin_email FROM apps.ecx_tp_headers_v WHERE party_type = 'Customer';
• Find a partner by site address fragment:
  SELECT tp_header_id, party_name, party_site_name FROM apps.ecx_tp_headers_v WHERE org_id = :p_org_id AND UPPER(party_site_name) LIKE '%' || UPPER(:p_fragment) || '%';
• Audit recent partner setup changes:
  SELECT tp_header_id, party_name, last_update_date, last_updated_by FROM apps.ecx_tp_headers_v WHERE last_update_date >= SYSDATE - 30;

In 12.2.2, results remain consistent with 12.1.1 because the view definition is unchanged and continues to rely on the HZ and PO_VENDOR synonyms and views.