Search Results shipment_direction




Overview
Explore in AI Chat

Overview

The WSH_DELIVERIES_BOL_RDF_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Shipping Execution (WSH) module. Its name incorporates the "RDF" convention commonly used by Oracle Reports and report definition files, indicating that the view was constructed to feed a specific Bill of Lading (BOL) report or similar shipping document output. The view presents a streamlined, denormalized projection of delivery header information, exposing delivery identity, type, organization, and shipment direction in a form directly consumable by reporting tools such as Oracle Reports, BI Publisher, or custom concurrent programs.

The view carries a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. Its principal role is to supply delivery records suitable for Bill of Lading generation and related shipping documentation, while translating internal delivery type lookup codes into user-facing meanings. Because it is a view rather than a base table, it imposes no physical storage and reflects live data from its underlying sources at query time.

Underlying Base Objects

The view is defined over two documented base objects:

  • WSH_NEW_DELIVERIES (referenced as a SYNONYM) — the primary delivery source, aliased in the view text as WND. This object supplies the delivery header attributes including delivery ID, name, type, organization, and shipment direction.
  • FND_LOOKUP_VALUES_VL (VIEW) — the Oracle Application Object Library lookup values view, aliased as LKP. This supplies the translated meaning for the delivery type lookup.

The two sources are joined with an inner equijoin: WND.DELIVERY_TYPE = LKP.LOOKUP_CODE, constrained by LKP.LOOKUP_TYPE = 'WSH_DELIVERY_TYPE'. Because the join is an inner join, only deliveries whose type matches a defined lookup code in the WSH_DELIVERY_TYPE lookup type are returned. The FND_LOOKUP_VALUES_VL view itself joins the base lookup values table to its translation (_TL) table, so the MEANING returned reflects the session's language where a translation is available.

Key Columns

  • DELIVERY_ID — The unique system identifier for the delivery; the primary key used to relate the delivery to its detail lines and assignments.
  • NAME — The user-visible delivery name or number, typically the delivery identifier displayed on shipping documents and the Bill of Lading.
  • DELIVERY_TYPE — The internal lookup code for the delivery type (for example, STANDARD), drawn from the WSH_DELIVERY_TYPE lookup type.
  • DELIVERY_TYPE_MEANING — A decoded, user-facing description of the delivery type. The view applies a DECODE so that the value 'STANDARD' is returned as NULL, while all other types return the lookup meaning. This suppresses display of the meaning for standard deliveries while showing descriptive text for non-standard types.
  • ORGANIZATION_ID — The inventory organization that owns the delivery, used for organizational filtering and reporting.
  • SHIPMENT_DIRECTION — Indicates the direction of the shipment (for example, outbound or inbound), supporting directional reporting and document selection.

Common Use Cases and Queries

The view is typically consumed by BOL and shipping documentation reports that require delivery header data enriched with human-readable delivery type meanings. Common scenarios include listing deliveries for a given organization, filtering to non-standard delivery types, and joining delivery IDs back to the base WSH tables for line-level detail.

A representative query retrieving deliveries for an organization, with meaningful type descriptions, is:

  • SELECT delivery_id, name, delivery_type, delivery_type_meaning, organization_id, shipment_direction FROM apps.wsh_deliveries_bol_rdf_v WHERE organization_id = :p_org_id ORDER BY name;

To isolate non-standard deliveries — those for which the decoded meaning is populated — a filter on delivery_type_meaning IS NOT NULL may be applied. To obtain line and item detail, the report or query joins delivery_id to the delivery detail tables such as WSH_DELIVERY_ASSIGNMENTS and WSH_DELIVERY_DETAILS. Because the view exposes only header-level attributes, it serves as the entry point for a broader BOL report query rather than a standalone data source.