Search Results load_sequence_number




Overview
Explore in AI Chat

Overview

APPS.WSHBV_PICK_LINE_DETAIL is a reporting and integration-oriented view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes detailed picking information for outbound logistics. The view is a column-renamed projection of the picking line detail data maintained by Oracle Shipping Execution, and it is intended to give downstream consumers — reports, interfaces, and custom extensions — a stable, business-friendly presentation of the underlying picking records.

The view does not modify or aggregate its source; it presents a single row per picking line detail record. Notably, it applies aliasing to several columns so that the exposed names differ from the physical column names (for example, SCHEDULE_DATE becomes PICK_SCHEDULE_DATE, SCHEDULE_LEVEL becomes SCHEDULE_CONTROL_LEVEL, TRANSACTABLE_FLAG becomes INVENTORY_TRANSACTABLE_FLAG, DPW_ASSIGNED_FLAG becomes DEPARTURE_PLAN_ASSIGNED_FLAG, and LOAD_SEQ_NUMBER becomes LOAD_SEQUENCE_NUMBER). This aliasing is the key reason a user searching for load_sequence_number is directed to this view: the underlying database column is LOAD_SEQ_NUMBER, but the view exposes it under the more descriptive name LOAD_SEQUENCE_NUMBER.

Underlying Base Objects

According to the documented metadata, the view is defined over the base object SO_PICKING_LINE_DETAILS, which is referenced through a synonym. The view text references this table with the alias SPLD, selecting columns directly from it without joins to other tables in the projection. Consequently, WSHBV_PICK_LINE_DETAIL inherits the granularity and transaction semantics of SO_PICKING_LINE_DETAILS: one row for each picking line detail, which typically corresponds to a specific lot, serial, revision, or location assignment within a picking line.

Key Columns

Common Use Cases and Queries

Typical uses include pick confirmation reports, load sequencing/loading worksheets, shipping manifestation extracts, and custom integrations that need load order. A query retrieving load sequence information for a given delivery might read:

SELECT picking_line_detail_id, picking_line_id, delivery_id, departure_id,
       load_sequence_number, requested_quantity, shipped_quantity, pick_slip_number
FROM   apps.wshbv_pick_line_detail
WHERE  delivery_id = :p_delivery_id
ORDER  BY load_sequence_number;

To list all pick details belonging to a pick slip ordered by load sequence:

SELECT pick_slip_number, load_sequence_number, serial_number,
       inventory_transactable_flag, released_flag
FROM   apps.wshbv_pick_line_detail
WHERE  pick_slip_number = :p_pick_slip
ORDER  BY load_sequence_number;

Because the view renames LOAD_SEQ_NUMBER to LOAD_SEQUENCE_NUMBER, references to load_sequence_number should target this view or its synonym alias, not the underlying table column name. When the total row count is not required, it is also common to join the view to WSH_DELIVERY_DETAILS or WSH_DELIVERIES on delivery_id for enriched shipment reporting.