Search Results wsh_address_tp_v

Overview

WSH_ADDRESS_TP_V is a Shipping Execution (WSH) view that joins shipping address records from the Receivables address repository to trading partner header information from the E-Commerce/EDI gateway. The view exposes a denormalized address and trading partner projection used historically to reconcile ship-to locations with the trading partner (TP) definitions that describe how a customer or supplier is represented in electronic commerce transactions. The view carries an explicit obsolescence marker: the WHERE clause contains the constant predicate 'THIS VIEW IS OBSOLETE FROM PATCHSET I ONWARDS' = 'TRUE'. This technique forces the driving condition to evaluate true while documenting that Oracle no longer supports the object in current patchsets.

Because of this marker, WSH_ADDRESS_TP_V should be treated as a documentation and historical reference artifact rather than a supported integration point in Oracle EBS 12.1.1 or 12.2.2. Existing custom code that references it may still compile and execute, but Oracle does not guarantee column semantics, join behavior, or continued availability across patches.

Underlying Base Objects

The documented view text is defined over two base tables:

• RA_ADDRESSES_ALL — the multi-org address table holding address and party/customer information. It supplies the address identifier, customer identifier, original system reference, and the individual address component columns.
• ECE_TP_HEADERS — the EDI/E-Commerce trading partner header table. It supplies the trading partner header identifier and the two external trading partner reference attributes.

The join is an outer join from RA_ADDRESSES_ALL to ECE_TP_HEADERS on the TP_HEADER_ID column, expressed as RAD.TP_HEADER_ID = ETH.TP_HEADER_ID (+). This means every qualifying address row is returned even when no matching trading partner header exists, with the ECE columns nulled out. The relationship is therefore address-driven: RA_ADDRESSES_ALL is the driving table and ECE_TP_HEADERS is the optionally matched lookup.

Key Columns

• ADDRESS_ID — primary address identifier from RA_ADDRESSES_ALL; the unique key for the returned address record.
• CUSTOMER_ID — the party or customer that owns the address.
• TP_HEADER_ID — the trading partner header identifier carried on the address record and matched to ECE_TP_HEADERS. This is the column most often used to correlate addresses with their EDI trading partner definition, and matches the user's search term.
• ORIG_SYSTEM_REFERENCE — the originating system's reference for the address, used in multi-system environments to trace the source record.
• ADDRESS1 – ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY — the standard address component fields.
• TP_LOCATION_CODE_EXT — aliases RAD.ECE_TP_LOCATION_CODE, the EDI location code associated with the address.
• TP_REFERENCE_EXT1 and TP_REFERENCE_EXT2 — the external trading partner references from ECE_TP_HEADERS, available only when a matching header exists.

Common Use Cases and Queries

The principal historical use case is verifying that shipping addresses are correctly associated with trading partner definitions prior to EDI transaction generation, and auditing addresses that lack a trading partner mapping. A representative query filtering on the column the user searched for:

SELECT address_id,
       customer_id,
       tp_header_id,
       city,
       state,
       postal_code,
       country,
       tp_location_code_ext
FROM   wsh_address_tp_v
WHERE  tp_header_id = :p_tp_header_id;

To identify addresses with no ECE trading partner header (outer-join nulls):

SELECT address_id, customer_id, tp_header_id
FROM   wsh_address_tp_v
WHERE  tp_reference_ext1 IS NULL;

Given the obsolescence marker, new development should query RA_ADDRESSES_ALL and ECE_TP_HEADERS directly, or use the supported Shipping Execution and E-Commerce views, rather than relying on WSH_ADDRESS_TP_V. Any existing report or interface that depends on this view should be inventoried and migrated. The metadata does not document an owner or additional referenced base objects, and the object is noted as not implemented in the current database, consistent with its obsolete status.