Search Results confirmed_date




Overview
Explore in AI Chat

Overview

APPS.WSHBV_PICK_LINE is a backward-compatibility view in Oracle E-Business Suite that exposes picking line information for the shipping execution and order management modules. It is defined entirely over the SO_PICKING_LINES_ALL table and functions as a renamed, denormalized projection of that base object rather than as a join or aggregation. The view preserves legacy column names that predate the WSH (Warehouse Shipping) schema realignment, allowing older reports, concurrent programs, forms, and custom integrations to continue functioning after the SO_PICKING_LINES_ALL migration. Because several columns are aliased (for example, DATE_CONFIRMED is exposed as CONFIRMED_DATE, REQUESTED_QUANTITY as CURRENT_REQUEST_QUANTITY, and MODEL_OPTION_COMPONENT_CODE), the view also shields downstream consumers from physical renames applied during the schema evolution from 11i to R12. The view is read-only with respect to application data; all DML is expected to target the underlying base table. In ETRM 12.1.1 and 12.2.2, the view remains available in the APPS schema and is documented with the single referenced base object SO_PICKING_LINES_ALL.

Underlying Base Objects

The view is defined over exactly one documented object:

  • SO_PICKING_LINES_ALL (SYNONYM) — the operational picking lines table that stores one row per order line, delivery detail, or model component scheduled for picking. The _ALL suffix confirms it is the multi-org (Operating Unit) enabled table, secured through ORG_ID.

No joins, unions, or derived subqueries appear in the view text. Every column is a direct selection or a simple rename of a column on SO_PICKING_LINES_ALL. Consequently, the view shares the base table's row count, partitioning, and indexing behavior, and no additional predicates beyond any applied by the security context are introduced.

Key Columns

The view exposes the full set of picking line attributes, including standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), concurrent program columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID), and the multi-org ORG_ID. Columns of particular analytical importance include:

Common Use Cases and Queries

Typical usage involves confirming shipments, reconciling pick quantities, and reporting on order fulfilment timing. A frequent pattern is filtering on the confirmed date for a date range within an operating unit:

  • Confirmed shipments by date: SELECT PICKING_LINE_ID, ORDER_LINE_ID, SHIPPED_QUANTITY, CONFIRMED_DATE FROM APPS.WSHBV_PICK_LINE WHERE CONFIRMED_DATE BETWEEN :from_date AND :to_date AND ORG_ID = :org_id;
  • Open picks awaiting confirmation: SELECT PICKING_LINE_ID, ORDER_LINE_ID, REQUESTED_QUANTITY FROM APPS.WSHBV_PICK_LINE WHERE CONFIRMED_DATE IS NULL AND ORG_ID = :org_id;
  • Component-level detail for configured items: selecting MODEL_OPTION_COMPONENT_CODE, MODEL_OPTION_COMPONENT_RATIO, and COMPONENT_SEQUENCE_ID alongside ORDER_LINE_ID.
  • Interface reconciliation: filtering on RECEIVABLE_INTERFACE_STATUS or INVENTORY_INT_STATUS to identify unprocessed lines.

Because the view is a thin projection, query performance matches direct queries against SO_PICKING_LINES_ALL, and existing indexes on that table apply. New development should generally target the base table or the current WSH views, while WSHBV_PICK_LINE persists for compatibility with legacy code.