Lesson 2 of 6
RF testing: real devices, real aisles, real networks
10 min
Listen to this lesson
In a modern warehouse, the RF device is the user interface for most of the work. A process that works on a desktop in a meeting room can fail on a scanner at the back of aisle 06, behind steel racking, with gloves on, at 5:30 in the morning. RF testing is where warehouse sign-off is won or lost, and it cannot be done from the project office.
What the RF framework gives you
EWM's RF framework runs warehouse transactions on mobile devices. Users log on with /SCWM/RFUI, need an SAP user with a default resource, and get screens built from templates combined into a display profile for the device. GUI devices connect like a PC. Browser-based devices, the usual choice for new rollouts, connect through ITS Mobile or SAP GUI for HTML; since SAP S/4HANA 2021 the EWM_MOBGUI service shows RF screens in SAP GUI for HTML with a current SAP Fiori theme (SAP Note 3048632). Older character-based (telnet) terminals connect through SAPConsole, a legacy Windows-based route that SAP training still lists but that a new device strategy should not depend on. Pick-by-voice replaces the screen with voice. SAP Fiori apps for EWM serve office and supervisor work such as monitoring; they do not replace RF transactions on scanners. Standard functions include logon, logoff and recovery, plus putaway, picking, loading, unloading, deconsolidation, packing, counting and replenishment. Menus can be adapted with the RF menu manager.
| Connection type | How it connects | What to test specifically |
|---|---|---|
| GUI device | Like any SAP GUI client | Screen size and touch targets; keyboard shortcuts |
| Browser-based | ITS Mobile, or SAP GUI for HTML through the EWM_MOBGUI service | Browser on the device; session timeouts; reconnection; theme and scan field focus |
| Character-based (legacy) | Through SAPConsole on a Windows server | Only if old terminals stay: function keys, SAPConsole server availability, and a replacement plan |
| Pick by voice | Voice dialog instead of a screen | Recognition in real noise; fallback to scanning |
Test conditions you cannot simulate in the office
| Condition | What can go wrong | How Contoso tests it |
|---|---|---|
| Wi-Fi coverage | Dead spots behind steel racks or at dock doors | Walk every aisle and door with a device; log signal and response |
| Roaming | Session lost when moving between access points | Drive a forklift terminal the full length of the building mid-task |
| Connection loss | Half-confirmed task or duplicate posting | Cut the network during confirmation; log back on and use recovery |
| Scanning | Damaged or glossy labels, wrong barcode type | Scan real labels from Lakeside, real bin labels, real HU labels |
| Environment | Gloves, cold dock, glare, battery at end of shift | Run a full shift on devices, not a 20-minute demo |
| Printers | Labels print at the wrong printer or not at all | Print HU and shipping labels at every station |
RF conditions only the real warehouse can test.
Recovery deserves its own test case. When a device loses connection in the middle of a task, the user must be able to log back on and continue where they stopped, without confirming a task twice or leaving it half-done. Test it at the worst moments: after scanning the source, before scanning the destination; during a pick into a handling unit; during count entry.
- PrepareReal users with real roles and default resources; devices on the production network design
- WalkNetwork survey of every aisle, door and work center with response times logged
- ExecuteScripted RF scenarios per process family on each device type
- BreakConnection loss, bad labels, wrong scans, exception codes at each step
- Shift testA full shift on devices with a realistic workload
- EvidenceTask and user logs, device IDs, photos of labels, network survey results
What would you do?
All RF scripts pass in the training room using the building's office Wi-Fi. Sam, the Basis lead, says the warehouse access points are installed but untested. Go-live is in five weeks. What should Priya plan?
In SAP S/4HANA Cloud Public Edition, warehouse workers use the same RF framework and mobile approach for scanners, while supervisors use the Fiori warehouse apps; the device and network tests in this lesson apply unchanged.
- RF devices connect as GUI, browser-based (ITS Mobile or SAP GUI for HTML), legacy character-based (SAPConsole) or voice; each has its own test points.
- Test in the real building: Wi-Fi coverage, roaming, scanning, printers, environment and full shifts.
- Recovery after connection loss needs its own test cases at the worst moments.
- Run RF tests with production roles, default resources and real labels.
Check your understanding · not graded
Lesson check
1. How do character-based RF devices connect to EWM?
2. What does an RF recovery test prove?
3. Why walk every aisle with a device before RF sign-off?
4. Which RF master data is most often missing at go-live?