Search Results wsh_delivery_type

Overview

APPS.WSH_DELIVERIES_BOL_RDF_V is a reporting view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that exposes delivery header information in a form suited to Bill of Lading (BOL) and related shipping documentation. The view is owned by the APPS schema and surfaces a small, focused projection of delivery data drawn from the Warehouse Management (WSH) module. Its defining characteristic is that it joins the delivery record to the seeded WSH_DELIVERY_TYPE lookup so that the raw lookup code is translated into a human-readable meaning.

The view embodies a deliberate presentation convention: when the delivery type is STANDARD, the meaningful description is suppressed (returned as NULL), and for all other delivery types the corresponding lookup meaning is returned. This design allows downstream reports, BOL print programs, and integration extracts to display a descriptive delivery type only when the delivery deviates from the default standard delivery. Because it is an RDF (Report Definition File)-style view, it is typically consumed by Oracle Reports, concurrent programs, and custom SQL reports rather than by the application's base transactional logic.

Underlying Base Objects

The view is defined over two documented objects:

• WSH_NEW_DELIVERIES (referenced via a synonym) — the core delivery header entity in Warehouse Management. This supplies the delivery identifier, name, delivery type code, organization, and shipment direction.
• FND_LOOKUP_VALUES_VL (a view) — the multilingual lookup values view in the Application Object Library (FND). It supplies the translated MEANING for the delivery type code.

The join is an equijoin between WND.DELIVERY_TYPE and LKP.LOOKUP_CODE, restricted by the predicate LKP.LOOKUP_TYPE = 'WSH_DELIVERY_TYPE'. This restricts the lookup side to the seeded delivery type lookup set, ensuring each delivery is matched to exactly one valid delivery type meaning. The use of the _VL lookup view means the returned meaning respects the session's language, an important consideration for global, multi-language deployments.

Key Columns

• DELIVERY_ID — the unique identifier of the delivery header; the primary join key to other WSH delivery and detail objects.
• NAME — the delivery name/number as known within Warehouse Management.
• DELIVERY_TYPE — the raw lookup code stored on the delivery (for example, STANDARD or other seeded types). This is the value that most directly answers the common search term "delivery_type."
• DELIVERY_TYPE_MEANING — a derived column produced by DECODE(delivery_type,'STANDARD',NULL,lkp.meaning). It returns the descriptive meaning of the delivery type for non-standard deliveries and NULL for standard ones, supporting cleaner report output.
• ORGANIZATION_ID — the inventory organization that owns the delivery, enabling organization-level filtering and reporting.
• SHIPMENT_DIRECTION — indicates whether the shipment is inbound or outbound, relevant to BOL and logistics reporting.

Common Use Cases and Queries

Typical scenarios include Bill of Lading printing, delivery manifests, and logistics extracts where the delivery type must be presented descriptively. A representative query is:

• SELECT delivery_id, name, delivery_type, delivery_type_meaning, organization_id, shipment_direction FROM apps.wsh_deliveries_bol_rdf_v WHERE organization_id = :org_id;
• Filtering non-standard deliveries: SELECT delivery_id, name, delivery_type_meaning FROM apps.wsh_deliveries_bol_rdf_v WHERE delivery_type_meaning IS NOT NULL;
• Restricting by direction for outbound BOLs: SELECT name, delivery_type, shipment_direction FROM apps.wsh_deliveries_bol_rdf_v WHERE shipment_direction = 'OUTBOUND';

Because the view already resolves the delivery type meaning and handles the standard-type suppression, it simplifies report logic and reduces the need for repeated lookup joins in custom queries.