Search Results wms_read_event




Overview
Explore in AI Chat

Overview

WMS_RFID_DEVICE_PUB is a public PL/SQL package in the Oracle Warehouse Management (WMS) product, owned by the APPS schema and declared with AUTHID CURRENT_USER. Its documented purpose is to process EPC (Electronic Product Code) and LPN (License Plate Number) data read through RFID or barcode hardware. The package serves as the interface between the Oracle Edge Server and Oracle Warehouse Management, accepting raw scan reads from RFID readers and barcode devices and translating them into the appropriate warehouse transactions. The package header carries the signature $Header: WMSRFIDS.pls 120.4 2006/07/06, indicating it has been a stable, active component of the WMS stack since the early 11i era and remains present through EBS 12.1.1 and 12.2.2.

The behavior of the package is configuration-driven. The "Define Device" and "Assign Device" forms in Oracle Warehouse Management determine which transactions are valid for a given device and how read data should be interpreted. Scan results and processing outcomes are persisted in an XML file generated according to device setup and in the WMS_DEVICE_REQUESTS_HIST table, viewable through the "Device Requests History" form.

Key Procedures and Functions

The documented API surface consists of four procedures/functions. Parameter lists are intentionally omitted; only purpose is described.

  • PROCESS_RFID_TXN — The principal entry point. It accepts read data (tag ID, typically an EPC or LPN identifier) and performs the transaction determined by device configuration. Per the header comment, hardware may read only the LPN_ID, and this API resolves the correct business event from that value.
  • WMS_READ_EVENT — Handles event processing associated with a read, capturing the raw read and its outcome for storage into XML and the device requests history.
  • MOBTEST_PROCESS_RFID_TXN — A test-mode variant used to validate RFID transaction processing, typically from a mobile test harness without committing production transactions.
  • t_genref / tag_info_tbl — Not procedures but publicly declared types supporting the API: a REF CURSOR and an associative array of the tag_info record (tag_id, tag_data, LPN IDs, item, serial, GTIN, GTIN serial).

Tables Accessed

The package reads and writes a set of WMS and inventory tables through APPS synonyms. WMS_DEVICE_REQUESTS, WMS_DEVICE_REQUESTS_HIST, and WMS_DEVICE_REQUESTS_S store the request envelope, historical outcomes, and sequence respectively. WMS_BUS_EVENT_DEVICES maps devices to business events for transaction resolution. WMS_EPC, WMS_LICENSE_PLATE_NUMBERS, and WMS_LPN_CONTENTS provide EPC and LPN resolution. WMS_SHIPPING_TRANSACTION_TEMP, WSH_DELIVERY_DETAILS, and RCV_SHIPMENT_HEADERS support shipping and receiving contexts. MTL_SYSTEM_ITEMS, MTL_SERIAL_NUMBERS, MTL_CROSS_REFERENCES, and MTL_PARAMETERS supply item, serial, and cross-reference validation data. FND_APPLICATION identifies the owning application context.

Usage Notes

WMS_RFID_DEVICE_PUB is invoked primarily by the Oracle Edge Server, not by end users directly. It can also be called from custom code, device integration middleware, or mobile test harnesses (via MOBTEST_PROCESS_RFID_TXN). Because device behavior is entirely governed by the Define Device and Assign Device setup forms, integrators must configure devices before the API will resolve transactions; otherwise the XML record is generated but no transaction occurs. The package is referenced by zero other packages, confirming it is a leaf-level public API. The ETRM metadata is the authoritative source for the documented procedure set; consult the package specification in the target EBS release to confirm exact parameter signatures.