JinJin48
JinJin48
SAP Consultant | BTP · S/4HANA · US Global Rollout
· 11 min read

Cover: SAP EWM RF Menu — the navigation tree that connects warehouse operators to their RF tasks

SAP EWM RF Menu

The RF Menu is the navigation structure displayed on an RF terminal that groups RF Logical Transactions (RFLTs) into a browsable menu tree. When a warehouse operator logs into an RF device, they are directed to the RF Menu assigned through their RF Profile. The menu organizes all executable warehouse tasks — putaway, picking, stock transfers, physical inventory — into a hierarchical structure that matches operator roles and warehouse processes. This article covers the menu definition, item configuration, display settings, and multi-language text management that EWM consultants own.


Part 1: RF Menu — Core Concepts (All Modules)

1.1 What Is the RF Menu?

Hub-and-spoke diagram showing RF Menu at center, connected to RF Environment, RF Logical Transaction, RF Profile, User, and RF Presentation Device

An RF Menu is a named menu object within an RF Environment that presents warehouse operators with a structured list of executable RF tasks. Rather than exposing every RF Logical Transaction directly, the menu organizes them into a tree that the operator navigates using function keys or cursor movement. Each leaf node in the tree executes an RFLT; each intermediate node opens a sub-menu.

AspectDetails
RoleDefines the navigation tree on RF terminals — groups RFLTs into an operator-facing menu hierarchy
Modules using itEWM (RF Framework — primary owner across all license editions: B, A, D)
Transactions/SCWM/RFMENU (Define RF Menus), SPRO → EWM → RF Framework → Define RF Menus
Key Tables/SCWM/TRFMENU (menu header definition), /SCWM/TRFMITEM (menu item entries)
S/4HANA noteRF Menu configuration is identical across Embedded Basic, Embedded Advanced, and Decentralized EWM. No structural changes from ECC-based Decentralized EWM.

1.2 RF Menu Structure Types

Comparison grid showing three RF Menu structure types: Flat Single-Level, Hierarchical Multi-Level, and Role-Based menus

The depth and organization of an RF Menu reflects the complexity of warehouse operations and the diversity of operator roles. Choosing the wrong structure forces operators to scroll through irrelevant tasks or navigate too many sub-menu levels, both of which reduce picking and putaway efficiency.

Structure TypeDescriptionUse CaseKey Behavior
Flat Single-LevelAll RFLTs appear as direct items under one menu, no sub-menusSmall warehouses with limited task types; operators perform all functionsFast access, minimal navigation; only suitable when total RFLT count is low (typically fewer than 10)
Hierarchical Multi-LevelMenu items branch into sub-menus, which contain further sub-menus or RFLTsMid-to-large warehouses with distinct functional areas (inbound, outbound, internal, inventory)Allows logical grouping by process; operator navigates to their area before selecting a task
Role-Based MenuSeparate RF Menus defined per operator role; each menu contains only the RFLTs relevant to that roleDifferentiated warehouse roles (receiver, picker, packer, replenishment)Reduces visible clutter; operator sees only authorized tasks; role assignment handled via RF Profile

Design principle: Design one RF Menu per distinct operator role rather than building a single large menu for everyone. Role-based menus combined with RF Profile assignment are the standard pattern for mid-size and large EWM implementations.


1.3 Organizational Levels and Data Hierarchy

Hierarchy tree showing RF Framework levels: Warehouse Number → RF Environment → RF Menu → Menu Items → RF Logical Transaction

The RF Menu sits within the RF Framework hierarchy. It is defined under an RF Environment, which is itself scoped to a Warehouse Number. Understanding this hierarchy is essential when designing menus for multi-warehouse deployments — each warehouse may have different RF Environments, and each Environment can have multiple menus for different operator populations.

Warehouse Number (e.g., WH01)
   │
   └── RF Environment (e.g., ENV_STD — screen size, display settings)
          │
          ├── RF Menu A (e.g., INBOUND — receiver role)
          │      ├── Menu Item 1: [RFLT] GR from Inbound Delivery
          │      ├── Menu Item 2: [RFLT] Unload HU
          │      └── Menu Item 3: [Sub-Menu] Putaway
          │                          ├── Item 3-1: [RFLT] Putaway by Storage Bin
          │                          └── Item 3-2: [RFLT] Confirm Putaway
          │
          ├── RF Menu B (e.g., PICKING — picker role)
          │      └── ...
          │
          └── RF Menu C (e.g., INVENTORY — stock controller role)
                 └── ...
LevelObjectTablePrimary FieldsNotes
1Warehouse NumberT300 (SPRO config)LGNUMTop-level scope; all RF objects are scoped to a warehouse
2RF Environment/SCWM/TRFENVRFENV, LGNUM, screen rows/colsScreen size and display parameters; prerequisite for RF Menu
3RF Menu/SCWM/TRFMENURFMENU, RFENV, LGNUM, descriptionMenu header; links to its parent RF Environment
4Menu Item/SCWM/TRFMITEMRFMENU, SEQNO, item type, target RFLT/sub-menuEach entry in the menu tree; sequence number controls display order
5RF Logical Transaction/SCWM/TRFLTSRFLT, RFENVLeaf-level executable task; referenced from menu items of type RFLT

