Search Results pick_schedule_date

Overview

WSHBV_PICK_LINE_DETAIL is an APPS-owned database view in Oracle E-Business Suite, registered under the Order Entry (OE) product family. Its status is documented as VALID. The object is flagged in the ETRM metadata as a retrofitted artifact, indicating it was reconstructed or re-registered during the upgrade path spanning Oracle EBS 12.1.1 and 12.2.2 rather than authored as a net-new 12.2.x deliverable. Functionally, it exposes the detail-level picking records used by Oracle Shipping Execution and Order Management to track what is being picked at the container, lot, revision, and serial granularity.

The view presents a flattened, read-friendly projection of the picking line detail entity. It includes the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), the concurrent request context columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE), and the descriptive business attributes of each pick detail row. Its most notable characteristic is a set of column aliases that rename underlying source columns to clearer public names — SCHEDULE_DATE is surfaced as PICK_SCHEDULE_DATE, SCHEDULE_LEVEL as SCHEDULE_CONTROL_LEVEL, TRANSACTABLE_FLAG as INVENTORY_TRANSACTABLE_FLAG, DPW_ASSIGNED_FLAG as DEPARTURE_PLAN_ASSIGNED_FLAG, and LOAD_SEQ_NUMBER as LOAD_SEQUENCE_NUMBER.

Underlying Base Objects

The view is defined over a single documented base object: SO_PICKING_LINE_DETAILS, referenced through a synonym in the APPS schema as SPLD. The view text is a straightforward SELECT of forty columns from that table with no joins, unions, or derived expressions. Because it is a thin pass-through over SO_PICKING_LINE_DETAILS, WSHBV_PICK_LINE_DETAIL carries no independent storage and reflects the current committed state of the base table at query time.

This relationship means that the view is dependent on the structure of SO_PICKING_LINE_DETAILS remaining intact. Customizations querying the view inherit the base table's indexing, partitioning (where applicable), and concurrency behavior. Because it resides in the Shipping Execution (WSH) schema naming convention but is owned by APPS, read privileges are typically granted through standard EBS responsibility and GRANT mechanisms rather than schema-level direct access.

Key Columns

• PICKING_LINE_DETAIL_ID — Primary key of the picking line detail record.
• PICKING_LINE_ID — Foreign key to the parent picking line.
• WAREHOUSE_ID — Organization identifier for the warehouse performing the pick.
• REQUESTED_QUANTITY / SHIPPED_QUANTITY — The demanded quantity versus the quantity actually shipped against the detail.
• SERIAL_NUMBER / REVISION / SUBINVENTORY / INVENTORY_LOCATION_ID — Material control attributes identifying exactly what was picked.
• CUSTOMER_REQUESTED_LOT_FLAG — Flag indicating whether the customer mandated a specific lot; central to lot-selection and reservation logic.
• RELEASED_FLAG / RESERVABLE_FLAG / INVENTORY_TRANSACTABLE_FLAG — Status flags governing whether the detail may be released, reserved, or transacted.
• PICK_SCHEDULE_DATE / SCHEDULE_CONTROL_LEVEL / SCHEDULE_STATUS_CODE — Scheduling and control attributes aliased from SCHEDULE_* source columns.
• DEMAND_ID / DEMAND_CLASS_CODE / SUPPLY_SOURCE_TYPE / SUPPLY_SOURCE_HEADER_ID — Demand and supply sourcing context.
• DELIVERY_ID / DEPARTURE_ID / DEPARTURE_PLAN_ASSIGNED_FLAG / LOAD_SEQUENCE_NUMBER — Outbound logistics linkage.
• MASTER_CONTAINER_ITEM_ID / DETAIL_CONTAINER_ITEM_ID / CONTAINER_ID / MOVEMENT_ID / TRANSACTION_TEMP_ID — Container and inventory movement tracking.
• PICK_SLIP_NUMBER — Printed pick slip reference.

Common Use Cases and Queries

The view is primarily used for operational reporting and integration extracts around pick confirmation, container packing, lot control, and shipment staging. A frequent requirement involves identifying picking details where the customer requested a specific lot:

SELECT PICKING_LINE_DETAIL_ID, PICKING_LINE_ID, WAREHOUSE_ID, SERIAL_NUMBER, REVISION, SUBINVENTORY, REQUESTED_QUANTITY, SHIPPED_QUANTITY FROM APPS.WSHBV_PICK_LINE_DETAIL WHERE CUSTOMER_REQUESTED_LOT_FLAG = 'Y' AND SHIPPED_QUANTITY < REQUESTED_QUANTITY;

Other practical scenarios include locating unpicked or partially picked details by warehouse, reconciling shipped quantities against requested quantities for a delivery, and validating container or movement assignments prior to ship confirmation. Because the view returns no joined descriptive names, reports commonly join it back to WSH_PICKING_LINES, delivery, and inventory item master views to enrich results. All queries should be filtered by WAREHOUSE_ID and date ranges to avoid full-table scans against the underlying SO_PICKING_LINE_DETAILS table.