Results for “wms_lpn”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

INV_MWB_CG_TRANSFER is an Oracle E-Business Suite inventory package body owned by APPS and classified under the ETRM taxonomy as OTHER. Its name reflects its purpose: Material Workbench (MWB) Cost Group (CG) Transfer. The package implements the server-side logic required to move on-hand inventory quantities between cost groups without physically relocating the material. In Oracle Inventory, cost group transfer is a distinct transaction that reclassifies the value of inventory while leaving the physical stock in place, and this package encapsulates that transaction so that it can be driven programmatically rather than through manual entry.

The package operates against the standard Oracle Inventory transaction model. The header comment block records the hard-coded transaction attributes used for cost group transfers: transaction type 86, transaction source type 13, and transaction action 55. These constants identify the transaction as a cost group transfer within MTL_TRANSACTIONS and the surrounding transaction interface tables. The package also supports control attributes for revision, lot, and serial controlled items, and applies a unit of measure conversion when the entered UOM differs from the item's primary UOM.

Key Procedures and Functions

• TRANSFER — the core worker procedure. It accepts a full set of inventory key flexfield and control context values, including organization, inventory item, revision, subinventory, locator, LPN, lot, expiration date, serial number, on-hand quantity, availability, UOM, primary UOM, cost group, destination cost group, and user. It returns status, message count, and message data, and takes a transaction header identifier as an IN OUT parameter so the caller can create or reuse a transaction header. The procedure validates control flags, normalizes quantity for serial controlled items, and converts quantity when the operating UOM is not the primary UOM.
• VALIDATE — the pre-execution validation routine. It confirms that the supplied inventory context is consistent and permissible before the transfer is committed, returning the standard status/message interface used across Oracle Inventory public APIs.
• UPDATE_QUANTITY_TREE — the post-transaction maintenance routine. It refreshes the quantity tree aggregations so that on-hand balances, availability, and downstream planning visibility remain accurate after the cost group transfer posts.

Tables Accessed

The ETRM metadata documents a single referenced table for this package: MTL_ITEM_LOCATIONS, accessed through the APPS synonym. The package reads locator information to resolve and validate the locator identifier supplied by the caller, which is required to establish the correct on-hand record for the cost group transfer. A cost group transfer of this nature also participates in the broader MTL_TRANSACTIONS / MTL_MATERIAL_TRANSACTIONS and MTL_ONHAND_QUANTITIES family, since the package writes a transaction header and updates quantity tree aggregations, but MTL_ITEM_LOCATIONS is the only table explicitly documented in the ETRM record.

Usage Notes

INV_MWB_CG_TRANSFER is an internal, server-side package rather than a documented public API. The ETRM record shows no dependent packages — it is referenced by zero other packages — so it is not a shared library object. Invocation occurs through the Material Workbench user interface flow that performs cost group transfers, and potentially through custom PL/SQL that calls the TRANSFER procedure directly with an explicit transaction header identifier. The debug procedure mdebug is keyed to the INV_DEBUG_TRACE profile option; its body is effectively null, so tracing output is suppressed in this version. Because the package carries the "noship" header marker and a 2005 revision, it should be treated as an internal implementation detail. Custom code should prefer the supported inventory transaction APIs unless it must reproduce the Workbench cost group transfer behavior exactly, in which case the caller is responsible for supplying a valid transaction header, the correct control flags, and committed quantity tree maintenance via UPDATE_QUANTITY_TREE.