Search Results existing_rsvs_only_flag

Overview

The APPS.WSH_PICKING_BATCHES_V view is a denormalized reporting and inquiry layer over the WSH_PICKING_BATCHES base table in the Oracle E-Business Suite Shipping Execution (WSH) module. Picking batches group eligible delivery details into a single workflow for release, picking, and confirmation, and this view exposes each batch alongside the descriptive context that operators and downstream integrations require: customer, order, warehouse, ship-to and ship-from locations, trip and stop information, and the batch selection criteria that were applied at creation time. Because the underlying WSH_PICKING_BATCHES table stores only coded identifiers, the view resolves those codes into user-facing meanings and names through joins to lookups, order management, inventory, and shipping tables.

The view is documented as VALID and is owned by APPS. Its definition carries a historical annotation referencing Bug 1924581 and HR_LOCATION changes dated 8/15/01, indicating that location resolution logic has been revised over the product lifecycle. This matters on both Oracle EBS 12.1.1 and 12.2.2, where the view remains a stable interface for batch-level reporting even though the physical tables beneath it have evolved.

Underlying Base Objects

The view is defined primarily over WSH_PICKING_BATCHES (aliased WPB), which contributes all transactional columns, descriptive flexfield columns, and primary key values. The view text additionally references WSH_REPORT_SETS for the document set name, WSH_TRIPS and WSH_TRIP_STOPS for trip and stop names, WSH_LOCATIONS for ship-to, ship-from, and stop location codes, and WSH_NEW_DELIVERIES and WSH_DELIVERY_LEGS for delivery context.

Order and customer attributes are sourced from OE_ORDER_HEADERS_ALL for the order number, OE_ORDER_TYPES_V for the order type name, OE_SETS for the ship set name, and HZ_PARTIES plus HZ_CUST_ACCOUNTS for customer name and account number. Warehouse details come from and HR_ALL_ORGANIZATION_UNITS_TL. Project references are resolved through the PJM_PROJECT package using ALL_TASK_IDTONUM and ALL_PROJ_IDTONUM. Flag meanings are decoded from OE_LOOKUPS. Finally, WSH_PICK_GROUPING_RULES and WSH_PICK_SEQUENCE_RULES are referenced base objects associated with batch rule configuration.

Key Columns

• BATCH_ID, BATCH_NAME, ROW_ID — Batch identity and the row identifier used by the Oracle Forms inquiry screen.
• BACKORDERS_ONLY_FLAG / BACKORDERS — Indicates whether the batch includes only backordered lines, with decoded meaning.
• EXISTING_RSVS_ONLY_FLAG, RESERVATION, RESERVATION_STAR — Controls whether only reserved lines are picked; the star is a report convenience marker.
• CUSTOMER_ID, CUSTOMER_NAME, ACCOUNT_NUMBER — Customer identification resolved from HZ tables.
• ORDER_NUMBER, ORDER_HEADER_ID, SHIP_SET_ID, SHIP_SET_NUMBER, ORDER_TYPE — Order and ship set context.
• WAREHOUSE_CODE, WAREHOUSE, ORGANIZATION_ID, SUBINVENTORY, PICK_FROM_SUBINVENTORY — Warehouse and staging locations.
• SHIP_TO_LOCATION, SHIP_FROM_LOCATION, DEFAULT_STAGE_SUBINVENTORY, DEFAULT_STAGE_LOCATOR_ID — Physical movement context for the pick.
• TRIP_NAME, STOP_ID, STOP_NAME, CARRIER_ID, SHIP_METHOD_CODE, SHIPMENT_PRIORITY — Transportation and routing attributes.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — Descriptive flexfield columns for customer-specific extensions.

Note that the documented view text does not expose a column named autodetail_pr_flag; no column by that name appears in the WSH_PICKING_BATCHES_V definition. Analysts searching for that term should verify whether the flag resides on WSH_PICKING_BATCHES or on a related pick-confirmation object rather than this view.

Common Use Cases and Queries

Typical use cases include batch status reporting, pick-release validation, carrier and trip consolidation reporting, and custom concurrent programs that must present batch criteria in readable form.

SELECT batch_name,
       backorders,
       reservation,
       customer_name,
       order_number,
       warehouse_code,
       ship_to_location,
       trip_name
FROM   apps.wsh_picking_batches_v
WHERE  organization_id = :p_org_id
AND    creation_date >= :p_from_date
ORDER  BY creation_date DESC;

Because the view performs numerous outer joins, queries should always be constrained by organization, batch, or date to avoid full scans. On 12.1.1 and 12.2.2 the definition is identical in structure, so reporting SQL remains portable across both releases.