Search Results shipment_priority_flag

Overview

WSHBV_PICK_LINE_GROUPING_RULE is an APPS-owned database view in Oracle E-Business Suite, classified under the Order Entry (OE) product family. It exposes pick-slip grouping rule definitions used by Oracle Shipping Execution to determine how pick lines are consolidated onto a pick slip during the pick release and pick confirmation process. In release 12.1.1 and 12.2.2 the view carries a "Retrofitted" status, indicating it was recreated or preserved to maintain backward compatibility across the multi-org and OAF-based architecture changes introduced with the R12 technology stack.

From a reporting and integration standpoint, the view provides a stable, read-only projection of the pick-slip rule configuration stored in the underlying base table. It presents the rule identifiers, descriptive text, and the individual grouping flags that control whether pick lines are grouped by order number, subinventory, customer, ship-to address, carrier, shipment priority, departure, or delivery. Because the view renames several columns through column aliases, it serves as a compatibility layer for external reports, interfaces, and custom concurrent programs that reference the legacy naming convention rather than the physical column names.

Underlying Base Objects

The view is defined over a single base object, WSH_PICK_SLIP_RULES, referenced through an APPS synonym. According to the ETRM metadata the join is a straightforward projection: the view selects a defined subset of columns and applies aliases to reconcile naming differences between the view and the base table. The physical column ORDER_NUMBER_FLAG is exposed as GROUPB_BY_ORDER_NUMBER_FLAG, SUBINVENTORY_FLAG as GROUP_BY_SUBINVENTORY_FLAG, CUSTOMER_FLAG as GROUP_BY_CUSTOMER_FLAG, CARRIER_FLAG as GROUP_BY_CARRIER_FLAG, SHIPMENT_PRIORITY_FLAG as GROUP_BY_SHIP_PRIORITY_FLAG, DEPARTURE_FLAG as GROUP_DEPARTURE_FLAG, and DELIVERY_FLAG as GROUP_BY_DELIVERY_FLAG.

Notably, the SHIP_TO_FLAG column is exposed without an alias, retaining its physical name. Because the view contains no joins, filters, or aggregation, it behaves as a direct synonym-like projection of the pick slip rules table, allowing both seeded and user-defined grouping rules to be queried uniformly.

Key Columns

• PICK_SLIP_RULE_ID — Primary identifier for the grouping rule.
• NAME / DESCRIPTION — User-facing rule name and description.
• SHIP_TO_FLAG — Indicates whether pick lines are grouped by ship-to location. This is the column most relevant to users searching on "ship_to_flag".
• GROUPB_BY_ORDER_NUMBER_FLAG — Grouping by sales order number.
• GROUP_BY_SUBINVENTORY_FLAG — Grouping by subinventory.
• GROUP_BY_CUSTOMER_FLAG — Grouping by customer.
• GROUP_BY_CARRIER_FLAG — Grouping by carrier.
• GROUP_BY_SHIP_PRIORITY_FLAG — Grouping by shipment priority.
• GROUP_DEPARTURE_FLAG / GROUP_BY_DELIVERY_FLAG — Grouping by departure and delivery.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating for the rule.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID.

Common Use Cases and Queries

Typical usage includes diagnosing why pick lines were consolidated or split, validating rule configuration for a warehouse, and feeding grouping logic into custom shipping reports. A representative query listing active rules grouped by ship-to is:

SELECT pick_slip_rule_id, name, ship_to_flag, group_by_customer_flag, group_by_carrier_flag FROM apps.wshbv_pick_line_grouping_rule WHERE ship_to_flag = 'Y' AND (end_date_active IS NULL OR end_date_active > SYSDATE) ORDER BY name;

The view also supports integration extracts where grouping flags must be reconciled against Oracle Warehouse Management or Transportation Management configuration, and it provides an audit-friendly read for troubleshooting pick release behavior.