# Liquid UI for SAP Extended Warehouse Management

> Source: https://netray.co/stack/liquid-ui-sap-ewm-rf-rfid
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Stack

## Short answer

Liquid UI from Synactive puts a simplified, mobile-friendly layer over existing SAP WM and EWM transactions, so warehouse staff can use handhelds and RFID readers without custom ABAP. The vendor says no backend changes are required, and the SAP partner listing mentions handheld and fixed RFID readers.

## Erp

SAP ECC

## Erp Key

sap-ecc

## On Prem

true

## Product

Liquid UI for SAP Extended Warehouse Management

## Vendor

Synactive Inc.

## Category

RF and RFID data collection

## Integration

**Method:** Screen-layer extension of SAP transactions

**Detail:** Liquid UI works at the SAP GUI transaction layer, adding scripts that simplify screens, prefill fields and chain steps. Because it drives standard transactions, SAP business logic and authorizations still apply.

**Method:** RFID and handheld device support

**Detail:** The SAP partner listing describes support for handheld and fixed RFID readers. Reader data feeds the same transaction fields an operator would otherwise type or scan.

## Data Flows

**From:** Handheld or RFID reader

**To:** SAP WM or EWM

**Data:** Bin, handling unit, material and quantity scans

**Trigger:** Operator scan or tag read

**From:** SAP WM or EWM

**To:** Handheld

**Data:** Warehouse tasks and confirmation prompts

**Trigger:** Task creation or operator request

**From:** Handheld

**To:** SAP WM or EWM

**Data:** Task confirmations, put-away, picks and counts

**Trigger:** Operator confirms on the device

## Setup

### Pick one process

**Detail:** Start with receiving, put-away or picking in a single warehouse.

### Inventory the standard transactions in use

**Detail:** List the WM or EWM transactions and the fields operators touch.

### Design the simplified screens

**Detail:** Define which fields are scanned, defaulted or hidden.

### Choose and test devices

**Detail:** Test handheld models and RFID readers on your real wifi and lighting conditions.

### Align authorizations

**Detail:** Confirm operators have the SAP authorizations for the transactions the screens drive.

### Pilot on one shift

**Detail:** Run alongside the old process and compare error rates.

### Roll out with change control

**Detail:** Version the scripts so SAP upgrades can be regression tested.

## Pitfalls

- SAP upgrades or support packs that change a screen and break a script.
- RFID read zones that pick up tags from neighboring bins, causing wrong confirmations.
- Scanning barcodes that do not match the SAP field format, such as handling unit numbers with leading zeros.
- Session timeouts on weak wifi leaving tasks half confirmed.
- Customer-modified transactions that differ from the standard the scripts were built for.
- Treating WM and EWM as interchangeable; the transactions and data models differ.

## Ai Layer

### Task exception explanations

**Description:** A private assistant reads SAP warehouse task and error data and explains why a confirmation failed in plain language.

### Count variance review

**Description:** Compare cycle count results with movement history and suggest likely causes for a supervisor to confirm.

### Questions for warehouse leads

**Description:** Ask which open tasks are aging by area, and get an answer from SAP data without a custom report.

### Script change impact notes

**Description:** After an SAP change, summarize which screens and scripts are likely affected for testers to check.

## Alternatives

- Use SAP's standard RF framework for WM, or SAP Fiori warehouse apps for EWM, if their screens are acceptable.
- A third-party WMS with RF built in is better if you are replacing the warehouse layer entirely.
- Custom ABAP screens are possible but harder to maintain.

## Faq

### Does Liquid UI require backend changes in SAP?

**Answer:** The vendor states it extends existing transactions with no backend changes. You should still test with your authorizations, customizations and release, and plan regression tests for upgrades.

### Does it support RFID?

**Answer:** The SAP partner listing mentions handheld and fixed RFID readers. Reader models, tag types and read-zone design are project specifics you should validate in a pilot.

### Is it only for EWM?

**Answer:** The product is named for EWM, and the vendor record also references WM transactions. Confirm which applies to your warehouse before scoping.

### Where does AI fit?

**Answer:** As a read-only helper for exception explanation and questions. It should not confirm tasks itself; a person approves any change.

## Source

https://www.sap.com/canada/products/scm/partners/synactive-inc-liquid-ui-for-sap-extended-warehouse-management.html

## Search terms

liquid ui sap ewm rfid, synactive liquid ui, sap ewm handheld, sap wm rf without abap, sap rfid warehouse, sap mobile warehouse transactions

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json