Search Results p_order




Overview

WMS_SHIPPING_LOVS is an Oracle Warehouse Management (WMS) package body owned by the APPS schema that supplies list-of-values (LOV) query data for shipping and dispatch user interfaces in Oracle E-Business Suite. It is classified as an "OTHER" API, indicating it is a supporting infrastructure package rather than a public transactional API. Its role is to open weakly typed or strongly typed reference cursors (t_genref) that return candidate order, order line, manifest, and pick-slip records for selection in WMS shipping forms. The package header carries version information from WMSSHPLB.pls, with the latest documented revision dated 2006/09/20, reflecting a stable, low-change module. It is referenced by zero other packages, confirming that it is a terminal utility consumed primarily by forms or ad hoc callers rather than a shared framework component.

Key Procedures and Functions

  • GET_LPN_ORDER_LOV — Returns an LOV cursor of license plate number (LPN) related order headers. In the documented source, the implementation branches on the p_order parameter: when p_order is null or equal to '%', an open (unfiltered) query is issued; otherwise a filtered query is used. This branch was introduced to resolve performance issues on open queries. The cursor joins delivery details, trading partners, customer accounts, and order transaction type translations, restricted by organization, parent delivery detail, source code 'OE', and a non-null scheduled date.
  • GET_LPN_ORDERLINE_LOV — Supplies LOV data for individual order lines associated with an LPN, supporting line-level selection in shipping flows.
  • GET_MANIFEST_PICKSLIP_LOV — Populates the LOV for manifest pick slips, allowing users to select a pick slip when building or reviewing manifests.
  • GET_MANIFEST_ORDER_LOV — Populates the LOV for manifest orders, enabling order selection during manifest processing.

The naming convention (GET_*_LOV) and the x_order_lov OUT NOCOPY t_genref pattern indicate every routine returns a ref cursor rather than a scalar value. Parameters are limited to organization, parent delivery detail, and filtering criteria; no DML is performed.

Tables Accessed

The package reads from a defined set of shipping, order management, and resource tables through APPS synonyms. Core shipping tables include WSH_DELIVERY_DETAILS for delivery line data, WMS_DISPATCHED_TASKS for warehouse dispatch activity, and MTL_SECONDARY_INVENTORIES for subinventory context. Trading partner data is drawn from HZ_PARTIES and HZ_CUST_ACCOUNTS. Order information comes from OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_TRANSACTION_TYPES_TL, and MTL_SALES_ORDERS. Item and transaction context uses MTL_SYSTEM_ITEMS_KFV and MTL_MATERIAL_TRANSACTIONS_TEMP. Resource-related LOVs rely on BOM_RESOURCES, BOM_RESOURCE_EMPLOYEES, BOM_RESOURCE_EQUIPMENTS, and BOM_STD_OP_RESOURCES. These are read-only references supporting LOV cursor construction; the package writes no data.

Usage Notes

WMS_SHIPPING_LOVS is invoked by WMS shipping and dispatch forms and by custom extensions requiring the same shipping LOV result sets. Callers pass an organization identifier and any optional filter such as p_order, then iterate the returned ref cursor. Because it is not referenced by other PL/SQL packages, it should be treated as a form-facing utility. Developers extending WMS shipping should prefer these procedures over re-implementing the underlying joins, particularly given the documented performance optimization that separates open and filtered query paths. Note that the package is not a public API and carries no commit or validation logic; it merely retrieves candidate records.