Search Results lpn_match

Overview

WMS_DEVICE_CONFIRMATION_PUB is the public package body in the Oracle Warehouse Management (WMS) module that processes device-driven transaction confirmations submitted from mobile RF devices, barcode scanners, and material handling equipment. In Oracle EBS 12.1.1 and 12.2.2, it serves as the confirmation layer between WMS device requests captured in the WMS_DEVICE_REQUESTS interface tables and the resulting inventory and manufacturing transactions posted in Oracle Inventory and Bills of Material. The package validates the material, lot, serial, and quantity data supplied by the device, then drives the appropriate transaction confirmation logic so that device activity is reflected accurately in the procurement, receiving, and work-in-process supply chain.

The public API is classified as PUB, indicating it is intended for supported external invocation by other Oracle EBS modules and, where appropriate, by customer extensions. The package references the global task status constants used by the WMS Device Transactions (WDT) tables, including loaded and active states, and maintains a PL/SQL associative array of LPN, lot number, and quantity records to support LPN-based lot and quantity aggregation. The lpn_match search term relates to this internal LPN, lot, and quantity record structure, which correlates a license plate number (lpn_id) with its associated lot number and quantity during confirmation.

Key Procedures and Functions

• DEVICE_CONFIRMATION — The single documented public procedure. It is the entry point for confirming a transaction initiated from a WMS device. It accepts the device request data, validates it, and coordinates the inventory transaction flow. Callers invoke this procedure to commit the device response back to the EBS transaction tables.
• validate_child_record (private) — Validates child records associated with a parent device request. It examines lot and serial codes, transaction quantities, and quantity discrepancy flags, and returns a status indicating whether the child record passes validation. A parameter controls whether a null lot or serial number should be treated as an error, which is important for lot- and serial-controlled items.
• trace (private) — A diagnostic helper that writes debug messages to the Inventory transaction trace facility, gated by the INV_DEBUG_TRACE profile option and scoped to the WMS_DEVICE_CONFIRMATION_PUB module at trace level 9.

Tables Accessed

The package reads and writes the following via APPS synonyms:

• WMS_DEVICE_REQUESTS and WMS_DEVICE_REQUESTS_HIST — the device request interface and its history, which hold the pending and historical device confirmations.
• MTL_MATERIAL_TRANSACTIONS_TEMP and MTL_MATERIAL_TRANSACTIONS_S — staging and base inventory transaction records generated from the confirmation.
• MTL_TRANSACTION_LOTS_TEMP — temporary lot data for the transaction.
• MTL_SERIAL_NUMBERS and MTL_SERIAL_NUMBERS_TEMP — serial number validation and generation for serial-controlled items.
• MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, MTL_SECONDARY_INVENTORIES, MTL_TRANSACTION_REASONS, and MTL_TXN_REQUEST_LINES — item, subinventory, reason, and move order reference data used during validation.
• BOM_RESOURCES, BOM_STD_OP_RESOURCES, and FND_USER — resource definitions, standard operation resources, and the confirming user for WIP and security context.

Usage Notes

WMS_DEVICE_CONFIRMATION_PUB is invoked from WMS device integration flows and is referenced by two other packages. It is called when a device submits a confirmation that must be validated and posted to inventory or WIP. Typical invocation is through the WMS mobile device framework rather than directly from an Oracle Forms screen, though custom RF applications and extensions may call the public DEVICE_CONFIRMATION procedure directly. Because the package writes to interface and temporary transaction tables, callers must ensure the standard WMS device integration setup and the INV_DEBUG_TRACE profile option are configured appropriately. When troubleshooting confirmations, enabling trace provides detailed diagnostic output for validation and posting steps, including LPN, lot, and serial matching logic.