Search Results pooled_ship_to_location

Overview

APPS.WSH_SS_PARTNER_V is a shipping and receiving partner view within the Oracle E-Business Suite Warehouse Management (WSH) module. It exposes ship-to partner information associated with deliveries, deriving its rows primarily from the delivery header table WSH_NEW_DELIVERIES joined against the Oracle Trading Community Architecture (TCA) model — parties, party sites, customer account sites, customer site uses, and locations. The view presents a flattened, DISTINCT set of partner attributes that downstream shipping documents, EDI partner mappings, and integration interfaces consume when they require a normalized ship-to partner record tied to an outbound delivery.

The object is relevant in both 12.1.1 and 12.2.2, where the TCA data model (HZ_* synonyms) is the authoritative source for party and location data. Because the view is owned by APPS and references public synonyms, it is callable from custom concurrent programs, BI Publisher data templates, and inbound/outbound EDI maps without requiring direct grants on the underlying HZ tables.

Underlying Base Objects

The documented dependency list includes: HR_GENERAL (PACKAGE), HR_LOCATIONS (VIEW), HR_SECURITY (PACKAGE), HZ_CONTACT_POINTS (SYNONYM), HZ_CUST_ACCT_SITES (SYNONYM), HZ_CUST_SITE_USES (SYNONYM), HZ_LOCATIONS (SYNONYM), HZ_PARTIES (SYNONYM), HZ_PARTY_SITES (SYNONYM), ORG_ORGANIZATION_DEFINITIONS (VIEW), and WSH_NEW_DELIVERIES (SYNONYM). The view text joins WSH_NEW_DELIVERIES to HZ_PARTIES via party_id, to HZ_PARTY_SITES via party_site_id, and to HZ_CUST_SITE_USES and HZ_CUST_ACCT_SITES through the customer account site chain, filtered to SITE_USE_CODE = 'SHIP_TO' and STATUS = 'A'. Address and contact attributes come from HZ_LOCATIONS and HZ_CONTACT_POINTS. Two inline views named INTMED_SHIP_TO_V and POOLED_SHIP_TO_V supply intermediate ship-to and pooled ship-to location, phone, and URL data, which is why the search term "pooled_ship_to_v" resolves here — it is an internal alias, not a standalone database object.

Key Columns

• PARTY_NAME — the ship-to party name from HZ_PARTIES.
• PARTNER_LOCATION and PARTNER_TYPE — location designation and the literal 'ShipTo' partner classification.
• DUNS_NUMBER — the party's D-U-N-S identifier used in EDI partner identification.
• INTMED_SHIP_TO_LOCATION / POOLED_SHIP_TO_LOCATION — intermediate and pooled ship-to locations derived from the inline views.
• ADDRESS1–4, CITY, STATE, PROVINCE, COUNTY, COUNTRY, POSTAL_CODE — the formatted ship-to address from HZ_LOCATIONS.
• TELEPHONE, FAX_NUMBER, URL — contact points sourced from the GEN and FAX contact point records.
• DELIVERY_ID — the WSH_NEW_DELIVERIES key linking the partner back to a specific delivery.

Common Use Cases and Queries

Typical scenarios include populating EDI 856/810 partner segments, driving shipping label and manifest output, and validating ship-to addresses on delivery confirmation. A representative query returns partner detail for a single delivery:

• SELECT party_name, partner_location, duns_number, address1, city, state, postal_code, telephone FROM apps.wsh_ss_partner_v WHERE delivery_id = :delivery_id;
• SELECT delivery_id, party_name, pooled_ship_to_location FROM apps.wsh_ss_partner_v WHERE duns_number = :duns;
• SELECT partner_name, partner_type FROM apps.wsh_ss_partner_v WHERE partner_type = 'ShipTo';

Because the view employs SELECT DISTINCT across multiple joins, performance benefits from filtering on DELIVERY_ID or DUNS_NUMBER, and consumers should avoid joining it to large transaction sets without such predicates.