Search Results wms_device_integration_pvt




Overview
Explore in AI Chat

Overview

WMS_DEVICE_INTEGRATION_PVT is a private (PVT classification) PL/SQL package owned by APPS that serves as the core integration engine between Oracle Warehouse Management (WMS) business events and the physical material handling devices deployed on a warehouse floor. Its central responsibility is to translate warehouse execution activities — such as receipts, putaways, cycle counts, picks, issues, transfers, load confirmations, and task completions — into device requests that can be dispatched to RF guns, scanners, printers, conveyors, and RFID hardware, and to process the responses those devices return.

The package declares the full set of WMS business event constants (for example WMS_BE_DIRECT_RECEIPT, WMS_BE_PUTAWAY_DROP, WMS_BE_PICK_LOAD, WMS_BE_SHIP_CONFIRM, and the task completion events WMS_BE_TASK_COMPLETE through WMS_BE_TASK_CONFIRM) which mirror the MFG_LOOKUP values for the WMS_BUS_EVENT_TYPE lookup. It also declares the WMS device I/O type constants (WMS_DEV_IO_XML, WMS_DEV_IO_API, WMS_DEV_IO_TABLE, WMS_DEV_IO_CSV) defined in MFG_LOOKUP under WMS_DEVICE_IO_TYPES. These constants establish the vocabulary through which the package classifies both the triggering event and the delivery mechanism for the resulting device message.

Key Procedures and Functions

  • DEVICE_REQUEST — the primary entry point that accepts a warehouse business event and orchestrates creation of the corresponding device request record, device selection, and message dispatch.
  • RESUBMIT_REQUEST — reprocesses a previously submitted device request, typically after a communication failure or a corrected payload.
  • POPULATE_HISTORY — writes request detail into the device request history table for audit and troubleshooting purposes.
  • TRACE — emits diagnostic trace information used during debugging and support of device integration flows.
  • IS_DEVICE_SET_UP — validates that device configuration exists before a request is dispatched, preventing requests against unmapped or disabled devices.
  • SELECT_DEVICE — applies device assignment rules to determine the correct physical device for a given event, warehouse, and operator context.
  • GENERATE_XML_CSV — renders the outbound device message in the required XML or CSV format according to the device I/O type.

Tables Accessed

The package reads and writes WMS_DEVICE_REQUESTS, WMS_DEVICE_REQUESTS_S, and WMS_DEVICE_REQUESTS_HIST to create, store, and archive device request transactions. Device configuration and assignment are resolved through WMS_DEVICES, WMS_DEVICES_B, WMS_BUS_EVENT_DEVICES, and WMS_DEVICE_ASSIGNMENT_TEMP. Warehouse and item context is drawn from MTL_PARAMETERS, MTL_SYSTEM_ITEMS_KFV, MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_SERIAL_NUMBERS_TEMP, MTL_TRANSACTION_LOTS_TEMP, and MTL_TXN_REQUEST_LINES. Task and container data are sourced from WMS_DISPATCHED_TASKS and WMS_LICENSE_PLATE_NUMBERS.

Usage Notes

WMS_DEVICE_INTEGRATION_PVT is not intended for direct customer invocation. It is called internally by fifteen other packages within the WMS and Mobile Supply Chain Applications stack, which invoke DEVICE_REQUEST when a qualifying business event occurs. Because the package is declared AUTHID CURRENT_USER and classified PVT, customizations should call the corresponding public APIs or the device integration framework rather than this package directly. Typical triggering contexts include RF/mobile transactions, warehouse execution concurrent programs, and label or RFID dispatch flows in both 12.1.1 and 12.2.2.