Results for “schedule_status_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_PICKING_UPGRADE_V is an APPS-owned database view in the Oracle Shipping Execution (WSH) module, defined over picking line and picking line detail data. Its name reflects its original purpose: supporting the 11i-to-Release 12 upgrade path, where legacy picking line records are reconciled with the new Release 12 shipping data model. Although it originated as an upgrade utility, the view remains valid in EBS 12.1.1 and 12.2.2 and is frequently referenced for reporting on picking activity, requested versus shipped quantities, and departure-schedule linkage.

The view presents one row per picking line / line detail / schedule-date combination, aggregating quantity information at that grain. It exposes the shipped_quantity column as the sum of detail-level shipped quantities, which is precisely the attribute users search for when reconciling outbound shipments against pick confirmations and order lines.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view references three base objects, all accessed via APPS synonyms:

• SO_PICKING_LINES_ALL — the picking line header-level table (aliased PL), providing order line, inventory item, ship method, and component information.
• SO_PICKING_LINE_DETAILS — the detail table (aliased PLD), holding schedule date, requested quantity, shipped quantity, delivery, and departure reference.
• WSH_DEPARTURES — the departure table (aliased DP), supplying actual departure date; joined with an outer (+) operator so picking lines without a departure are not eliminated.

The join is PL.PICKING_LINE_ID = PLD.PICKING_LINE_ID with the departure outer-joined on the detail row's departure_id. A filter restricts output to picking headers equal to zero or headers with a positive shipped quantity on the picking line, effectively suppressing header-level rows already rolled up elsewhere.

Key Columns

• PICKING_LINE_ID / PICKING_HEADER_ID — keys linking the row back to the picking line and its header.
• ORDER_LINE_ID / LINE_DETAIL_ID — linkage to the originating order line and detail.
• REQUESTED_QUANTITY — sum of detail-level requested quantities for the grouping.
• SHIPPED_QUANTITY — sum of detail-level shipped quantities; the primary reconciliation measure for shipped-versus-requested analysis.
• SCHEDULE_DATE / LATEST_ACCEPTABLE_DATE — coalesced from detail or picking line, reflecting scheduled and deadline dates.
• WAREHOUSE_ID, INVENTORY_ITEM_ID, CUSTOMER_ITEM_ID — warehouse and item identification.
• DELIVERY, ACTUAL_DEPARTURE_DATE — delivery name and departure date from WSH_DEPARTURES.
• COMPONENT_SEQUENCE_ID / COMPONENT_CODE / CONFIGURATION_ITEM_FLAG — support for configured or component items.

Common Use Cases and Queries

Typical scenarios include verifying pick-confirmed quantities against shipped quantities, reporting outstanding picks, and auditing shipment activity by warehouse or delivery.

Shipping reconciliation:

SELECT picking_line_id, order_line_id,
       requested_quantity, shipped_quantity
FROM   apps.wsh_picking_upgrade_v
WHERE  shipped_quantity > 0
ORDER BY order_line_id;

Warehouse-level shipped totals:

SELECT warehouse_id,
       SUM(requested_quantity) requested,
       SUM(shipped_quantity)   shipped
FROM   apps.wsh_picking_upgrade_v
GROUP BY warehouse_id;

Departure schedule check:

SELECT delivery, actual_departure_date, schedule_date,
       shipped_quantity
FROM   apps.wsh_picking_upgrade_v
WHERE  delivery IS NOT NULL
ORDER BY actual_departure_date;