Lesson 5 of 6
Resources, users and queues
9 min
Listen to this lesson
A warehouse task says what to move. It does not say who moves it. EWM assigns work through warehouse orders, queues and resources. If this master data is wrong, every process can be correct on paper while the reach-truck driver's scanner stays empty. This lesson explains the objects and how they connect.
The objects
| Object | What it is | Contoso example |
|---|---|---|
| Resource | A person or piece of equipment that executes work; logs on to an RF or non-RF environment | RT-01 (reach truck), PK-03 (picker with cart) |
| Resource type | Groups resources with similar physical qualifications: velocities, position management, priorities for bin access types and handling unit types | RTRK (reach truck, can reach level 5), WALK (walking picker, levels 1–2) |
| Resource group | Groups resources for work assignment; defines the sequence of queues they may work | RG-IN (inbound), RG-OUT (outbound) |
| Queue | A logical list of warehouse orders, determined from activity areas, bin access type, process type and activity | Q-PUT-HR, Q-PICK, Q-REPL, Q-COUNT |
| User assignment | Links the SAP user to a default resource so mobile logon works | User MARCUS → resource SUP-01 (warehouse supervisor) |
Resource management objects. Names are Contoso's.
- Warehouse task createdPutaway of pallet HU 1000123 to bin 03-07-4
- Queue determinedFrom source and destination activity area, bin access type and process type: Q-PUT-HR
- Warehouse order builtCreation rules group tasks; all tasks in one order share one queue
- Resource asks for workDriver on RT-01 chooses system-guided processing on the scanner
- Queue sequence checkedRG-IN may work Q-PUT-HR first, then Q-REPL
- Order assignedThe best available warehouse order in an allowed queue goes to RT-01
Warehouse orders in one paragraph
Warehouse orders bundle tasks into a work package a person can finish in a set time. Warehouse order creation rules, found by activity area and activity, apply filters (weight, volume, time), limits (for example at most 20 items) and sort rules, and can create pick handling units through a packing profile. If no rule applies, SAP's fallback rule groups tasks by activity area, queue and warehouse request. When orders come out differently than designed, activate the application log for warehouse order creation (/SCWM/ACTLOG) and read it in the monitor rather than guessing.
Logging on and getting work
Mobile users start the RF framework with transaction /SCWM/RFUI. The user must exist as an SAP user and have a resource assigned as default; the logon also sets the device's presentation profile and environment. Resources can only execute warehouse orders in queues that match their operating environment, RF or desktop. Work then arrives in one of two ways:
| System-guided | Manual | |
|---|---|---|
| Who chooses the order | EWM, from the queues allowed for the resource | The user scans or selects a specific order or handling unit |
| Queue restriction | Only queues assigned to the resource or its group | Any available order can be selected |
| Typical use | High-volume putaway and picking | Exceptions, supervisors, small warehouses |
| Desktop alternative | Supervisor assigns orders to resources in the warehouse monitor | Printed warehouse orders handed to workers |
In most releases resources, groups, queue sequences and user assignments are maintained through the EWM menu (Master Data → Resource Management) or transactions such as /SCWM/RSRC, /SCWM/RGRP, /SCWM/QSEQ and /SCWM/USER. Check your system's menu for the exact entries.
What would you do?
Sam, the Basis lead, confirms the scanners connect. Pickers on the outbound shift log on but receive no work, while a supervisor using a test user picks fine. What should Marcus's team check first?
- Resources execute work; resource types describe what they can physically do; resource groups define which queues they work.
- Queues are determined per warehouse task; every task in a warehouse order shares one queue.
- Mobile logon via /SCWM/RFUI needs an SAP user with a default resource.
- Test with real users, resources and devices, not with an all-access test user.
Check your understanding · not graded
Lesson check
1. What decides which queues a resource is offered work from in system-guided processing?
2. What does a resource type typically describe?
3. A user logs on to /SCWM/RFUI and is rejected. Which master data is most likely missing?
4. All tasks in one warehouse order must share which attribute?