SAP EWM RF Framework: Navigation, Profiles and Mobile Setup

Everyone uses the RF framework in SAP EWM without seeing it: it is the terminal screen the warehouse operator scans. But the real value is not in the scan, it is in the configuration, the navigation, the screen profiles and the menus, exactly what the general introductions leave out.

This guide goes beyond “RF lets you scan barcodes”. It explains what the RF framework really is, how you log on and navigate, and above all which personalization objects let you tailor the interface to each operator profile. All of it grounded in the SAP standard, with no homemade recipe.

The RF framework in SAP EWM, concretely

The RF (radio frequency) framework is SAP EWM’s mobile data entry infrastructure. It meets two precise objectives: decoupling business logic from the physical presentation of data on the chosen device, while allowing personalized menus and screens, and supporting a wide variety of sizes, device types and data entry modes. In the end, the objective fits in one phrase: error-free data entry in the warehouse, through RF terminals and barcodes.

This definition changes how you see the tool. The RF framework is not “the scanner application”, it is a layer that presents the same EWM process on very different devices. Hence three connection families, which you must distinguish before any project.

For identification and verification, the framework relies on barcodes: SAP supports the GS1-128 type as standard, and other types can be added. Two tools round out the display personalization: the RF screen manager for screen appearance, and the RF menu manager to define your own menus and their hierarchy. This personalization layer is what separates a generic deployment from one truly tailored to the warehouse. Before you get there, the master data must of course be in place, which is the matter of master data synchronization between SAP ERP and EWM.

Logging on and navigating the RF environment

You start the RF environment with transaction /SCWM/RFUI. The logon user must be a registered SAP user, to which an EWM resource can be assigned by default. Once logged on, the main menu appears and the resource can be tracked in the Warehouse Management Monitor: the resource itself, the stock it carries and the selected warehouse orders.

The framework provides a base of standard functionalities. Logon enables tracking of resources, of the stock on the resource and the selection of warehouse orders. At logon, a recovery function checks whether the resource was interrupted while executing a warehouse order and, if so, redisplays the screen of the relevant step to resume the process. Then come the execution transactions for the main warehouse processes: picking, putaway, loading, unloading, deconsolidation, packing, physical inventory and replenishment.

Within a transaction, you enter data, validate it, or both. Entry is done by scanning a barcode or typing, then confirming with Enter. If the Skip Shortcut indicator is set, the posting (for example a warehouse task confirmation) is triggered automatically; otherwise the cursor moves to the Shortcut field. It is in this Shortcut field that you enter the function keys and, where necessary, the exception codes, for example to handle differences.

Transaction-specific function keys, for their part, appear in the function key line. If there are more than four buttons, the > sign appears and F5 shows the next ones. Since SAP S/4HANA 2020 FSP01, these functions can also be presented as on-screen buttons for touch devices without physical keys, through a setting in the Presentation Device.

The RF framework configuration objects

Configuring the RF framework rests on a small number of objects, all grouped under the Mobile Data Entry node of EWM customizing. Understanding them means holding the thread of the whole personalization.

In practice, you never change the standard menu directly: it is delivered with application 01, presentation profile **** and personalization profile **, and these entries are locked in a customer system. So you copy the standard into your own profiles. Creating a presentation profile and a personalization profile follows this customizing path.

1. 1
   Create a Presentation Profile and a Personalization Profile

   Copy the standard presentation profile, then add your personalization profile under the Define Personalization Profile entry of the dialog structure.

   SPRO path:

   SCM Extended Warehouse Management → Extended Warehouse Management → Mobile Data Entry → Radio Frequency (RF) Framework → Define Steps in Logical Transactions

2. 2
   Assign the Presentation Profile to your warehouse

   Link your new profile to the relevant warehouse number.

   SPRO path:

   SCM Extended Warehouse Management → Extended Warehouse Management → Mobile Data Entry → Assign Presentation Profile to Warehouse

