Search Results original_requested_quantity




Overview
Explore in AI Chat

Overview

ICX_SO_PICKING_HDRS_LINES_V is a reporting and integration view within the Oracle iProcurement (ICX) product family, described in the ETRM repository as the "Order Entry Picking Lines View." It presents a denormalized, read-only projection that joins picking header and picking line information from Oracle Order Management/Shipping with item master attributes and freight method details. The view is intended to expose a combined header-and-line record set so that downstream consumers — iProcurement requisition/picking flows, custom reports, and interface programs — can retrieve picking data without directly navigating the underlying transactional tables.

A notable characteristic of this view, as documented in the ETRM metadata, is the notation "Not implemented in this database." This indicates that the object is defined in the application dictionary but is not instantiated as a physical database object in the reference environment. Consequently, the view text serves primarily as a specification of intent, and any deployment must verify the object's existence before querying it.

Underlying Base Objects

The view text identifies four referenced base objects through outer and inner joins:

The join predicate between MTL_SYSTEM_ITEMS and the picking lines uses an NVL against WAREHOUSE_ID at header or line level, meaning item attributes are resolved against the line warehouse when present, otherwise the header warehouse. The ETRM 12.2.2 metadata records no explicitly documented base objects, so the join structure above must be treated as authoritative from the view definition itself.

Key Columns

The view exposes a wide column set spanning both headers and lines. Header-derived columns include PICKING_HEADER_ID, BATCH_ID, ORDER_HEADER_ID, STATUS_CODE, PICK_SLIP_NUMBER, WAYBILL_NUM, PICKED_BY_ID, PACKED_BY_ID, WEIGHT, WEIGHT_UNIT_CODE, NUMBER_OF_BOXES, SHIP_METHOD_CODE, and the DATE_RELEASED, DATE_SHIPPED, DATE_CONFIRMED, and EXPECTED_ARRIVAL_DATE timestamps.

Line-derived columns include PICKING_LINE_ID, SEQUENCE_NUMBER, ORDER_LINE_ID, COMPONENT_CODE, COMPONENT_RATIO, REQUESTED_QUANTITY, ORIGINAL_REQUESTED_QUANTITY, SHIPPED_QUANTITY, CANCELLED_QUANTITY, INVOICED_QUANTITY, INVENTORY_ITEM_ID, WAREHOUSE_ID, SHIP_TO_SITE_USE_ID, SHIP_TO_CONTACT_ID, SHIPMENT_PRIORITY_CODE, INVENTORY_STATUS, UNIT_CODE, SCHEDULE_DATE, DEMAND_CLASS_CODE, CONFIGURATION_ITEM_FLAG, LATEST_ACCEPTABLE_DATE, and MOVEMENT_ID. Item master contributes ITEM_DESCRIPTION, PRIMARY_UOM_CODE, and ITEM_URL, while ORG_FREIGHT contributes SHIP_METHOD_URL.

The column most relevant to the search term weight_unit_code is WEIGHT_UNIT_CODE, sourced from the picking header. It holds the unit of measure applicable to the WEIGHT column on the same header, allowing reports to interpret shipment weight consistently across carriers and regions.

Common Use Cases and Queries

Typical uses include iProcurement receiving and shipment reporting, pick slip analysis, and reconciliation of shipped versus requested versus invoiced quantities. A representative query filtering on the searched attribute follows:

  • SELECT PICK_SLIP_NUMBER, WAYBILL_NUM, WEIGHT, WEIGHT_UNIT_CODE, SHIP_METHOD_CODE, ITEM_DESCRIPTION, SHIPPED_QUANTITY FROM ICX_SO_PICKING_HDRS_LINES_V WHERE WEIGHT_UNIT_CODE = 'LB' ORDER BY PICK_SLIP_NUMBER, SEQUENCE_NUMBER;
  • SELECT PICKING_HEADER_ID, ORDER_HEADER_ID, STATUS_CODE, DATE_SHIPPED FROM ICX_SO_PICKING_HDRS_LINES_V WHERE DATE_SHIPPED >= TRUNC(SYSDATE) - 30;

Because the object is documented as not implemented, implementers should confirm availability in the target instance and, where absent, recreate the view from the supplied text. All access should remain read-only, as the view carries no DML semantics.