Search Results group_by_delivery_flag




Overview
Explore in AI Chat

Overview

APPS.WSHFV_PICK_LINE_GROUPING_RULE is an Oracle E-Business Suite compatibility view that exposes the pick-line grouping configuration defined for picking rules in Oracle Warehouse Management and Oracle Shipping Execution. The view surfaces the criteria by which pick slip lines are consolidated during wave and pick release processing, allowing the shipping and warehouse modules to group demand lines into a single pick slip according to business priorities such as order number, subinventory, customer, carrier, shipment priority, departure, and delivery.

In 12.1.1 and 12.2.2 the object retains the "FV" naming convention characteristic of older forms-and-views interfaces, indicating that it was originally built to back an Oracle Forms screen and is now retained as a stable, backwards-compatible query surface. The view is a read-oriented projection over the base rules table and does not store data itself, so it is safe for reporting, integration extracts, and validation logic.

For users searching on the term "group_by_ship_priority_flag", this view is the relevant object: the column is exposed here under the alias GROUP_BY_SHIP_PRIORITY_FLAG, derived from the base column SHIPMENT_PRIORITY_FLAG in WSH_PICK_SLIP_RULES.

Underlying Base Objects

Per the ETRM metadata, the view is defined over a single referenced base object: the synonym WSH_PICK_SLIP_RULES. The underlying table is WSH_WSH_PICK_SLIP_RULES in the WSH (Shipping Execution) schema, which stores one row per named pick slip rule, including its grouping flags, active date range, and standard WHO audit columns.

The view applies only column aliasing — it renames the base table's *_FLAG columns to the GROUP_BY_* naming convention used by the grouping-rule UI — and performs no joins, unions, or predicate filtering. As a result, one row in WSH_PICK_SLIP_RULES maps directly to one row in WSHFV_PICK_LINE_GROUPING_RULE, and the view inherits the base table's indexes, constraints, and audit trigger behavior.

Key Columns

Common Use Cases and Queries

Typical uses include auditing which rules enable shipment-priority grouping, driving custom pick release logic, and reconciling configuration between environments.

  • Locate rules that group by shipment priority:
SELECT pick_slip_rule_id, name, group_by_ship_priority_flag
FROM   apps.wshfv_pick_line_grouping_rule
WHERE  group_by_ship_priority_flag = 'Y';
  • List all active grouping rules with their grouping criteria:
SELECT name,
       group_by_order_number_flag, group_by_subinventory_flag,
       group_by_customer_flag, group_by_carrier_flag,
       group_by_ship_priority_flag, group_departure_flag,
       group_by_delivery_flag
FROM   apps.wshfv_pick_line_grouping_rule
WHERE  TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE+1);
  • Audit recent configuration changes:
SELECT name, last_update_date, last_updated_by, request_id
FROM   apps.wshfv_pick_line_grouping_rule
ORDER BY last_update_date DESC;

Because the view performs no filtering, any query against it can be rewritten directly against WSH_PICK_SLIP_RULES; use the view when aligning with Oracle's supported API surface or when maintaining portability between 12.1.1 and 12.2.2.