Search Results tp_header_attribute1

Overview

WSH_DSNO_DELIVERY_ATTRIBS_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, registered under the WSH (Shipping Execution) product. It exposes delivery-related attribute information that originates from Oracle Transportation Management (OTM) or from external trading partner (TP) integration flows, where header-level and detail-level descriptive flexfield (DFF) values are captured against transportation planning entities and then reconciled back to Oracle Shipping deliveries. The view joins delivery records to their transportation planning header and detail rows, to warehouse and location master data, and to customer master data, presenting a flattened, reporting-friendly projection of the attribute columns.

The object is most relevant to integrators and report developers who need the transportation planning (TP_) identifier context for a delivery, including the searched column TP_DETAIL_ID. The view is documented as VALID, indicating a successfully compiled definition in the referenced environment. Because it is a view and not a table, it carries no storage of its own and inherits read-only semantics from the underlying base objects.

Underlying Base Objects

The documented base objects reveal the lineage of the view. Transportation planning data is sourced from ECE_TP_HEADERS and ECE_TP_DETAILS, which supply TP_HEADER_ID and TP_DETAIL_ID respectively. The delivery side is sourced from the WSH family: WSH_DELIVERY_DETAILS, WSH_NEW_DELIVERIES, WSH_LOCATIONS, and the aggregate view WSH_DELIVERY_ASSIGNMENTS_V. Location and trading partner context is enriched through HR_LOCATIONS_ALL, while customer and site information is drawn from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and HZ_PARTY_SITES. The view text carries an ORDERED hint, indicating the join sequence is deliberately controlled by the developer, a common pattern where ECE and WSH tables are linked via location code and delivery identifiers.

Key Columns

• TP_HEADER_ID — Identifier of the transportation planning header row, sourced from ECE_TP_HEADERS.
• TP_DETAIL_ID — Identifier of the transportation planning detail row, sourced from ECE_TP_DETAILS; the column associated with the user's search term.
• DELIVERY_ID — Delivery identifier from WSH_NEW_DELIVERIES, linking the TP context to a shipping delivery.
• WAREHOUSE_LOCATION_ID — Initial pickup location identifier, mapped to the delivery's warehouse.
• WAREHOUSE_CODE_EXT — External ECE trading partner location code for the warehouse.
• DESTINATION_SITE_USE_ID and DESTINATION_CUSTOMER_ID — Customer site use and account identifiers for the ship-to destination.
• Attribute sets — TP_HEADER_ATTRIBUTE1..15, TP_DETAIL_ATTRIBUTE1..5, and WAREHOUSE_ATTRIBUTE1..n, each paired with an ATTRIBUTE_CATEGORY column, exposing DFF context for planning and location data.

Common Use Cases and Queries

This view supports reconciliation reporting between OTM/TP planning records and Oracle Shipping deliveries, enabling users to trace which transportation plan detail drove a given delivery and to inspect the associated flexfield values. It is also useful when investigating interface errors, since TP detail context is difficult to retrieve directly from delivery tables.

A typical query returns TP detail context for a delivery:

SELECT d.delivery_id, d.tp_header_id, d.tp_detail_id,
  d.warehouse_code_ext, d.destination_customer_id
FROM apps.wsh_dsno_delivery_attribs_v d
WHERE d.delivery_id = :p_delivery_id;

To resolve a search on the detail identifier across related attributes:

SELECT tp_header_id, tp_detail_id, tp_detail_category,
  tp_detail_attribute1, tp_detail_attribute2
FROM apps.wsh_dsno_delivery_attribs_v
WHERE tp_detail_id = :p_tp_detail_id;

Because the ORDERED hint fixes the join path, consider driving queries from delivery or TP identifiers rather than performing unconstrained full scans on large ECE and HZ tables.