Key design decision: RF Menu is defined at the RF Environment level, not at the Warehouse Number level directly. A single warehouse can have multiple RF Environments (e.g., different device screen sizes), each with its own set of menus.


1.4 Integration with Other Master Data Objects

Hub-and-spoke diagram showing RF Menu at center, with spokes to RF Environment, RF Logical Transaction, RF Profile, User, and RF Presentation Device

The RF Menu does not operate in isolation. It is the central navigation object in the RF Framework and connects upward to the RF Environment, downward to RF Logical Transactions, and sideways to the RF Profile that assigns the menu to operators.

ObjectRelationshipPractical Notes
RF Environment (EWM-A09-01)Parent — RF Menu is defined within an RF EnvironmentThe RF Environment determines screen dimensions and global display settings that all menus in the environment inherit; the RF Menu must be created under an existing RF Environment
RF Logical Transaction (EWM-A09-02)Referenced by menu items — leaf-level items execute an RFLTEach RFLT referenced in the menu must already exist in the same RF Environment; referencing an RFLT from a different RF Environment is not supported
RF Profile (EWM-A09-04)Consumer — the RF Profile assigns an RF Menu to an operator or resourceOne RF Profile references exactly one RF Menu; changing the menu in the profile immediately affects all users assigned to that profile at next login
User (EWM-A04-06)Indirect — the User master references an RF Profile, which in turn references the RF MenuOperators do not reference the RF Menu directly; their menu is resolved at login by traversing User → RF Profile → RF Menu
RF Presentation Device (EWM-A09-06)Sibling — both are children of the RF EnvironmentRF Presentation Device registers the physical terminal; the device and the menu are separate objects under the same RF Environment

Part 2: EWM-Specific Field Details

2.0 Scope of EWM Ownership

Checklist showing EWM ownership across RF Menu data sections: Menu Definition, Menu Items, Display Settings, and Language Texts

Data SectionEWM InvolvementNotes
Menu Definition◎ OwnerMenu ID, description, parent RF Environment — entirely EWM-managed in /SCWM/RFMENU
Menu Items◎ OwnerItem sequence, item type, target RFLT or sub-menu reference — EWM-specific configuration
Display Settings◎ OwnerIcon assignment, function key shortcut, visible/hidden flag, sort order — configured per menu item
Language Texts○ Shared with BasisLanguage key and translated display text — EWM stores texts in standard SAP text tables; Basis manages transport and language import

Legend: ◎ = Owner / Critical, ○ = Direct involvement


2.1 Menu Definition

Checklist slide showing RF Menu Definition fields: Menu ID, Description, RF Environment, Warehouse Number

The menu definition is the header record that uniquely identifies an RF Menu within an RF Environment. It establishes the menu’s identity before any items or language texts can be added. All menu items and display configuration hang off this header.

FieldDescriptionPractical Usage
Menu ID (RFMENU)Unique alphanumeric identifier for the RF Menu within an RF EnvironmentUse a naming convention that reflects role and environment — for example, INBOUND_STD or PICKING_A. A clear ID makes RF Profile assignment and troubleshooting faster when multiple menus exist for the same warehouse.
RF Environment (RFENV)Reference to the parent RF Environment under which this menu is definedThe RF Environment sets the screen constraint for all menus within it; assign the menu to the correct environment matching the target device screen size. Attempting to add menu items that exceed the screen row count may cause display issues at runtime.
Warehouse Number (LGNUM)Warehouse to which the RF Environment and therefore this menu belongsIn multi-warehouse deployments, verify that the LGNUM matches the warehouse where operators using this menu will be working. Menus are not cross-warehouse — each warehouse requires its own set of RF Menus.
DescriptionShort free-text description of the menuInclude the target operator role in the description (e.g., “Receiver Menu — Inbound Dock”). This text appears in RF Profile maintenance and helps administrators quickly identify the correct menu when assigning profiles.

2.2 Menu Items

Checklist slide showing RF Menu Item fields: Sequence Number, Item Type, Target RFLT/Sub-Menu, Display Text

Menu items are the individual entries that populate the RF Menu tree. Each item is either a reference to an RFLT (leaf node) or a pointer to another sub-menu (intermediate node). The sequence number controls the order in which items appear on the RF terminal screen.

FieldDescriptionPractical Usage
Sequence Number (SEQNO)Integer that determines the display order of items within the menuNumber items in increments of 10 (10, 20, 30 …) rather than 1, 2, 3 to allow future insertion without full renumbering. The most frequently used tasks should receive the lowest sequence numbers to minimize navigation keystrokes.
Item TypeSpecifies whether the item executes an RFLT or navigates to a sub-menuUse RFLT type for executable tasks and SUB type for grouping sub-menus. Avoid nesting more than three sub-menu levels — deeper hierarchies slow down operators and increase mis-navigation errors during time-pressured warehouse work.
Target RFLT (RFLT)RF Logical Transaction ID to execute when the operator selects this item (only for RFLT-type items)The referenced RFLT must belong to the same RF Environment. Verify that the RFLT exists and is active before adding it as a menu item; a missing or deactivated RFLT causes a runtime error when the operator attempts to select that item.
Target Sub-MenuRF Menu ID of the sub-menu to navigate to when this item is selected (only for SUB-type items)The target sub-menu must be defined under the same RF Environment. Circular references (Menu A → Sub-Menu B → back to Menu A) are not validated at save time but cause infinite loops at runtime — always verify sub-menu chains manually after configuration.
Display TextShort text shown on the RF terminal screen for this menu itemKeep display text under 20 characters to prevent truncation on standard RF screens (typically 20 columns wide). Abbreviations are acceptable and often necessary — document abbreviation conventions in the project configuration guide.

