Search Results shipped_quantity_disp

Overview

The view SO_PICKING_LINES_VIEW_V belongs to the Oracle Order Entry (OE) module and provides a consolidated, reporting-oriented projection of picking line activity drawn from the shipping and picking execution tables of Oracle Shipping Execution. It joins picking lines, picking headers, picking batches, inventory item master information, ship-to locations, and order lines into a single flattened structure suitable for operational reporting, label printing, and integration extracts.

The view is not implemented as a physical database object in every environment; the ETRM metadata explicitly notes "Not implemented in this database," meaning availability depends on the applied patch level and installed shipping functionality. Where present, it is typically used by shipping reports, carrier interfaces, and custom dashboards that require picking line detail without invoking the full pick confirmation UI.

Underlying Base Objects

The view definition references the following base objects:

• SO_PICKING_LINES (SPL) — the primary driving table, holding individual picking line records.
• SO_PICKING_HEADERS (SPH) — header-level shipping and confirmation data, outer-joined to SPL.
• SO_PICKING_BATCHES (PB) — batch grouping information, outer-joined through SPH.BATCH_ID.
• SO_PICKING_LINE_DETAILS (SPLD) — supplies the pick slip number.
• SO_LINES (SL) — order line linkage for header resolution.
• MTL_PARAMETERS (MP) — resolves the warehouse organization code.
• MTL_SYSTEM_ITEMS_VL (MSI) — item description, outer-joined.
• ORG_FREIGHT (ORGF) — freight organization configuration.
• RA_SITE_USES (RSU) — ship-to location.

All header, batch, warehouse, item, freight, and site-use joins are outer joins, ensuring picking line rows are retained even when related context is missing.

Key Columns

• PICKING_LINE_ID — unique identifier of the picking line.
• PICK_SLIP_NUMBER — printed pick slip reference from SO_PICKING_LINE_DETAILS.
• WAREHOUSE — organization code resolved via MTL_PARAMETERS.ORGANIZATION_CODE.
• ITEM — concatenated item flexfield, derived using OE_QUERY.ITEM_CONC_SEG together with FND_PROFILE.VALUE('SO_ORGANIZATION_ID'). This profile-driven lookup is the reason the search term so_organization_id surfaces in this context: the concatenated item segment and the ORG_FREIGHT join both depend on the SO_ORGANIZATION_ID profile option.
• SHIPPED_QUANTITY_DISP — shipped quantity with nulls decoded to zero.
• REQUESTED_QUANTITY and BACKORDERED_QUANTITY — requested versus shortfall, the latter computed where PICKING_HEADER_ID is zero.
• RESERVED_QUANTITY — derived from OE_QUERY.PICKING_LINE_RESERVED_QTY.
• SCHEDULE_STATUS — derived from OE_QUERY.SCHEDULE_STATUS where no header exists.
• DATE_SHIPPED, DATE_CONFIRMED, WAYBILL_NUM, NUMBER_OF_BOXES, WEIGHT — shipment tracking attributes.
• SHIP_TO_LOCATION — from RA_SITE_USES.LOCATION.
• ROW_ID — SPL rowid for row-level addressing.

Common Use Cases and Queries

Typical scenarios include pick slip reprint, shipped-versus-requested analysis, backorder identification, and carrier waybill reconciliation.

SELECT picking_line_id,
       pick_slip_number,
       item,
       warehouse,
       shipped_quantity_disp,
       requested_quantity,
       backordered_quantity,
       date_shipped,
       waybill_num
FROM   so_picking_lines_view_v
WHERE  warehouse = :org_code
AND    date_shipped >= :from_date;

To list currently unshipped picking lines with reserves:

SELECT picking_line_id,
       item,
       reserved_quantity,
       schedule_status
FROM   so_picking_lines_view_v
WHERE  picking_header_id = 0
AND    reserved_quantity > 0;

Because the ITEM column resolves through FND_PROFILE.VALUE('SO_ORGANIZATION_ID'), query results can differ by responsibility or user session when the profile option varies; report developers should set the profile explicitly before execution to guarantee consistent item concatenation and freight join behavior.