Results for “auto_pick_confirm_flag”

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

Overview

WSH_PICKING_BATCHES is a Shipping Execution (WSH) transaction table in Oracle E-Business Suite 12.1.1 and 12.2.2 that persists picking batch definitions. A picking batch is the runtime grouping mechanism by which Oracle Shipping consolidates delivery details into a single, ordered wave of picking work, applying grouping and sequencing rules so that warehouse personnel move through a subinventory in an efficient path. Each row represents one batch header, together with the selection criteria, defaults, flags, and rules that governed its creation and release. The table is owned by the WSH schema and contains 98 documented columns in the 12.2.2 physical schema.

In Data Vault terms, the mined FK structure classifies this object heuristically as a link. This is a modeling suggestion rather than a physical characteristic: the table sits at the intersection of delivery details, deliveries, trips, trip stops, picking rules, and order attributes, and thus behaves as a relationship record between those business hubs. The primary key WSH_PICKING_BATCHES_PK (BATCH_ID) is the surrogate identifier, and the unique index WSH_PICKING_BATCHES_U1 (BATCH_ID) enforces it, while WSH_PICKING_BATCHES_U2 (NAME) provides the documented business-key candidate for the batch name.

Key Information Stored

The most operationally significant columns fall into three groups.

• Identity: BATCH_ID (surrogate primary key), NAME (unique, user-facing batch identifier), SELECTED_BATCH_ID, and PLANNED_FLAG.
• Selection and scope criteria: ORDER_HEADER_ID, ORDER_LINE_ID, DELIVERY_ID, DELIVERY_DETAIL_ID, TRIP_ID, TRIP_STOP_ID, CUSTOMER_ID, SHIP_TO_LOCATION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, SUBINVENTORY, PICK_FROM_SUBINVENTORY, PICK_FROM_LOCATOR_ID, SHIP_METHOD_CODE, CARRIER_ID, ORDER_TYPE_ID, SHIP_SET_NUMBER, and the date-range pairs FROM_REQUESTED_DATE/TO_REQUESTED_DATE, FROM_SCHEDULED_SHIP_DATE/TO_SCHEDULED_SHIP_DATE, PICKUP_DATE_LO/HI, and DROPOFF_DATE_LO/HI.
• Processing behavior and defaults: PICK_GROUPING_RULE_ID, PICK_SEQUENCE_RULE_ID, AUTODETAIL_PR_FLAG, AUTO_PICK_CONFIRM_FLAG, PARTIAL_ALLOWED_FLAG, INCLUDE_PLANNED_LINES, AUTOCREATE_DELIVERY_FLAG, AUTO_SEND_DOC_FLAG, AUTOPACK_FLAG, SHIP_CONFIRM_RULE_ID, ALLOCATION_METHOD, CROSSDOCK_CRITERIA_ID, ZONE_ID, REGION_ID, DEFAULT_STAGE_SUBINVENTORY, and DEFAULT_STAGE_LOCATOR_ID.
• Audit and extensibility: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID, PROJECT_ID, TASK_ID, and the ATTRIBUTE_CATEGORY/ATTRIBUTE1–15 descriptive flexfield columns.

Common Use Cases and Queries

Typical reporting joins batch headers to deliveries and delivery details to answer "what did this wave pick?" and "how many batches remain open?". A representative query pattern follows.

• Locate a batch by business key: SELECT batch_id, name FROM wsh_picking_batches WHERE name = :p_name; (resolves through WSH_PICKING_BATCHES_U2).
• Explode batch contents: join WSH_PICKING_BATCHES to WSH_DELIVERY_DETAILS on DELIVERY_DETAIL_ID, or to WSH_NEW_DELIVERIES on DELIVERY_ID.
• Wave effectiveness reporting: group by PICK_GROUPING_RULE_ID and PICK_SEQUENCE_RULE_ID to evaluate whether rules are producing balanced work.
• Trip consolidation checks: join TRIP_ID and TRIP_STOP_ID to WSH_TRIPS and WSH_TRIP_STOPS to confirm batches align with planned stops.
• Automation auditing: filter on AUTODETAIL_PR_FLAG, AUTO_PICK_CONFIRM_FLAG, or AUTOCREATE_DELIVERY_FLAG to distinguish manually created batches from automated ones.

Related Objects

• WSH_DELIVERY_DETAILS — referenced via DELIVERY_DETAIL_ID.
• WSH_NEW_DELIVERIES — referenced via DELIVERY_ID.
• WSH_TRIPS — referenced via TRIP_ID.
• WSH_TRIP_STOPS — referenced via TRIP_STOP_ID.
• WSH_PICK_GROUPING_RULES — referenced via PICK_GROUPING_RULE_ID.
• WSH_PICK_SEQUENCE_RULES — referenced via PICK_SEQUENCE_RULE_ID.
• WSH_SHIP_CONFIRM_RULES — referenced via SHIP_CONFIRM_RULE_ID.
• WMS_ZONES_B — referenced via ZONE_ID.
• SO_ORDER_TYPES_115_ALL — referenced via ORDER_TYPE_ID.

These relationships are enforced as foreign keys from WSH_PICKING_BATCHES to the target tables listed above, making the batch a child record in each case and confirming its role as a link between picking work and the delivery, trip, and order entities it services.