3. 3
   Build your menus with the RF Menu Manager

   Copy the standard menu into your profiles, then create a reduced menu for the personalization profile, keeping only the buttons useful to a group of operators.

   SPRO path:

   SCM Extended Warehouse Management → Extended Warehouse Management → Mobile Data Entry → Radio Frequency (RF) Framework → RF Menu Manager

Two wizards, launched from a running RF transaction with Ctrl + Shift + F1, complete the toolset: the Split Screen wizard splits a transaction screen into several screens, and the Modify Screen wizard adds or removes fields and lets you adapt the verification fields. With each change, the system regenerates the screen for the targeted personalization profile.

Screen profiles and menus tailored to each user

SAP delivers three standard display profiles. The choice depends on the device and the entry mode, and it shapes the whole operator experience.

A display profile’s Msg.Disp. parameter controls where messages appear: on the status line (value 1) or on a new screen (value 0). This detail has a concrete consequence: to enable on-screen buttons on a touch device, a feature that arrived with SAP S/4HANA 2020, the profile must have Msg.Disp. at 0. Beware the flip side: once the pushbuttons are active, the keyboard function keys (such as F7) no longer work, the operator has to use the on-screen buttons. It is an ergonomic choice to commit to for the whole fleet.

The link between a user, their personalization profile and their resource is set in the resource management user maintenance. Technically, the entry is not mandatory to log on, but without it the user works with the standard profile, hence with all functions. That is why assigning a profile is, in practice, an important control point.

Pick by Voice and queues: going further

Pick by Voice (PbV) extends the RF framework to voice-driven picking and internal moves. It is based on the RF framework, the RF picking transaction and the ITS template generator Mobile Devices with Speech Input. The system interprets a voice input either as a field value or as a command: all possible commands must be visible on screen and represented by a button, the framework supporting up to sixteen, and you cannot assign a command to a function key. You switch to command mode by saying the keyword “Command”, and “Okay” is the equivalent of Enter. Transaction /SCWM/RFUI_PBV starts the framework, sets the voice parameter and launches the PbV transaction directly.

The other extension concerns work distribution. A queue is a logical file to which the warehouse orders to be processed are assigned. In an RF environment, a warehouse order can be assigned to a resource manually or automatically: for automatic assignment, the warehouse order must belong to a queue to which the resource is assigned. When the resource requests work by choosing a system-guided option in the RF menu, the system assigns it the most appropriate warehouse order. Queue determination happens for each warehouse task, based on criteria such as the source and destination activity area, the bin access type, the warehouse process type and the activity. The other half of the contract between ERP and EWM, on the stock side, rests moreover on availability groups and the ROD and AFS storage locations.

FAQ: the RF framework in SAP EWM

The lesson of the RF framework fits in one idea: performance does not come from the scan, but from the configuration. Screen profiles matched to devices, menus tailored per operator profile and mastered navigation turn a generic terminal into a precise tool. And like any warehouse execution, RF relies on a correct foundation, from the choice of deployment mode in the guide to choosing between WM, Stock Room Management and EWM to the master data. To go further, the RF framework in SAP S/4HANA EWM details each screen.

Keep reading

01

SAP Tutorials

SAP EWM Master Data Integration: ERP Sync with CIF, ALE, DRF

Since the move to S/4HANA, the question "how do you synchronize data between SAP ERP and EWM" no longer has the same answer, and many projects still get it wrong...

Michael A. 7 min read

02

SAP Tutorials

SAP EWM Availability Groups: ROD and AFS Storage Locations

Eight in the morning, the day after go-live. Receiving has been scanning pallets since dawn, the quantities show up fine in S/4HANA, and yet the phone rings: sales order processing...

Michael A. 12 min read

03

SAP Tutorials

SAP SD Pricing Determination: The Condition Technique

Sooner or later, on a project, a user shows you a sales order and asks why the displayed price is not the one they expected. You open the line, you...

Michael A. 14 min read

04

SAP Careers

SAP ECC vs S/4HANA: the key differences for your SAP career

If you look into SAP for your career, two acronyms keep coming up: ECC and S/4HANA. One is the older generation of SAP's ERP, the other is the current version....

Michael A. 11 min read