Results for “wshfv_pick_sequence_rules”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The WSHFV_PICK_SEQUENCE_RULES view is a Full BIS (Business Intelligence System) business view owned by the APPS schema in Oracle E-Business Suite. It resides in the WSH – Shipping Execution product/module and is documented as VALID under both EBS 12.1.1 and 12.2.2. Its stated purpose is to expose pick sequence rule definitions for reporting and integration consumption.
Pick sequence rules in Oracle Shipping Execution determine the order in which pick confirmations, move orders, and related picking activities are sequenced. Administrators configure priorities and sort directions across a set of business criteria, and Oracle Shipping then applies those rules when generating pick slips and sequencing warehouse tasks. This view surfaces those configuration records in a read-only, reporting-friendly form so that external tools, custom reports, and BIS-based extracts can consume them without directly querying the transactional configuration table.
The view is defined with the WITH READ ONLY clause, preventing accidental DML through the view. It is a "Full BIS Business View," meaning it exposes all relevant columns of the underlying rule header, prefixed conceptually by the WSH application short name. It is central to anyone troubleshooting picking behavior, auditing rule configuration, or building custom warehouse dashboards.
Underlying Base Objects
The view is defined over a single base object: the WSH_PICK_SEQUENCE_RULES table (referenced in ETRM 12.2.2 as a synonym pointing to the table owned by the WSH/APPS schema). The view text aliases this table as WPS:
FROM WSH_PICK_SEQUENCE_RULES WPS WITH READ ONLY
No joins, unions, or derived subqueries are present in the documented view text. The object is therefore a thin projection layer: every column returned maps one-to-one to a column on the base table, except for the injected literal '_DF:WSH:WSH_PICK_SEQUENCE_RULES:WPS' (exposed as the column "_DF"), which is a descriptive flexfield context indicator used by BIS tooling.
Because the view references the base table through a schema-level synonym, any grants or synonyms applied to WSH_PICK_SEQUENCE_RULES in the APPS schema govern access to the view data. The view is owned by APPS and inherits that schema's visibility rules.
Key Columns
The columns exposed fall into two functional groups: identity/administrative attributes and rule-configuration attributes.
- PICK_SEQUENCE_RULE_ID – Primary key of the rule; the value users typically search for when troubleshooting.
- NAME and DESCRIPTION – Human-readable identifiers for the rule.
- ORDER_ID_PRIORITY / ORDER_ID_SORT – Priority and sort direction governing sequencing by sales order.
- INVOICE_VALUE_PRIORITY / INVOICE_VALUE_SORT – Sequencing driven by invoice value.
- SCHEDULE_DATE_PRIORITY / SCHEDULE_DATE_SORT – Sequencing by schedule date.
- SHIPMENT_PRI_PRIORITY / SHIPMENT_PRI_SORT – Sequencing by shipment priority code.
- TRIP_STOP_DATE_PRIORITY / TRIP_STOP_DATE_SORT – Sequencing by trip stop date.
- START_DATE_ACTIVE / END_DATE_ACTIVE – Effective date range for the rule.
- "_DF" – Literal descriptive flexfield context string
'_DF:WSH:WSH_PICK_SEQUENCE_RULES:WPS'. - CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard audit columns inherited from the base table.
Common Use Cases and Queries
Typical scenarios include retrieving the active rule, auditing change history, and feeding warehouse dashboards. The following example returns the currently effective rules:
SELECT pick_sequence_rule_id, name, description, start_date_active, end_date_active
FROM apps.wshfv_pick_sequence_rules
WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE)+1);
To inspect the priority weighting assigned across criteria for a specific rule:
SELECT pick_sequence_rule_id, name, order_id_priority, invoice_value_priority,
schedule_date_priority, shipment_pri_priority, trip_stop_date_priority
FROM apps.wshfv_pick_sequence_rules
WHERE pick_sequence_rule_id = :rule_id;
For audit purposes, filter by the standard audit columns to identify recently modified configurations. Because the view is read-only and thin, queries are efficient and safe for reporting, extract, and integration layers, and column values are identical to those on WSH_PICK_SEQUENCE_RULES.
-
Full BIS Business View for Pick Sequence Rules.
APPS.WSHFV_PICK_SEQUENCE_RULES·↳ WSH_PICK_SEQUENCE_RULES·Explore WSH module →
-
Full BIS Business View for Pick Sequence Rules.
APPS.WSHFV_PICK_SEQUENCE_RULES·↳ WSH_PICK_SEQUENCE_RULES·Explore WSH module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
eTRM - WSH Tables and Views 12.2.2
Stores hierarchy for zones. Each region component of a zone has a record in this table.
-
eTRM - WSH Tables and Views 12.1.1
Stores hierarchy for zones. Each region component of a zone has a record in this table.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - WSH Tables and Views 12.1.1
Stores hierarchy for zones. Each region component of a zone has a record in this table.
-
eTRM - WSH Tables and Views 12.2.2
Stores hierarchy for zones. Each region component of a zone has a record in this table.