Search Results shipment_attribute1




Overview
Explore in AI Chat

Overview

The WSH_STND_SHIPMENT_V view is a shipped-and-standalone reporting object owned by the APPS schema within the Oracle E-Business Suite WSH – Shipping Execution module. Its status is VALID and it is available in both EBS 12.1.1 and 12.2.2. The view presents a denormalized, business-friendly projection of delivery and shipment data, joining delivery header information from WSH_NEW_DELIVERIES with transaction history from WSH_TRANSACTIONS_HISTORY and enriching it with carrier, organization, and ship-from location attributes. Because it exposes descriptive column aliases (for example SHIP_METHOD, CARRIER, TRANSPORTATION_METHOD, and the SHIPMENT_ATTRIBUTE1 through SHIPMENT_ATTRIBUTE15 flexfield columns), it is intended for operational reporting, outbound integrations, and custom concurrent programs rather than for transactional processing. The view is scoped to shipping execution; it does not expose order line or inventory detail, only delivery-level shipment context.

Underlying Base Objects

According to the documented view text and ETRM metadata, WSH_STND_SHIPMENT_V is defined over the following base objects:

  • WSH_NEW_DELIVERIES (SYNONYM) — aliased as WND; supplies the delivery header, weights, volumes, waybill, service level, and the descriptive flexfield attribute columns.
  • WSH_TRANSACTIONS_HISTORY (SYNONYM) — aliased as WTH; supplies action type, document type, document number/revision, and original document number.
  • WSH_CARRIERS_V (VIEW) — aliased as WCAR; resolves the carrier name.
  • WSH_LOCATIONS (SYNONYM) and HR_LOCATIONS_ALL_TL (SYNONYM) — via HRL; provide the ship-from location code.
  • ORG_ORGANIZATION_DEFINITIONS (VIEW) — aliased as OOG; supplies the organization code.
  • HR_GENERAL and HR_SECURITY (PACKAGES) — supply the multitenancy and security predicates used by the localization layer.

The view uses SELECT DISTINCT, so duplicate delivery/transaction combinations are collapsed before returning rows.

Key Columns

Common Use Cases and Queries

Typical scenarios include carrier scorecarding, shipment audits, DFF-driven reporting, and integration feeds. A simple query returning the shipment attribute and its descriptive context is shown below.

  • Retrieve all deliveries carrying a specific DFF value: 
    SELECT delivery_id, document_number, carrier, ship_method,
       shipment_attribute_category, shipment_attribute1
FROM   apps.wsh_stnd_shipment_v
WHERE  shipment_attribute1 = :p_attr1;
  • Weight and volume reconciliation by organization and ship-from location: 
    SELECT organization_code, ship_from_location, carrier,
       SUM(gross_weight) gross, SUM(net_weight) net, SUM(volume) vol
FROM   apps.wsh_stnd_shipment_v
WHERE  creation_date >= :p_from_date
GROUP  BY organization_code, ship_from_location, carrier;
  • Feed deliveries to a downstream TMS using ACTION_CODE, DOCUMENT_TYPE, and DELIVERED_DATE.

Because the view is a reporting projection over transactional shipping tables, always apply organization and date predicates to constrain row counts, and use the DELIVERY_ID to drill back to WSH_NEW_DELIVERIES for any detail not exposed here.