Search Results include_planned_lines_flag

Overview

WSHBV_PICK_RELEASE_RULE is an APPS-owned database view in Oracle E-Business Suite, catalogued under the Order Entry (OE) product family and marked with the description "Retrofitted." The "BV" naming convention denotes a backward-compatibility or business view layer, and the view is documented as VALID in both the 12.1.1 and 12.2.2 releases. Functionally, it exposes the configuration of picking rules used by Oracle Shipping Execution and Order Management to determine how order lines are grouped, sequenced, and released for picking and shipment. The view presents a filtered column projection over the picking-rule definition table, allowing reporting tools, concurrent programs, and integration interfaces to read rule attributes without querying the base table directly.

For users searching on autocreate_delivery_flag, this view is the relevant access point: it is one of the columns exposed by WSHBV_PICK_RELEASE_RULE, carried through from the underlying SO_PICKING_RULES record.

Underlying Base Objects

The view is defined over a single base object, documented as:

• SO_PICKING_RULES — referenced through a SYNONYM in the APPS schema. This is the authoritative table in which picking and release rule definitions are stored, including rule scope, active date ranges, sequencing rule sets, and the flags that govern automation behavior.

The view text is a straightforward SELECT of the full attribute list from SO_PICKING_RULES, aliased as SPR. No joins, unions, or aggregations are present. The practical consequence is that WSHBV_PICK_RELEASE_RULE behaves as a near one-to-one projection of the base table: one row per picking-rule definition, with no row multiplication or loss. It is therefore safe to use in reporting contexts where the base table is not exposed directly to the reporting schema, and where read-only access to rule metadata is required.

Key Columns

The view exposes 34 columns. The most operationally significant include:

• AUTOCREATE_DELIVERY_FLAG — Controls whether a delivery is created automatically during the pick release or autocreate process. This is the column most frequently searched in conjunction with the view, and it directly influences whether the release workflow generates delivery records without manual intervention.
• PICKING_RULE — The identifying name of the picking rule.
• PARTIAL_ALLOWED_FLAG — Indicates whether partial quantity releases are permitted.
• BACKORDERS_ONLY_FLAG — Restricts the rule to backordered demand only.
• EXISTING_RSVS_ONLY_FLAG — Limits eligibility to lines with existing reservations.
• INCLUDE_PLANNED_LINES_FLAG — Determines whether planned (unreserved or unfulfilled) lines are included in the release.
• PICK_SLIP_RULE_ID and RELEASE_SEQ_RULE_SET_ID — Foreign references to pick-slip formatting and release sequencing rule sets.
• SHIPMENT_PRIORITY_CODE, SHIP_METHOD_CODE, SUBINVENTORY — Filtering attributes that scope the rule to specific fulfillment characteristics.
• START_DATE_ACTIVE / END_DATE_ACTIVE — The effective date envelope of the rule.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the concurrent-program columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) provide audit and lineage information.

Common Use Cases and Queries

The view is most commonly used to audit pick release automation settings and to reconcile rule configurations across environments. A typical query locating rules that auto-create deliveries is:

• SELECT picking_rule, autocreate_delivery_flag, partial_allowed_flag, include_planned_lines_flag FROM apps.wshbv_pick_release_rule WHERE autocreate_delivery_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

Additional scenarios include verifying which rule set a given pick slip rule is bound to, confirming that a rule applies to the correct warehouse or customer scope, and producing configuration evidence for change control or audit. Because the view is unaggregated and reads directly from SO_PICKING_RULES, it is appropriate for both ad hoc SQL and embedded use in custom concurrent programs or BI Publisher data templates.