Search Results to_requested_date

Overview

WSHFV_PICK_RELEASE_RULE is a reporting view in the Oracle E-Business Suite Order Entry (OE) module that exposes the configuration and definition data of picking rules used by the shipping and release process. It presents a denormalized, human-readable projection of the underlying SO_PICKING_RULES base table, joining descriptive attributes from order headers, customers, ship methods, order types, item groups, inventory items, and pick slip rules so that picking rule definitions can be queried without manually resolving foreign keys.

The view is classified in ETRM as "Retrofitted," indicating that it was carried forward in the 12.1.1/12.2.2 code line to maintain compatibility with earlier releases and to support reporting and integration consumers that depend on its column set. In the documentation metadata provided, the view is noted as "Not implemented in this database," meaning the physical object is not deployed in every environment; where it exists, it is typically used for read-only analysis of picking rule definitions rather than for transactional processing.

The view plays a supporting role in shipping execution and release-rule analysis, providing the parameters a user configured for automatic picking and release, such as date ranges, priorities, and flags.

Underlying Base Objects

The documented view definition is constructed primarily over SO_PICKING_RULES (aliased SPR), with outer joins to descriptive reference tables. The documented base objects are:

• SO_PICKING_RULES (SPR) — the primary driving table holding the picking rule definition.
• SO_HEADERS_ALL (SH) — supplies the order number for the header.
• ORG_FREIGHT (OGF) — supplies the ship method description.
• SO_ORDER_TYPES_ALL (SOT) — supplies the order type name.
• RA_CUSTOMERS (RC) — supplies the customer name.
• MTL_PARAMETERS (ORG) — supplies the warehouse organization code.
• RA_SITE_USES_ALL (SU) — supplies the ship-to location.
• SO_ITEM_GROUPS (SIG) — supplies the item group name.
• MTL_SYSTEM_ITEMS (MSI) — supplies the item description.
• WSH_PICK_SLIP_RULES (WPSR) — supplies the pick slip rule name.

All reference tables are joined with the Oracle outer-join operator (+) against SPR, so the picking rule row is always returned even when descriptive lookups are absent. Note that the documentation excerpt does not include the final join predicate on WSH_PICK_SLIP_RULES.

Key Columns

The view exposes identification, audit, and configuration columns. Among the most significant are PICKING_RULE, the rule identifier, and the standard 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, which support change tracking and concurrent program tracing.

Rule behavior is captured by flags and parameters: BACKORDERS_ONLY_FLAG, SHIPMENT_PRIORITY_CODE, EXISTING_RSVS_ONLY_FLAG, PARTIAL_ALLOWED_FLAG, INCLUDE_PLANNED_LINES_FLAG, and AUTOCREATE_DELIVERY_FLAG. Dates controlling rule validity include ACTIVE_START_DATE and ACTIVE_END_DATE, plus FROM_REQUESTED_DATE and TO_REQUESTED_DATE, which bound the requested-date window and correspond directly to the "to_requested_date" search term. Related pairs include FROM_SCHEDULED_SHIPMENT_DATE and TO_SCHEDULED_SHIPMENT_DATE.

Descriptive columns include ORDER_NUMBER, ORDER_TYPE_NAME, ORGANIZATION_CODE, CUSTOMER_NAME, SHIP_TO, SHIP_METHOD, ITEM_GROUP_NAME, ITEM_DESCRIPTION, and PICK_SLIP_RULE_NAME, enabling self-contained reporting without additional joins.

Common Use Cases and Queries

Typical uses include reviewing picking rule configuration, auditing date-range parameters such as requested-date windows, and supporting integration extraction of release-rule metadata. A basic query filtering on the requested-date boundary is:

• To list rules whose requested-date window ends on or after a given date: SELECT picking_rule, to_requested_date, partial_allowed_flag, existing_rsvs_only_flag FROM wshfv_pick_release_rule WHERE to_requested_date >= SYSDATE;
• To report the full descriptive profile of each rule: SELECT picking_rule, order_number, order_type_name, organization_code, customer_name, ship_to, ship_method, item_description, pick_slip_rule_name, from_requested_date, to_requested_date FROM wshfv_pick_release_rule ORDER BY picking_rule;
• To audit active rules by warehouse: SELECT organization_code, picking_rule, active_start_date, active_end_date, autcreate_delivery_flag FROM wshfv_pick_release_rule WHERE organization_code = :org;

Because the object is documented as retrofitted and not implemented in every database, consumers should verify its existence before reliance and treat it as read-only. Its outer-join construction ensures rules are reported even when descriptive attributes are null.