Search Results pack_unpack_split
Overview
WMS_RCV_PUP_PVT is a private PL/SQL package body in the Oracle Warehouse Management (WMS) module that supports pack, unpack, and split operations performed against receiving transactions within Oracle E-Business Suite. The name convention — the PVT suffix — indicates that this is an internal (private) API package, not a public interface intended for direct customer invocation. It works closely with the receiving (RCV) and inventory (INV) schemas to manage the movement of material, license plates, lots, and serial numbers during warehouse-directed receiving flows. In EBS 12.1.1 and 12.2.2, it frequently appears in the context of "7.2.2" warehouse management setup and receiving documentation, where pack/unpack/split functionality for inbound shipments is configured and exercised.
Key Procedures and Functions
The ETRM metadata documents two procedures/functions in this package:
- PACK_UNPACK_SPLIT — The primary workhorse routine of the package. It orchestrates packing, unpacking, and splitting of received material. Based on the referenced interface tables and the package's role, this procedure creates and manipulates transaction temporary records, lot and serial interface records, and license plate numbers to reflect the desired pack, unpack, or split outcome. It builds the corresponding MTL transaction temp rows and lot/serial interface rows so that downstream transaction processing (e.g., the receiving transaction processor) can post the resulting inventory movements. Variations such as a derived insert_lot_serial helper visible in the package source support populating lot and serial attributes (lot number, expiration date, status, supplier lot number, grade, and similar attributes) on the interface records.
- print_debug — A utility procedure (evident from the package source) used to emit trace/debug output controlled by the INV_DEBUG_TRACE profile option, primarily for diagnostic logging through the mobile helper functions.
Because this is a private package, parameter lists are not exposed for public use, and callers should not rely on the internal signatures.
Tables Accessed
The package reads and writes several inventory, receiving, and warehouse tables via APPS synonyms:
- MTL_MATERIAL_TRANSACTIONS_TEMP — staging of pending material transactions produced by pack/unpack/split.
- MTL_SERIAL_NUMBERS_TEMP and MTL_SERIAL_NUMBERS_INTERFACE — staging of serial number assignments and interface rows.
- MTL_TRANSACTION_LOTS_TEMP and MTL_TRANSACTION_LOTS_INTERFACE — staging of lot-controlled transaction detail and interface rows.
- MTL_TXN_REQUEST_LINES, MTL_SYSTEM_ITEMS — item and move-order line validation and lookup.
- RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS_INTERFACE_S — receiving shipment and transaction context driving the pack/unpack/split logic.
- WMS_DISPATCHED_TASKS, WMS_LICENSE_PLATE_NUMBERS, WMS_PACKING_MATERIAL_GTEMP — WMS license plate, task, and packing material structures used to model LPN-based packing and unpacking.
- DUAL and PLITBLM — utility and standard WMS support objects.
Usage Notes
WMS_RCV_PUP_PVT is invoked indirectly by other packages (the metadata notes it is referenced by two other packages) and by WMS receiving flows — typically when a user performs pack, unpack, or split actions in the WMS receiving pages (mobile or desktop) related to "7.2.2" receiving setup. It is not a supported public API, so custom code should call the documented public RCV/WMS APIs rather than this package. Direct invocation is appropriate only for diagnostics or when replicating standard behavior in a controlled patch, and callers must respect the transaction interface staging pattern the package follows.
-
APPS.WMS_RCV_PUP_PVT SQL Statements
12.1.1
-
APPS.WMS_RCV_PUP_PVT SQL Statements
12.2.2
-
PACKAGE BODY: APPS.WMS_RCV_PUP_PVT
12.1.1
-
PACKAGE BODY: APPS.WMS_RCV_PUP_PVT
12.2.2
-
PACKAGE: APPS.WMS_RCV_PUP_PVT
12.1.1
-
PACKAGE: APPS.WMS_RCV_PUP_PVT
12.2.2
-
PACKAGE BODY: APPS.WMS_ITEM_LOAD
12.1.1
-
PACKAGE BODY: APPS.WMS_ITEM_LOAD
12.2.2
-
APPS.WMS_RCV_PUP_PVT dependencies on FND_MESSAGE
12.1.1
-
APPS.WMS_RCV_PUP_PVT dependencies on FND_MSG_PUB
12.2.2
-
APPS.WMS_RCV_PUP_PVT dependencies on FND_API
12.1.1
-
APPS.WMS_RCV_PUP_PVT dependencies on FND_API
12.2.2
-
APPS.WMS_RCV_PUP_PVT dependencies on FND_MESSAGE
12.2.2
-
APPS.WMS_RCV_PUP_PVT dependencies on FND_MSG_PUB
12.1.1
-
APPS.WMS_RCV_PUP_PVT dependencies on INV_RCV_STD_TRANSFER_APIS
12.1.1
-
APPS.WMS_RCV_PUP_PVT dependencies on INV_RCV_STD_TRANSFER_APIS
12.2.2
-
APPS.WMS_RCV_PUP_PVT dependencies on INV_RCV_COMMON_APIS
12.1.1
-
APPS.WMS_RCV_PUP_PVT dependencies on WMS_RCV_PUP_PVT
12.2.2
-
APPS.WMS_RCV_PUP_PVT dependencies on WMS_RCV_PUP_PVT
12.1.1
-
APPS.WMS_ITEM_LOAD dependencies on WMS_RCV_PUP_PVT
12.2.2
-
APPS.WMS_RCV_PUP_PVT dependencies on INV_RCV_COMMON_APIS
12.2.2
-
APPS.WMS_ITEM_LOAD dependencies on WMS_RCV_PUP_PVT
12.1.1
-
APPS.WMS_RCV_PUP_PVT dependencies on INV_RCV_INTEGRATION_APIS
12.1.1
-
APPS.WMS_RCV_PUP_PVT dependencies on INV_RCV_INTEGRATION_APIS
12.2.2
-
APPS.WMS_ITEM_LOAD dependencies on INV_RCV_INTEGRATION_APIS
12.1.1
-
APPS.WMS_ITEM_LOAD dependencies on INV_RCV_INTEGRATION_APIS
12.2.2
-
APPS.WMS_RCV_PUP_PVT dependencies on FND_API
12.1.1
-
APPS.WMS_RCV_PUP_PVT dependencies on FND_API
12.2.2
-
APPS.WMS_ITEM_LOAD dependencies on WMS_CONTAINER_PUB
12.1.1
-
APPS.WMS_ITEM_LOAD dependencies on WMS_CONTAINER_PUB
12.2.2
-
APPS.WMS_ITEM_LOAD dependencies on FND_API
12.1.1
-
APPS.WMS_ITEM_LOAD dependencies on FND_API
12.2.2