Search Results movement_id




Overview
Explore in AI Chat

Overview

The SO_PICKING_LINES view is an Oracle E-Business Suite Order Entry (OE) reporting object owned by the APPS schema and documented with the notation "10SC ONLY." This designation reflects a legacy, restricted-scope construct associated with an earlier release lineage (Release 10 / Supply Chain context) rather than a general-purpose interface for the Order Management fulfillment flow in Release 12.1.1 or 12.2.2. The view is registered in the ETRM metadata with a status of VALID and exposes picking line attributes drawn from the picking batch and pick release tables, including requested, shipped, cancelled, and invoiced quantities at the picking-line granularity.

Functionally, the view presents a multi-org–filtered projection of picking line records, allowing external reads and reports to retrieve picking activity without directly accessing the underlying transactional table. It is important to note that the object is not part of the standard, documented Order Management public APIs for Release 12; administrators should treat it as an internal or residual artifact and validate its continued use before depending on it in reports, interfaces, or conversions.

Underlying Base Objects

According to the ETRM documentation, the view is defined as a restricted SELECT over a single referenced base object: SO_PICKING_LINES_ALL, accessed through a synonym. The view text performs no joins, unions, or aggregations; it projects a defined column list directly from SO_PICKING_LINES_ALL and applies a WHERE clause that enforces multi-org security.

The multi-org predicate uses USERENV('CLIENT_INFO') to derive the current operating unit identifier from the first ten characters of client information, comparing it against the ORG_ID column of the base table. Because the filter is embedded in the view definition itself, any query executed through the view is automatically restricted to the organization context established by the session's client information. Rows whose ORG_ID is null are treated with a default value of -99, which limits their visibility under normal operating unit contexts.

Key Columns

The view exposes several categories of attributes that mirror the columns of SO_PICKING_LINES_ALL:

Common Use Cases and Queries

Because the view is documented as restricted ("10SC ONLY"), its practical use in a Release 12 implementation is limited. Where it remains valid and enabled, it can support ad hoc reporting for historical picking activity and reconciliation of quantities between pick release, shipment, and invoicing. Typical scenarios include auditing shipped versus cancelled quantities by warehouse and identifying picking lines that remain open, unpicked, or awaiting confirmation.

A representative query counting allocation and shipment variance by warehouse follows:

SELECT warehouse_id,
       order_line_id,
       requested_quantity,
       shipped_quantity,
       cancelled_quantity,
       (requested_quantity - shipped_quantity - cancelled_quantity) AS open_qty,
       date_requested
FROM   apps.so_picking_lines
WHERE  included_item_flag = 'Y'
ORDER  BY warehouse_id, date_requested;

Because the multi-org predicate is embedded in the view, results are automatically scoped to the operating unit identified in the session's client information; callers running outside a properly initialized session, particularly concurrent or third-party integrations, may not see expected rows. For new development on Release 12.1.1 or 12.2.2, the supported Order Management tables and APIs should be used in preference to this view, and any existing dependency on SO_PICKING_LINES should be reviewed against the documented "10SC ONLY" restriction before remediation.