How Liquid UI for SAP Extended Warehouse Management connects to SAP ECC
Screen-layer extension of SAP transactions
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.
RFID and handheld device support
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.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Handheld or RFID reader | SAP WM or EWM | Bin, handling unit, material and quantity scans | Operator scan or tag read |
| SAP WM or EWM | Handheld | Warehouse tasks and confirmation prompts | Task creation or operator request |
| Handheld | SAP WM or EWM | Task confirmations, put-away, picks and counts | Operator confirms on the device |
Setting it up
- 1Pick one processStart with receiving, put-away or picking in a single warehouse.
- 2Inventory the standard transactions in useList the WM or EWM transactions and the fields operators touch.
- 3Design the simplified screensDefine which fields are scanned, defaulted or hidden.
- 4Choose and test devicesTest handheld models and RFID readers on your real wifi and lighting conditions.
- 5Align authorizationsConfirm operators have the SAP authorizations for the transactions the screens drive.
- 6Pilot on one shiftRun alongside the old process and compare error rates.
- 7Roll out with change controlVersion the scripts so SAP upgrades can be regression tested.
What usually breaks
- !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.
A private AI layer across both systems
Task exception explanations
A private assistant reads SAP warehouse task and error data and explains why a confirmation failed in plain language.
Count variance review
Compare cycle count results with movement history and suggest likely causes for a supervisor to confirm.
Questions for warehouse leads
Ask which open tasks are aging by area, and get an answer from SAP data without a custom report.
Script change impact notes
After an SAP change, summarize which screens and scripts are likely affected for testers to check.
Try it here, free
SAP WM and EWM Warehouse Tables Reference
A searchable list of the classic WM and EWM tables you query most, with a plain description and typical key fields.
When something else fits better
- 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.
Frequently asked questions
Does Liquid UI require backend changes in SAP?
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?
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?
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?
As a read-only helper for exception explanation and questions. It should not confirm tasks itself; a person approves any change.
Pairing documented at www.sap.com/canada/products/scm/partners/synactive-inc-liquid-ui-for-sap-extende . Liquid UI for SAP Extended Warehouse Management is a product of Synactive Inc.; Netray is independent and not affiliated with either vendor.