Results for “document_set_name”

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

Overview

WSHFV_PICKING_RULES is a full Business Intelligence System (BIS) business view owned by the APPS schema within the WSH – Shipping Execution product family. It exposes the configuration and operational attributes of picking rules defined in Oracle EBS Warehouse Management and Shipping Execution. A picking rule (WSH_PICKING_RULES) determines how the system selects and sequences inventory for outbound picking, including which subinventory and locator to pick from, whether backorders are included, whether deliveries are autocreated, and how picks are grouped and sequenced. This view is one of several WSHFV_* BIS views shipped for ad hoc reporting, Discoverer workbooks, and third-party integration extracts, and it is maintained in both EBS 12.1.1 and 12.2.2 with status VALID.

The object is significant to users searching for subinventory description because it resolves the numeric subinventory identifier on a picking rule into the human-readable description maintained in MTL_SECONDARY_INVENTORIES. This makes the view suitable for reports that must present business-friendly subinventory names instead of codes.

Underlying Base Objects

WSHFV_PICKING_RULES is defined over the WSH_PICKING_RULES base table (aliased WPR) joined to a set of supporting master and reference tables. The documented referenced base objects are:

• WSH_PICKING_RULES – the master picking rule definitions.
• WSH_REPORT_SETS – report set name (DOCUMENT_SET_NAME).
• WSH_PICK_GROUPING_RULES – pick grouping rule name.
• WSH_PICK_SEQUENCE_RULES – pick sequence rule name.
• WSH_LOCATIONS – ship-from and ship-to location identifiers and location codes.
• MTL_SECONDARY_INVENTORIES – subinventory descriptions (joined three times as SUBINV1, SUBINV2, SUBINV3).
• MTL_ITEM_LOCATIONS – ship-from/ship-to location references.
• MTL_SYSTEM_ITEMS – inventory item reference.
• OE_ORDER_HEADERS_ALL – order number.
• OE_TRANSACTION_TYPES_ALL – order type code.
• HZ_PARTIES / HZ_CUST_ACCOUNTS – customer name.
• PA_PROJECTS_ALL / PA_TASKS – project name and task number.

The view text also embeds special BIS tokens such as '_KF', '_LA', and '_DF', which signal flexible key, lookup, and descriptive flexfield metadata to the Oracle Business Intelligence reporting layer.

Key Columns

• PICKING_RULE_ID / NAME – primary key and rule name.
• DEFAULT_STAGE_SUBINVENTORY and DEFAULT_STAGE_DESCRIPTION – the default staging subinventory code and its description (SUBINV1).
• PICK_FROM_SUBINVENTORY and PICK_FROM_DESCRIPTION – the subinventory to pick from and its description (SUBINV2).
• SUBINVENTORY and SUBINV_DESCRIPTION – the additional subinventory criterion and its description (SUBINV3). This is the column most relevant to the "subinventory description" search.
• SHIP_FROM_LOCATION / SHIP_TO_LOCATION – location codes from WSH_LOCATIONS and MTL_ITEM_LOCATIONS.
• DOCUMENT_SET_NAME, PICK_GROUPING_RULE_NAME, PICK_SEQUENCE_RULE_NAME – referenced rule and report set names.
• Flags – BACKORDERS_ONLY_FLAG, AUTODETAIL_PR_FLAG, AUTO_PICK_CONFIRM_FLAG, EXISTING_RSVS_ONLY_FLAG, PARTIAL_ALLOWED_FLAG, AUTOCREATE_DELIVERY_FLAG.
• Date filters – FROM/TO REQUESTED_DATE, FROM/TO SCHEDULED_SHIP_DATE, START_DATE_ACTIVE, END_DATE_ACTIVE.
• Customer / order context – CUSTOMER_NAME, ORDER_NUMBER, ORDER_TYPE_CODE, SHIP_METHOD_CODE, PROJECT_NAME, TASK_NUMBER.

Common Use Cases and Queries

The primary use case is reporting on picking rule configuration, particularly resolving subinventory codes into descriptions for operational dashboards, audit reports, and integration extracts.

SELECT picking_rule_id,
       name,
       pick_from_subinventory,
       pick_from_description,
       subinventory,
       subinv_description
FROM   apps.wshfv_picking_rules
WHERE  organization_id = :org_id
AND    NVL(end_date_active, SYSDATE+1) > SYSDATE;

To identify rules targeting a specific subinventory by description:

SELECT name, subinventory, subinv_description
FROM   apps.wshfv_picking_rules
WHERE  UPPER(subinv_description) LIKE UPPER('%:subinv%');

Other typical scenarios include joining the view to WSH_DELIVERY_ASSIGNMENTS or WSH_NEW_DELIVERIES to determine which rule governed a shipment, and extracting rule definitions for migration between environments. Because the view is a full BIS view, it can be queried directly with standard SQL in Reports, BI Publisher, and Discoverer without additional joins for descriptions.