Search Results reorder_picking_line




Overview
Explore in AI Chat

Overview

WSH_PR_CUSTOM is a custom PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. In the documented ETRM metadata it carries the object type PACKAGE BODY and a status of VALID, indicating that the compiled body resides in the database and is available for execution. The package operates within the Oracle Shipping Execution (WSH) functional area, as reflected by its name prefix. Its purpose is to extend or supplement standard picking and release processing logic — specifically the rules that determine which order lines are eligible to be released for picking and how outstanding demand is evaluated. Because it is a custom package, it is not part of the certified Oracle application code base; instead it was created by an implementation team to satisfy business rules that the seeded release and picking logic does not cover out of the box. The API classification is recorded as OTHER, confirming that this is not a public, supported Oracle API but rather an internal customer extension.

Key Procedures and Functions

The ETRM documentation records three program units within the package body:

  • OUTSTANDING_ORDER_VALUE — Evaluates and returns a measure of open or outstanding order value. This is typically used to quantify demand that has not yet been fully shipped, allowing release or picking logic to make decisions based on remaining value rather than raw quantities.
  • PROCESS_LINES — The principal driver routine of the package. It iterates over candidate order lines and applies the custom release or eligibility logic, determining which lines should proceed through the picking and release workflow.
  • REORDER_PICKING_LINE — Handles reprocessing or re-sequencing of a picking line, supporting scenarios where a previously released or allocated line must be reconsidered by the release process.

The metadata does not document parameter lists or signatures, so the precise interface of each program unit must be confirmed by inspecting the compiled source in the database.

Tables Accessed

The package body references two documented tables through APPS synonyms:

  • SO_HEADERS_ALL — The order header table. It supplies the header-level attributes of sales orders, such as order status, customer, and ordering data, which frame the context for line-level processing.
  • SO_LINES_ALL — The order line table. This provides the individual line details — item, quantity, and line status — that the package evaluates when determining outstanding value and deciding whether a line should be processed or reordered for picking.

These tables are read as the source of order demand; the package derives its determinations from order header and line data rather than maintaining its own persistent tables.

Usage Notes

WSH_PR_CUSTOM is referenced by one other database object according to the documented dependency map, and it in turn references the standard SYS.STANDARD package. This dependency pattern suggests the package is invoked from a standard calling point — such as a shipping release or pick-confirm program, or a custom wrapper built on top of the picking workflow. Typical invocation scenarios include custom release rules that must be evaluated before lines are passed to the standard picking engine, and re-processing of picking lines that were skipped or failed. Because the package is a custom body and the metadata lists only three program units without signatures, any implementation work on it should begin by extracting the current body from the database to confirm the exact parameter lists and return types before extending or debugging the logic. Testing should be performed in a non-production environment, since the package directly influences which sales order lines become eligible for shipment.