Search Results bo_picking_line_id




Overview

SO_PICKING_LINES_ALL is the OE (Order Entry) schema table that stores picking line records in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Each row represents a single request to move a quantity of material from a warehouse to satisfy a specific order line during the pick-release and ship-confirm cycle. The table is the operational anchor of the picking and shipping sub-process: it is created when pick release generates picking headers and lines, is updated as confirm ship transactions flow through the shipping execution module, and is consumed by inventory, costing, and interfacing components that translate picks into material transactions. Because all organization-specific picking data is consolidated, the ALL suffix reflects a multi-org structure governed by ORG_ID.

From a heuristic Data Vault modeling perspective, this object leans toward a hub classification. Its primary key, column PICKING_LINE_ID, is a stable, unique business identifier suitable as a hub business key. Foreign keys such as ORDER_LINE_ID and PICKING_HEADER_ID naturally serve as link references to other hubs, and the many descriptive columns (quantities, dates, flags) would be modeled as satellite attributes on that hub.

Key Information Stored

The surrogate primary key is PICKING_LINE_ID, enforced by the SO_PICKING_LINES_PK constraint and complemented by the unique index SO_PICKING_LINES_U1 on the same column, which makes it the principal business-key candidate.

Common Use Cases and Queries

Typical scenarios include pick-release status reporting, shipped-not-invoiced reconciliation, and open pick-line aging. A frequent query joins picking lines to their order lines and headers to reconcile requested versus shipped quantities:

SELECT l.PICKING_LINE_ID, l.ORDER_LINE_ID, l.WAREHOUSE_ID, l.REQUESTED_QUANTITY, l.SHIPPED_QUANTITY, l.CANCELLED_QUANTITY FROM SO_PICKING_LINES_ALL l WHERE l.ORG_ID = :org_id AND l.SHIPPED_QUANTITY < l.REQUESTED_QUANTITY;

Another pattern traces a picking line to the inventory material transactions it produced by joining MOVEMENT_ID back to MTL_MATERIAL_TRANSACTIONS, or identifies lines awaiting ship confirmation using DATE_CONFIRMED and the interface status columns RA_INTERFACE_STATUS and SERVICE_INTERFACE_STATUS. Reporting on the Oracle India localization frequently requires joining PICKING_LINE_ID to JAI_OM_OE_RMA_LINES to map returns back to their originating picks.

Related Objects