Search Results pooled_ship_to




Overview
Explore in AI Chat

Overview

WSH_DELIVERY_TEMPLATES_V is a reporting and inquiry view in Oracle E-Business Suite that exposes delivery template definitions used by Oracle Shipping and Order Management. Delivery templates allow planners and shipping personnel to predefine recurring delivery schedules, departure templates, and the ship-to routing hierarchy (customer, ultimate ship-to, intermediate ship-to, and pooled ship-to) associated with consolidated or pooled outbound shipments. The view is catalogued under the OE – Order Entry product grouping and is primarily consumed by reporting, integration, and inquiry routines that need to resolve delivery template identifiers and their associated location names without joining the base shipping tables directly.

The view is significant for users searching on the column pooled_ship_to, because it denormalizes the pooled ship-to location into a single readable value derived from the RA_SITE_USES_ALL table, removing the need to resolve the ship-to identifier manually. In ETRM metadata for 12.2.2, the object lists no referenced base objects and is marked "Not implemented in this database," indicating that the view is defined at the application layer and may not exist in every environment or schema against which the documentation was generated. In practice it is created in the APPS schema and accessible to reporting users and concurrent programs.

Underlying Base Objects

The view is defined over a join of four documented base objects:

  • WSH_DELIVERY_TEMPLATES WDELT — the primary driving table holding the delivery template header, including organization, name, planned departure template, sequencing, and the three ship-to identifiers.
  • WSH_DEPARTURE_TEMPLATES WDEPT — supplies the planned departure template name (PLANNED_DEP_TEMPLATE_NAME).
  • RA_CUSTOMERS RC — supplies the customer name associated with the template.
  • RA_SITE_USES_ALL RSUA1, RSUA2, RSUA3 — three aliases of the site uses table that resolve the ultimate ship-to, intermediate ship-to, and pooled ship-to location values respectively.

The join is rooted on the delivery template record and extends outward to resolve descriptive names for the customer and each ship-to level. This structure enables a single-row result per delivery template, with all three location names available as text.

Key Columns

Common Use Cases and Queries

The most frequent use is resolving the pooled ship-to name for a given template or reporting on routing configuration. For example, to list templates and their pooled destinations:

SELECT name, organization_id, customer_name, pooled_ship_to
FROM wsh_delivery_templates_v
WHERE pooled_ship_to IS NOT NULL;

To identify templates linked to a specific customer and review all routing levels:

SELECT name, customer_name, ultimate_ship_to, intermediate_ship_to, pooled_ship_to
FROM wsh_delivery_templates_v
WHERE customer_id = :p_customer_id;

It is also used to validate scheduled templates by planned frequency:

SELECT name, planned_frequency, planned_day, planned_time, expected_arrival_day_offset
FROM wsh_delivery_templates_v
WHERE organization_id = :p_org_id;

Integrations often query the view to populate downstream systems with template-to-location mappings without performing separate joins to RA_SITE_USES_ALL. Because the view spans shipping and receivables base objects, organizations should confirm that the view exists and is valid in the target environment before relying on it in custom code, per the ETRM note that it was not implemented in the documented database.