Search Results shipping_marks




Overview
Explore in AI Chat

Overview

The WSH_STND_SHIPMENT_V view is a standard Oracle Shipping Execution (WSH) reporting object owned by the APPS schema. It exposes a consolidated, denormalized projection of shipment (delivery) header information combined with document-type and transaction-history attributes. The name carries the "STND" (standard) prefix, indicating that Oracle ships this view as part of the seeded WSH schema rather than as a customer-defined object. In Oracle EBS 12.1.1 and 12.2.2, the view is registered in the ETRM with a status of VALID.

The primary role of the view is to provide a single, read-only source for shipment-level attributes that would otherwise require joining the delivery header, carrier, location, organization, and document-history tables. Because it flattens these relationships, it is well suited for operational reports, outbound integration extracts, carrier manifest interfaces, and ad-hoc queries. It is particularly relevant to users searching on shipping_marks, since the view exposes the SHIPPING_MARKS column directly from the delivery record.

Underlying Base Objects

The view is defined with a DISTINCT join over the delivery and transaction-history objects. The documented base objects are:

Key Columns

Common Use Cases and Queries

Typical usage includes shipment status reports, carrier extracts, and flexfield-driven custom reporting. A representative query retrieving shipping marks is:

SELECT DELIVERY_ID, DOCUMENT_NUMBER, SHIP_FROM_LOCATION, CARRIER, SERVICE_LEVEL, SHIPPING_MARKS, GROSS_WEIGHT, FREIGHT_TERMS FROM APPS.WSH_STND_SHIPMENT_V WHERE DOCUMENT_NUMBER = :p_doc;

Because the view applies DISTINCT and joins transaction history, a single delivery may return multiple rows when several historical document actions exist. Queries should therefore filter by ACTION_CODE or DOCUMENT_TYPE where a specific document is required, and should be executed using the APPS schema or a responsibility with WSH reporting privileges.