Search Results dock_code

Overview

WSH_DLS_UNASSIGNED_SC_V is a reporting view in the Oracle E-Business Suite Order Entry (OE) module that surfaces picking line details which have not yet been assigned to a delivery. The view name reflects its functional scope: WSH (Warehouse Shipping / shipping execution), DLS (delivery line sourcing), and UNASSIGNED_SC (unassigned shipping container / delivery assignment). Its principal purpose is to expose open picking activity that is still awaiting delivery assignment, providing a staging and reporting layer over the shipping execution data model.

The view is documented in ETRM 12.2.2 metadata as "Not implemented in this database," indicating that it is a seeded but conditionally deployed object. In Oracle EBS 12.1.1 and 12.2.2, such views are commonly used by shipping, warehouse, and fulfillment reporting processes to identify demand lines that remain candidates for delivery grouping and shipment confirmation. The view also carries the ULTIMATE_SHIP_TO_ID column, which is the attribute users typically search when tracing where a picked line will ultimately be shipped.

Underlying Base Objects

The view is defined over a join of several shipping and order management base tables. The documented FROM clause references:

• SO_PICKING_LINE_DETAILS (PLD) — picking line detail rows, the driving table for unassigned lines.
• SO_PICKING_LINES_ALL (PL) — picking line header-level attributes.
• SO_PICKING_HEADERS_ALL (PH) — picking header and status information.
• SO_LINES_ALL (L) — order line details, including intermediate ship-to.
• SO_HEADERS_ALL (H) — order header attributes such as customer, currency, and ship-to.
• WSH_PACKED_CONTAINERS (PC) — packed container and container item information (outer-joined).
• MTL_SYSTEM_ITEMS (MSI) — item master description for containers (outer-joined).
• WIP_ENTITIES (WIP) — WIP entity name for the associated work order.
• RA_CUSTOMERS (RC) — customer name.

Filters restrict results to open picking headers (STATUS_CODE = 'OPEN') and lines with no delivery assignment (PLD.DELIVERY_ID IS NULL), which is precisely what makes the view represent "unassigned" picking content.

Key Columns

• ULTIMATE_SHIP_TO_ID — the resolved ship-to site use ID, derived via NVL from picking line, picking header, order line, then order header, reflecting the effective ultimate destination.
• INTERMEDIATE_SHIP_TO_ID — the intermediate ship-to from the order line, relevant to drop-ship or multi-leg flows.
• PICKING_LINE_DETAIL_ID / PICK_SLIP_NUMBER — identifiers for the picking detail and pick slip.
• REQUESTED_QUANTITY — quantity requested on the picking line detail.
• ORGANIZATION_ID — warehouse organization (from WAREHOUSE_ID).
• INVENTORY_ITEM_ID and CONTAINER_ID / CONTAINER_INVENTORY_ITEM_ID — item and container associations.
• FREIGHT_CARRIER_CODE / SHIPMENT_PRIORITY_CODE / FOB_CODE / FREIGHT_TERMS_CODE — shipping and commercial attributes.
• ORDER_NUMBER / LINE_NUMBER / ORDER_HEADER_ID — order identifiers.
• CUSTOMER_ID / CUSTOMER_NAME — customer references.
• WIP_NUMBER — associated WIP entity name.

Common Use Cases and Queries

The view is typically queried to find picking demand not yet grouped into deliveries, enabling planners to analyze unassigned shipment volume. A common query filters by organization and destination:

• Identify all unassigned picked lines for a warehouse.
• Group by ULTIMATE_SHIP_TO_ID to measure demand by destination.
• Join to RA_SITE_USES_ALL on ULTIMATE_SHIP_TO_ID for address reporting.

Example:

SELECT pick_slip_number, order_number, line_number, inventory_item_id, requested_quantity, ultimate_ship_to_id FROM wsh_dls_unassigned_sc_v WHERE organization_id = :org_id;

Because the view resolves the ultimate ship-to through nested NVL logic, it is especially useful when the ship-to is defined at different levels (header, line, picking header, or picking line), and users searching on ultimate_ship_to_id can reliably locate the effective destination for each unassigned picking line.