Results for “tp_header_id”

50+ results




Overview
Explore in AI Chat

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

Overview

The CLN_ITEMMST_TRADING_PARTNERS_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite environment. It belongs to the CLN product, formally the Supply Chain Trading Connector for RosettaNet, which provides the messaging and process orchestration layer used to exchange business documents with external trading partners over RosettaNet and related B2B protocols.

As documented in the ETRM metadata, this view presents a consolidated list of the available trading partners that participate in RosettaNet item master synchronization flows. Rather than exposing raw identifiers alone, the view assembles a human-readable trading partner name by concatenating the party name with its associated address components, and pairs that label with the internal RosettaNet trading partner header identifier. In release 12.1.1 and 12.2.2 the object is reported with a status of VALID, indicating that the compiled definition is consistent with its referenced base objects.

The view is read-oriented. It performs no data manipulation and holds no storage of its own; it is a projection over existing EBS trading community and RosettaNet configuration tables. Its principal role is to give applications, concurrent programs, and ad hoc queries a stable, denormalized source for resolving a trading partner name to the identifier required by the connector.

Underlying Base Objects

The view is defined over seven base objects, all exposed to APPS as synonyms. They fall into three functional groups:

The joins are fully deterministic. ECX_TP_HEADERS links to ECX_TP_DETAILS on TP_HEADER_ID and to HZ_PARTIES on PARTY_ID; it links to HZ_PARTY_SITES on PARTY_SITE_ID, which in turn joins HZ_LOCATIONS on LOCATION_ID. The detail rows join ECX_EXT_PROCESSES on EXT_PROCESS_ID, and ECX_EXT_PROCESSES joins ECX_TRANSACTIONS on TRANSACTION_ID.

Key Columns

The view exposes two columns:

  • TRADING_PARTNER_NAME — A concatenation of HP.PARTY_NAME, ADDRESS1, ADDRESS2, CITY, STATE, and POSTAL_CODE, separated by single spaces. This is the descriptive label intended for display and selection lists. Because it is built from address components, two sites belonging to the same party can produce distinct names.
  • TP_HEADER_ID — The trading partner header identifier from ECX_TP_HEADERS. This is the surrogate key used throughout the connector to reference a specific partner registration, and is the value callers typically store or pass downstream.

The view's filter predicates restrict results to outbound synchronization: ET.TRANSACTION_TYPE = 'CLN', ET.TRANSACTION_SUBTYPE = 'SYNCITEMO', and EEP.DIRECTION = 'OUT'. Only trading partners configured for outbound RosettaNet item master synchronization are therefore returned.

Common Use Cases and Queries

Typical scenarios include populating a trading partner list of values, validating that a partner is registered for outbound item synchronization, and joining the returned TP_HEADER_ID back to connector tables for diagnostics or reconciliation.

Resolving a name to its identifier:

  • SELECT TP_HEADER_ID, TRADING_PARTNER_NAME FROM CLN_ITEMMST_TRADING_PARTNERS_V ORDER BY TRADING_PARTNER_NAME;

Searching by a known party name fragment, which is the pattern most often used when a user searches for a partner by name:

  • SELECT TP_HEADER_ID, TRADING_PARTNER_NAME FROM CLN_ITEMMST_TRADING_PARTNERS_V WHERE TRADING_PARTNER_NAME LIKE '%' || :p_name || '%';

Joining the view to ECX_TP_HEADERS or ECX_TP_DETAILS on TP_HEADER_ID supports auditing of which external processes map to each visible partner. Because the view is read-only and does not aggregate, existing indexes on the underlying primary and foreign keys are used directly, keeping query cost low.