Search Results call_workflow

Overview

The APPS.WMS_WCS_DEVICE_GRP package body is a Warehouse Management System (WMS) Warehouse Control System (WCS) integration package that manages the interaction between Oracle E-Business Suite and material handling equipment such as RF devices, scanners, and automated conveyor controllers. Classified as a GRP (group) API in ETRM 12.2.2, it encapsulates the device-level transaction logic required to sign devices on and off, validate device authorization, dispatch requests to the WCS layer, and translate WCS responses back into EBS state changes. The package is owned by APPS and resides in the WMS schema family, operating alongside the WMS_Task_Dispatch_Device API, which it calls to resolve device metadata.

Key Procedures and Functions

• DEVICE_SIGN_ON — Validates a device against WMS_Task_Dispatch_Device.get_device_info. If the device is already signed on, the procedure raises the error WMS_DEVICE_ALREADY_SIGNED and sets the open API x_return_status to E. If the device is valid (S), it invokes WMS_Task_Dispatch_Device.insert_device and returns a success status. The procedure is declared with PRAGMA AUTONOMOUS_TRANSACTION and supports debug logging via the INV_DEBUG_TRACE profile option.
• DEVICE_SIGN_OFF — Terminates an active device session, releasing the device for reuse and appropriately updating the device request state.
• SINGLE_DEVICE_SIGN_OFF — Performs sign-off for a single identified device, typically invoked to force-release a device from a session without affecting other devices in the group.
• DEVICE_REQUEST — Submits a request to the WCS, creating or updating a record in WMS_DEVICE_REQUESTS that represents the unit of work the device must process.
• IS_WCS_ENABLED — Returns whether WCS integration is active for the current operating context, allowing callers to short-circuit WCS logic when the feature is disabled.
• PROCESS_RESPONSE — Consumes a WCS response message (MSG_COMPONENT_LOOKUP_TYPE) and applies the resulting state transition. This procedure is the counterpart invoked after call_workflow for asynchronous response handling.
• call_workflow — Accepts a device identifier and a response record, and dispatches the WCS workflow processing for that device. This is the entry point most commonly referenced by callers searching for the call_workflow token.

Tables Accessed

• WMS_DEVICE_REQUESTS — The primary transactional table. Reads and writes here track outstanding work dispatched to devices and their completion status, driving sign-on/sign-off and request lifecycle logic.
• MTL_TRANSACTION_REASONS — Referenced for reason code validation, ensuring device-driven inventory transactions carry a legitimate reason identifier prior to posting.

Usage Notes

The package is invoked from WMS mobile/RF forms, WCS integration concurrent programs, and custom code that requires direct device session control. It is referenced by four other packages in the ETRM inventory, indicating it is a shared service layer rather than a standalone entry point. Because DEVICE_SIGN_ON declares PRAGMA AUTONOMOUS_TRANSACTION, callers must commit or roll back sign-on work explicitly; the autonomous transaction insulates sign-on state from the surrounding transaction context. Standard Oracle EBS open API conventions apply: inspect x_return_status, then x_msg_count and x_msg_data for error detail. When integrating custom code, invoke IS_WCS_ENABLED first to avoid unnecessary WCS calls in non-WCS installations. Debug tracing can be enabled by setting the INV_DEBUG_TRACE profile option, which routes messages through the package's LOG procedure.