Results for “arrived_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

SO_PICKING_HEADERS_ALL is an Order Entry (OE) base table that stores batch picking headers. Each row represents the header-level record of a picking activity, capturing the consolidated shipping and packing attributes associated with a picking batch and its related sales order. In the Oracle E-Business Suite release 12.1.1 and 12.2.2 data model, the table owner is the OE schema and the object status is VALID. The table sits between order management and shipping execution, acting as the header anchor for the picking lines that describe individual items to be picked, packed, and shipped.

From a heuristic Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table is keyed by its own surrogate primary key and is heavily dependent on parent entities such as SO_PICKING_BATCHES_ALL, SO_HEADERS_ALL, and WSH_DELIVERIES, with predominantly descriptive attributes (weights, box counts, dates, and status flags) rather than consisting of a pure many-to-many relationship structure. This classification is a modeling suggestion derived from the FK topology, not a physical design directive.

Key Information Stored

The table contains 48 documented columns in the 12.2.2 physical schema. The most operationally significant columns include:

• PICKING_HEADER_ID — the surrogate primary key (SO_PICKING_HEADERS_PK) and the unique index column (SO_PICKING_HEADERS_U1). This is the identifier referenced by all child tables.
• BATCH_ID — foreign key to SO_PICKING_BATCHES_ALL, linking the header to its batch-picking run.
• ORDER_HEADER_ID — foreign key to SO_HEADERS_ALL, tying the picking header to the originating sales order.
• DELIVERY_ID — foreign key to WSH_DELIVERIES, associating the pick with a shipping delivery.
• STATUS_CODE — the current lifecycle state of the picking header.
• PICK_SLIP_NUMBER — the printed pick slip reference used on the warehouse floor.
• WAYBILL_NUM — carrier waybill or tracking reference assigned to the shipment.
• PICKED_BY_ID and PACKED_BY_ID — foreign keys to FND_USER identifying the warehouse operator who picked and packed the shipment.
• SHIP_TO_SITE_USE_ID — foreign key to RA_SITE_USES_ALL identifying the ship-to address usage.
• WEIGHT and WEIGHT_UNIT_CODE — the recorded shipment weight and its unit of measure.
• NUMBER_OF_BOXES — the count of cartons or containers in the pick.
• DATE_RELEASED, DATE_SHIPPED, and DATE_CONFIRMED — the key transaction timestamps across the picking lifecycle.
• ORG_ID — the multi-org operating unit discriminator, essential for reporting and security.
• ARRIVED_FLAG and SHIP_NOTICE_SENT_FLAG — shipment notification and arrival tracking indicators.

The DFF columns ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT provide the standard descriptive flexfield extension points maintained for customer-specific data.

Common Use Cases and Queries

The primary reporting use case is tracking picking activity from batch creation through shipment confirmation. A typical query joins the header to its lines to reconstruct the pick:

SELECT h.picking_header_id, h.pick_slip_number, h.status_code, h.date_shipped, l.inventory_item_id, l.requested_quantity
FROM oe.so_picking_headers_all h, oe.so_picking_lines_all l
WHERE h.picking_header_id = l.picking_header_id
AND h.org_id = :org_id;

Warehouse productivity analysis correlates PICKED_BY_ID and PACKED_BY_ID with FND_USER to measure operator throughput. Shipping reconciliation joins DELIVERY_ID to WSH_DELIVERIES to confirm that every pick header is assigned to an outbound delivery. Order status dashboards use the ORDER_HEADER_ID join to SO_HEADERS_ALL to relate picking progress back to the sales order. Additional patterns include weight-and-box reporting for freight planning, cycle-time analysis using DATE_RELEASED against DATE_SHIPPED, and multi-org reporting filtered by ORG_ID.

Related Objects

The most significant related objects, based on the documented foreign key relationships, are:

• SO_PICKING_BATCHES_ALL — parent batch entity joined on BATCH_ID.
• SO_HEADERS_ALL — parent sales order joined on ORDER_HEADER_ID.
• WSH_DELIVERIES — delivery entity joined on DELIVERY_ID.
• RA_SITE_USES_ALL — ship-to address usage joined on SHIP_TO_SITE_USE_ID.
• FND_USER — operator identity joined on PICKED_BY_ID and PACKED_BY_ID.
• SO_PICKING_LINES_ALL — child detail lines referencing PICKING_HEADER_ID.
• SO_FREIGHT_CHARGES — freight details referencing PICKING_HEADER_ID.
• JAI_OM_WSH_LINES_ALL, JAI_OM_OE_BOND_TRXS, and JAI_OM_OE_GEN_TAXINV_T — India localization tables referencing PICKING_HEADER_ID.

This relationship topology confirms SO_PICKING_HEADERS_ALL as a header hub within the picking and shipping sub-model, serving as the join point between order, delivery, user, and localization data.