Search Results validate_overpick




Overview
Explore in AI Chat

Overview

The APPS.WMS_OVERPICK package is a Warehouse Management System (WMS) utility within Oracle E-Business Suite that supports overpick validation logic during material picking operations. Its documented purpose is to query the quantity tree (MTL_QUANTITY_TREE conceptually) to determine whether sufficient quantity exists in a given locator to be picked. When sufficient quantity is available, the API returns an indicator value of 1; otherwise it returns 0. In the context of Oracle EBS 12.1.1 and 12.2.2, this package is relevant to warehouse execution flows where an operator may attempt to pick more than the nominal suggested quantity, and the system must validate that the physical or logical locator inventory can support the requested overpick.

The package is owned by APPS and is classified under the ETRM API classification of OTHER, indicating it is not a standard public open-interface API but rather an internal warehouse utility. The header comment (version 120.1, dated 2005) reflects an implementation that has remained stable across releases, which is typical for focused WMS helper APIs that are consumed by picking and move-order logic rather than by external integrations.

Key Procedures and Functions

  • VALIDATE_OVERPICK — The single documented procedure in the package. Its stated purpose is to query the quantity tree to determine whether there is sufficient quantity to be picked in a locator. It returns a status value that indicates success, error, or unexpected error, along with message count and message data for error handling. Critically, it returns x_ret, a numeric indicator that equals 1 when the requested quantity is available (that is, the requested quantity is greater than the quantity found in the quantity tree, permitting an overpick) and 0 otherwise. It also returns x_att, the quantity available to transact, and accepts inputs identifying the transaction (via a transaction temp identifier), the requested quantity, and the unit of measure. The parameter lists are not restated here beyond the documented intent.

Tables Accessed

The ETRM metadata documents the following tables referenced via APPS synonyms:

  • MTL_MATERIAL_TRANSACTIONS_TEMP — The transaction temporary table. The procedure accepts p_temp_id (transaction_temp_id), which ties the validation to a staged transaction row in this table. The package reads this table to identify the transaction context (item, locator, subinventory, and related attributes) against which the overpick validation is performed.
  • MTL_SYSTEM_ITEMS — The item master table. This is read to resolve item-level attributes relevant to the transaction, including unit of measure handling and item definition, ensuring the validation is applied to a valid, transactable item.

The quantity tree referenced in the package comments is the internal structure used to determine on-hand availability by locator; the documented table list reflects the primary staging and item master reads that drive the validation.

Usage Notes

WMS_OVERPICK.VALIDATE_OVERPICK is an internal WMS helper rather than a standalone interface. It is typically invoked by Oracle Warehouse Management picking, move-order, and task execution logic at the point where a user or subsystem attempts to pick a quantity that may exceed the suggested pick quantity. Invocation is generally indirect — triggered from WMS picking forms and warehouse execution flows as part of the overpick confirmation path — rather than from standalone concurrent programs.

Because the ETRM metadata records that the package is referenced by 0 other packages, it is best characterized as a leaf-level utility consumed within the WMS transaction stack rather than a shared dependency. Custom code that performs direct picking or staging into MTL_MATERIAL_TRANSACTIONS_TEMP may call this procedure to validate overpick availability before committing a transaction, observing the standard WMS error-handling contract (return status, message count, and message data) and using x_ret and x_att to decide whether to proceed. The reference to the obsolete NOCOPY /* file.sql.39 */ annotation and the 2005 header indicate the package has been carried forward largely unchanged through 12.1.1 and 12.2.2, so behavior should be treated as stable. The user search term "validate_overpick" corresponds directly to the sole documented procedure in this package.