Search Results wms_device_requests_s

Overview

WMS_DEVICE_INTEGRATION_PVT is a private PL/SQL package body in the APPS schema that provides the core integration layer between Oracle Warehouse Management (WMS) transactional activity and the warehouse material handling devices managed within an EBS instance. The package belongs to the WMS device management subsystem, which routes task and transaction requests to radio-frequency (RF) terminals, printers, scanners, and other device endpoints configured in the warehouse. Its central responsibility is to record device requests against a request sequence, resolve the appropriate device for a given business event, and produce the formatted payload — XML or CSV — that is transmitted to the device interface.

The package is classified as a PVT (private) API in the ETRM 12.2.2 inventory, indicating that it is not intended for direct external invocation. It is consumed internally by other WMS public packages and by concurrent processing infrastructure. The header comment references patch level 120.7 of the 12.1.1 code line, and the same body is carried forward into 12.2.2 without functional change.

Key Procedures and Functions

• DEVICE_REQUEST — Raises a new device request record, allocating a request identifier from the WMS_DEVICE_REQUESTS_S sequence and persisting the defining attributes of the transaction to be executed on the device.
• RESUBMIT_REQUEST — Re-issues an existing request that previously failed or was not acknowledged, updating its state so the device interface retries delivery.
• POPULATE_HISTORY — Copies processed request rows into WMS_DEVICE_REQUESTS_HIST, providing the archival and audit trail for device activity.
• TRACE — Emits diagnostic messages when the INV_DEBUG_TRACE profile option is enabled, delegating to INV_TRX_UTIL_PUB.TRACE for consistent logging.
• IS_DEVICE_SET_UP — Determines whether device integration has been configured for the current organization, guarding downstream processing.
• SELECT_DEVICE — Resolves the target device for a given business event by consulting WMS_BUS_EVENT_DEVICES and the device definition tables.
• GENERATE_XML_CSV — Builds the outbound message payload for a device request in either XML or CSV format, the function most commonly referenced in troubleshooting and extension searches.

Tables Accessed

The package reads and writes WMS_DEVICE_REQUESTS and WMS_DEVICE_REQUESTS_HIST for the active and archived request queues, and draws sequence values from WMS_DEVICE_REQUESTS_S. Device configuration is resolved through WMS_DEVICES, WMS_DEVICES_B, WMS_BUS_EVENT_DEVICES, and WMS_DEVICE_ASSIGNMENT_TEMP. Transaction detail is gathered from MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_PARAMETERS, MTL_SERIAL_NUMBERS_TEMP, MTL_SYSTEM_ITEMS_KFV, MTL_TRANSACTION_LOTS_TEMP, and MTL_TXN_REQUEST_LINES, while WMS_DISPATCHED_TASKS and WMS_LICENSE_PLATE_NUMBERS supply task and LPN context. Collectively these tables allow the package to translate an inventory or shipping transaction into a device-readable instruction.

Usage Notes

WMS_DEVICE_INTEGRATION_PVT is referenced by fifteen other packages and is normally reached indirectly — for example, through shipping confirmation and task dispatch flows that call the device integration layer rather than invoking this body directly. Because the API classification is private, customizations should call the supported public wrapper packages instead. When troubleshooting GENERATE_XML_CSV output or missing device requests, enable the INV_DEBUG_TRACE profile option to obtain trace output, and verify device setup through IS_DEVICE_SET_UP before investigating payload formatting.