2.3 Display Settings

Stack-layered slide showing RF Menu Display Settings: Icon, Function Key, Visible Flag, Sort Order

Display settings control the visual presentation and accessibility of each menu item on the RF terminal screen. These settings are especially important for high-throughput environments where operators execute repetitive tasks under time pressure — a well-configured display layout reduces miskeys and speeds up task selection.

FieldDescriptionPractical Usage
IconGraphical icon assigned to the menu item for visual identificationSAP provides a standard icon set for EWM RF menus. Assign recognizable icons to high-frequency items (e.g., a fork icon for putaway, a truck icon for goods receipt) to support quick visual scanning on small RF screens. Not all RF terminal firmware renders icons; confirm device capability during hardware selection.
Function Key ShortcutF-key (F1–F12) assigned as a direct shortcut to this menu itemAssign function key shortcuts to the most frequently accessed items in each menu. Document the key assignments in operator training materials — inconsistent shortcut assignments across different menus cause confusion for operators who work across multiple areas.
Visible/Hidden FlagControls whether the menu item is displayed to the operator or hiddenUse the hidden flag for items that must remain in the menu definition for technical reasons (e.g., referenced in RF Profile configuration) but should not be operator-accessible. This is preferable to deleting items that may be re-activated later.
Sort OrderSecondary ordering field when multiple items share the same sequence number rangeSort order allows fine-grained positioning of items within a sequence band. In practice, this field is rarely needed if sequence numbers are assigned with sufficient gaps (increments of 10).

2.4 Language Texts

Comparison two-column slide showing Language Texts configuration: Language Key and Translated Menu Text for multi-language RF environments

Language texts allow the same RF Menu to display item labels in the operator’s logon language. In multi-national warehouses or facilities with a multilingual workforce, language text maintenance ensures that operators see menu items in their preferred language without requiring separate menu definitions per language.

FieldDescriptionPractical Usage
Language KeyISO language code (e.g., EN for English, JA for Japanese, DE for German) identifying the text languageAlways create at minimum the installation language text and the primary operator language. For Japanese manufacturing sites operating EWM, maintain both EN and JA texts; the EN text serves as the fallback when a logon language has no translation.
Translated Menu TextDisplay text for the menu item in the specified languageKeep translations to the same length constraint as the original text (under 20 characters for standard RF screens). Coordinate with the customer’s translation team early in the project — RF menu texts are often overlooked in translation scope until user acceptance testing, causing last-minute rework.

Prerequisite: Language texts can only be maintained after the menu item exists. The logon language of the operator at RF terminal login determines which language text is retrieved at runtime — if no text exists for the logon language, the system falls back to the installation language text.


L1) Big Picture

IDCategoryTitle
ewm-001OverviewWhat is SAP EWM?

L2-A) Master Data

IDCategoryTitle
ewm-a01OverviewSAP EWM Master Data: Overview, Hierarchy & Relationships
ewm-a02-01Master DataSAP EWM Material Master
ewm-a03-01Master DataSAP EWM Storage Type
ewm-a03-02Master DataSAP EWM Storage Section
ewm-a03-03Master DataSAP EWM Putaway Strategy
ewm-a03-04Master DataSAP EWM Picking Strategy
ewm-a04-02Master DataSAP EWM Storage Bin
ewm-a04-03Master DataSAP EWM Fixed Storage Bin
ewm-a04-04Master DataSAP EWM Production Supply Area
ewm-a04-05Master DataSAP EWM Packaging Specification
ewm-a04-06Master DataSAP EWM User
ewm-a05-01Master DataSAP EWM Wave Template
ewm-a06-01Master DataSAP EWM Resource
ewm-a07-01Master DataSAP EWM Inspection Type
ewm-a08-01Master DataSAP EWM Batch Master
ewm-a08-02Master DataSAP EWM Batch Characteristics
ewm-a09-01Master DataSAP EWM RF Environment
ewm-a09-02Master DataSAP EWM RF Logical Transaction
ewm-a09-03Master DataSAP EWM RF Menu 📍
ewm-a09-04Master DataSAP EWM RF Profile
ewm-a09-05Master DataSAP EWM RF Queue
ewm-a09-06Master DataSAP EWM RF Presentation Device
ewm-a10-01Master DataSAP EWM PLC
ewm-a10-02Master DataSAP EWM Communication Point

L2-B) Transaction

IDCategoryTitle
ewm-b01OverviewSAP EWM Transactions: Process Flow, Hierarchy & Relationships