EWM15

EWM115
Resource Management in SAP

Extended Warehouse Management
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 19
Course Duration: 3 Day(s)
Material Number: 50157362
SAP Copyrights, Trademarks and
Disclaimers
© 2022 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an SAP
affiliate company) in Germany and other countries. Please see https://
www.sap.com/corporate/en/legal/copyright.html for additional trademark
information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary
software components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical
errors or inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind, and SAP
SE or its affiliated companies shall not be liable for errors or omissions with respect
to the materials. The only warranties for SAP SE or SAP affiliate company products
and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be
construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any
course of business outlined in this document or any related presentation, or to
develop or release any functionality mentioned therein. This document, or any related
presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject
to change and may be changed by SAP SE or its affiliated companies at any time for
any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned not to
place undue reliance on these forward-looking statements, which speak only as of
their dates, and they should not be relied upon in making purchasing decisions.
Typographic Conventions
American English is the standard used in this handbook.

The following typographic conventions are also used.
This information is displayed in the instructor’s presentation
Demonstration
Procedure
Warning or Caution
Hint
Related or Additional Information
Facilitated Discussion
User interface control Example text
Window title Example text
© Copyright. All rights reserved. iii

iv © Copyright. All rights reserved.
Contents
vii Course Overview
1 Unit 1: Optimization of Resources and Processes
3 Lesson: Using Mobile Devices

17 Lesson: Managing Resources
25 Lesson: Distributing Work to Resources
41 Lesson: Optimizing The Work of Resources
47 Lesson: Setting Up the Pick, Pack, and Pass Process
57 Unit 2: Control of Physical Movements in the Warehouse
59 Lesson: Setting Up Layout-Oriented Storage Control

67 Lesson: Integrating a Material Flow System
© Copyright. All rights reserved. v

vi © Copyright. All rights reserved.
Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
● Application Consultant
● Project Manager
● Project Stakeholder
● Systems Architect
© Copyright. All rights reserved. vii

viii © Copyright. All rights reserved.
UNIT 1 Optimization of Resources and
Processes
Lesson 1
Using Mobile Devices 3
Lesson 2
Managing Resources 17
Lesson 3
Distributing Work to Resources 25
Lesson 4
Optimizing The Work of Resources 41
Lesson 5
Setting Up the Pick, Pack, and Pass Process 47
UNIT OBJECTIVES
● Use mobile devices

● Optimize mobile device processing
● Manage resources
● Work with the Pick by Cart app
● Distribute work to resources
● Set up travel distance calculation
● Optimization with SAP Warehouse Insights
● Set up system-guided or semi-system-guided processes
● Set up task interleaving
● Optimize warehouse orders
● Set up the pick, pack, and pass process
© Copyright. All rights reserved. 1

Unit 1: Optimization of Resources and Processes
2 © Copyright. All rights reserved.

Unit 1
Lesson 1
Using Mobile Devices
LESSON OVERVIEW
In this lesson, you learn how to use mobile data entry. This lessons also guides you through
the radio frequency (RF) framework and how to navigate in that environment. You are also
shown the settings for the RF framework.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
RF Framework
SAP EWM includes the implementation of a RF framework, which satisfies the following
objectives:
● Decouples business logic from the physical presentation of application data on a selected
presentation device, and enables personalized menus and screens
● Supports a large variety of device sizes, device types, and data entry types
By providing an RF framework, error-free data communication can be attained in the

warehouse through the use of mobile RF devices.

Figure 1: Using Mobile Devices
Support for GUI, Character-based, and Browser-based Devices

GUI devices are connected to the SAP system just like any other client-dependent PC.
The screens can be operated through touch screens, using predefined buttons, or they can be
operated using a keyboard. If you are using touch screens, you press the appropriate
positions on the touch screen instead of clicking with the mouse on a button.
Figure 2: Character-based or Browser-based Devices

Lesson: Using Mobile Devices
Character-based devices are linked to the system through SAPConsole. SAPConsole

operates on a Windows NT/Windows 2000 platform and interacts with the RF terminals
connected to it.
The system uses ITSmobile for connecting browser-based devices. ITSmobile uses the ITS
template technique to do this. This technique is based on the concept that an HTML template
for visualization in the browser is provided for every screen (dynpro) of the application. You
can include dynamic content or data in the templates at runtime using HTMLBusiness
(HTMLB).
ITSmobile is delivered with a new template generator that allows you to generate the
templates of simple screens directly. You can then change these further to meet your
requirements. You can also create a completely new template generator or create a new
template generator based on the one delivered.
Bar Code Support
The RF framework supports the use of bar codes for identification and verification purposes.
SAP currently supports GS1-128 bar code types, but you can also support other types within
the RF framework.
Screen Layout Personalization

Using the RF screen manager, you can customize the appearance of RF presentation screens
to ensure that they are consistent with the attributes of the presentation devices being used.
Menu Personalization
Using the RF menu manager, you can define your own menus and menu hierarchy for the RF
device transactions.
Standard RF Functionalities
The SAP RF framework provides the following standard RF functionalities:
● Logon:
Logon to the RF environment enables the tracking of resources, stock on resources, and
warehouse order (WO) selection. After logging on to the system, a resource can operate as
an active resource, which can request and execute work in the warehouse.
● Logoff
● Recovery:
During logon, the system checks with the content provider whether the user is logged on
as a resource, and if so, whether they were interrupted during WO execution. The system
checks whether a specific WO assigned to the resource was stopped before completion. If
yes, and if the WO can be locked, the system finds the WO's data and displays the screen
of the relevant step to continue the process.
● Work execution transactions for the following warehouse processes (examples):
- Picking
- Putaway
- Loading
- Unloading
- Deconsolidation

- Packing
- Physical inventory
- Replenishment
RF Navigation
In the RF framework, both menu navigation and transaction navigation are supported on
mobile devices.
The RF framework supports the following options for menu navigation to RF transactions:
1. Standard navigation:
You choose the required menu item.
2. Direct navigation to transaction:

You enter the number of the required menu item displayed in the Menu field.
3. Virtual navigation:
This option enables “virtual” navigation between menus. You enter the numbers of all
required menu items, including those not displayed on the current screen, but displayed
on subsequent screens.
Figure 3: RF Screens
Transaction Navigation
When in the screen for a particular logical transaction, you may be required to enter data,
validate existing data, or a combination of both.
When data entry is required, the input field is open. Enter the data by scanning bar codes or
typing. If you enter data manually, choose Enter.
After all input fields on the screen are filled in, one of the following actions occurs:

● If the Skip Shortcut indicator is set, the posting (for example, warehouse task (WT)
confirmation) is triggered automatically.
● If the Skip Shortcut indicator is not set, you will automatically be redirected to the Shortcut
field.
You can invoke functions by choosing the corresponding function key pushbutton, or entering
the function key in the Shortcut field. Where necessary, you enter exception codes in the
Shortcut field (for example, for differences).
RF Function Keys
Function keys are provided with the RF framework.
Standard function keys are not necessarily displayed in the function key line of an RF screen.
Instead, they are accessed directly via the function key or shortcut. For touchscreen devices
without function keys, they can also be displayed on the screen. This is a setting in the
definition of the Presentation Device.
Note:
This option to display pushbuttons is new for S/4HANA 2020 FSP01.
Function Function Key Shortcut Description

More F5 05 Displays the next
pushbuttons in the
sequence (in case of
more than four push-
buttons for a screen)
Clear F6 06 Clears a selected in-
put field, or all input
fields
Back F7 07 Returns to previous
screen/step
List F8 08 Displays the list
screen (showing the
possible input values)
for a selected field
Full Message F9 09 Displays the full mes-
sage on a separate
screen

Figure 4: Standard RF Function Keys
Transaction-specific function keys are displayed in the function key line. If more than four
function keys or pushbuttons exist for a screen, > is displayed. You can then choose F5 to
display the other pushbuttons.
RF Framework Settings
The following sections present the most important objects and settings in the RF framework:
RF Screen Manager, Presentation Device, Presentation Profile, RF Menu Manager, and
Wizards.
RF Screen Manager
The RF screen manager is a tool that enables you to customize the appearance of RF
presentation screens, to ensure that they are consistent with the attributes of the
presentation devices being used.
The RF screen manager also enables you to create, copy, and delete display profiles, and to
edit screens of a display profile. The display profile is a group of settings that determine the
appearance of RF presentation screens, including screen templates and the formats of screen
elements.
Screen Display Characteristics
By defining your own display profiles, you can determine the following screen display
characteristics:
● Screen size
● Screen element attributes, including:

- Number of buttons available for the screen

- Text length for buttons, logical transactions, and menu items
- How messages are displayed
● Screen template function groups and screen numbers
SAP delivers three display profiles:

● The standard profile is **. It has a screen layout of 8 x 40, landscape mode.
● Profile *1 is for pick-by-voice devices. The "screen layout" is 25 x 40, but only a selected
part of the standard screens is available.
● Profile *2 includes all screens of the standard profile, but in portrait mode. The screen
layout is 15 x 26.
Note:
Profile *2 was introduced with SAP S/4HANA 2020. The SAP Note “2968096 -
Example of alternative layout for Radio Frequency (RF) transactions” includes
a CSS file which can be used as a template for customer projects using this
new profile.
If you define your own display profile, you define height and width of your total screen and the
template program and screens (0001 and 0002 for messages). The length of the buttons, the
number of buttons, the length of the menu items, the display of error messages (0 = display
on a separate screen), and where the error messages are displayed is also defined at the
profile level.
Note:
ITSmobile also includes the “ITSmobile Visual Editor”, which enables you to edit
screens and templates directly in SE80. For details, see SAP Note “1872180 -
ITSmobile Visual Editor // Main Note //”.
Presentation Device
Presentation devices classify the different kind of devices you use in your warehouse.
When defining a presentation device, you enter its characteristics, such as display profile,
presentation device type, data entry type, function keys quantity, various indicators, and
signal assignments.
The presentation devices can be assigned to a resource (which is part of resource
management).
Presentation Profile
The presentation profile (together with the personalization profile) is used to support different
menu structures for different users.
The presentation profile is assigned to the application (the standard application for SAP EWM
is 01).
The personalization profile is used to enable the customer to make changes to the SAP
standard. With the personalization profile you can support different user groups working in
different menus and different processes. The standard personalization profile is ‘**’.

RF Menu Manager
With the RF menu manager, you can define your own menus.
First, you create your menu items for the main menu and the submenus. Then, in the
hierarchy, you define whether a logical transaction is triggered (field LTRANS) or if the user
jumps to a submenu (field LMENU).
SAP delivers the default menu with application ‘01’, presentation profile‘****’, and
personalization profile ‘**’. These entries can only be maintained in an SAP system. In a
customer system, these entries are locked for changes.
Wizards
There are two wizards available, which are started directly from a running RF transaction with
Ctrl + Shift + F1.
Split Screen
This wizard guides you through the necessary steps to split the RF transaction screen
into several screens. These screens are then displayed in your preferred sequence. You
can also configure the function codes that are displayed in each resulting screen.
The Split Screen wizard includes the following steps:
● Assign fields to split screens
● Assign function codes to split screens / assignment
● Assign function codes to split screens / buttons
● Define target function group and screen numbers
● Define personalization profile
● Complete (creating the new screens and customizing in database)
Modify Screen
This wizard guides you through the necessary steps to modify an RF transaction screen.
Each time you add or remove fields from the screen, the wizard generates an updated
screen. To display the new screen to a specific group of users, enter the user's
personalization profile, the wizard will automatically adjust the Customizing. The new
screen is displayed in Screen Painter, where you can adjust aspects of the screen layout,
such as the position and field size.
The wizard contains the following steps:
● Select target screen fields
● Assign verification fields
● Define target function group and screen number
● Define personalization profile
● Complete (creating the new screens and customizing in database)
Pick by Voice
The pick by voice (PbV) functionality in SAP Extended Warehouse Management (EWM)
supports voice-based picking and internal moves in the warehouse, independently of the RF
picking transaction. It is based on the RF framework, the RF picking transaction, and the ITS

template generator, Mobile Devices with Speech Input. It supports bar code scanning and
voice-enabling.
The pick by voice transaction uses SAPGUI Dynpros whose fields have speech properties.
From these Dynpros, the system generates HTML templates using the ITS HTML template
generator Mobile Device with Speech Input. These HTML templates contain speech-specific
tags that are interpreted by the web browsers on the device.
The system interprets speech input either as a field input value or as a command. All possible
commands must be visible on the screen and represented by a button. The RF framework
supports up to 16 buttons. You cannot assign commands to function keys.
To trigger a command, you must switch to command mode by saying the built-in keyword
“Command”. Alternatively, the system automatically goes into command mode if you make
entries in all input fields.
Using the command “Okay” is equivalent to pressing Enter.
You can use the start transaction /SCWM/RFUI_PBV to start the RF framework, set a voice-
enabling parameter, and start the PbV transaction directly. This transaction is not part of the
SAP Easy Access screen. The Internet Communication Framework (ICF) service RFUI_PBV is
linked to this start transaction.
Figure 5: Pick By Voice
Adapting Verification Fields

The standard RF transactions require the verification of every single field. This is usually not
necessary, as information might be redundant. When you are picking from a handling unit
which is stored in the warehouse, it is probably not necessary to confirm the HU and the
source bin - as you have confirmed the bin during putaway of the HU already. The fields you
require to verify can be defined by a verification profile.

Figure 6: RF Verification Profile
Verification Profile
You can define as many verification profiles for your warehouse as you require; assigning the
verification objects to each profile. Examples for the verification objects are:
● Source storage bin
● Pick HU
● Quantity
Verification Profile Determination

Define the determination of the verification profile with any combination of the following
fields:
● Warehouse Number
● Warehouse process type
● Process category:
Process categories are for example, putaway, stock removal, or physical inventory
● Activity
● Activity area
In addition you can distinguish between the general data entry (an RF device with screen and
scanner) or voice recognition.
Asynchronous WT Confirmation and Pick-HU WT Creation

SAP EWM offers possibilities to improve performance during picking with RF. These are:
● Asynchronous Delivery Update:

During pick warehouse task confirmation, the system also updates the corresponding
outbound delivery order item. To improve the response time of the warehouse task
confirmation step, the system can perform the delivery update asynchronously in a
Remote Function Call (RFC) queue. You can activate asynchronous delivery update on the
SAP Easy Access screen under Extended Warehouse Management → Settings →
Performance Settings → Activate Asynchronous Delivery Update.
● Asynchronous Pick Warehouse Task Confirmation:
To improve the response time of the warehouse task confirmation step, you can activate
asynchronous pick warehouse task confirmation. With asynchronous pick warehouse task
confirmation, the system presents the next RF screen before updating the database. You
can activate asynchronous pick warehouse task confirmation on the SAP Easy Access
screen under Extended Warehouse Management → Performance Settings → Activate
Asynchronous RF Processing. The asynchronous pick warehouse task confirmation can fail
if, for example, the Customizing settings for the storage type allow the available quantity to
be a negative value.
● Asynchronous Creation of Pick-Handling Unit Warehouse Tasks:
The system creates the pick-handling unit (pick-HU) warehouse task from the resource to
the destination bin when confirming the first pick warehouse task into the HU. To improve
the response time of the warehouse task confirmation step, the system creates the pick-
HU warehouse tasks asynchronously in an RFC queue. The path is the same as that for the
Asynchronous Pick Warehouse Task Confirmation.
Note:
Use asynchronous processing only when necessary as quicker response times
increase system load, which can have a negative effect on the required system
sizing.
Figure 7: Synchronous vs. Asynchronous Warehouse Task Confirmation

Other Settings to Improve Performance

There are other settings available to improve RF performance:
● Switching Off Printing:
Warehouse task printing and HU printing are called during warehouse task creation and
warehouse task confirmation. The function modules call the Post Processing Framework
(PPF) which reads the relevant Customizing and calls the schedule condition for all active
PPF actions.
The schedule condition checks whether the warehouse process type or the packaging
material type has a determination procedure from the assigned condition technique. If
there is one, the condition technique is called, and based on the result, the system
determines whether or not to print. If you know that you do not want printing as part of this
process, you can control whether or not the PPF is called. You can set the value for the
field QUEUE_PRINT in the queue definition. The resource has as similar field
(RSRC_PRINT).
● Switching Off Messages:
With the RF framework, you can send messages from the warehouse management
monitor to resources. However, checking for potential messages can consume system
performance. Therefore, you can turn messaging off on the SAP Easy Access screen under
Extended Warehouse Management → Master Data → Resource Management →
Deactivate Messages to Resources.
Combining Warehouse Tasks

You can use combined picking in the radio frequency (RF) picking transaction to collectively
pick warehouse tasks with the same attributes. By doing this, you can avoid the picker having
to confirm the same source bin or source HU more than once during the processing of one
warehouse order.
Figure 8: Combine Warehouse Tasks
The warehouse tasks can be combined if they have the following matching attributes:

● Warehouse task attributes:

- Source bin
- Source HU
- Pick-HU
● Stock attributes:
- Stock key, for example, product, batch, party entitled to dispose, and so on
- Alternative unit of measure
● Optional attributes:
- Warehouse task consolidation group
Exception Handling
You can use the standard exception codes in the RF picking transaction. The exception codes
are applied to the combined warehouse tasks.
● Exception codes such as BIDU or BIDF can be used for full denial of the combined quantity.
The system applies the full denial to all the warehouse tasks that were combined.
● When the quantity in the storage bin is lower than the combined quantity and you still want
to perform combined picking, you can use exception codes such as BIDP to distribute the
partial quantity among the combined warehouse tasks.
Example: You have three warehouse tasks for picking the same product from the same
source location:
● Warehouse task 1: To pick 10 pieces of product A
A warehouse worker is asked to confirm the combined picking of 23 pieces of product A.

However, there are only 15 pieces of product A in the source location. The warehouse worker
can pick products even if the number of products is lower than the number specified in the
system. The worker enters the BIDP exception code. The system performs the following pick
confirmation:
● Warehouse task 1: 10 pieces Full Pick
● Warehouse task 2: 5 pieces Partial Pick
● Warehouse task 3: 0 pieces Full Denial
You can use the SPLT exception code to split the product quantity of the combined
warehouse tasks into different quantities.
You can choose the F3 UnCom button to cancel the combination of warehouse tasks that
were combined previously by the system.
LESSON SUMMARY
You should now be able to:


Unit 1
Lesson 2
Managing Resources
LESSON OVERVIEW
In this lesson, you learn how to set up resources in SAP Extended Warehouse Management
(EWM).
LESSON OBJECTIVES
Resources in EWM
A resource is an entity representing a user or equipment that can execute work in the
warehouse.
It can log on to a radio frequency (RF) or non-RF environment. Once the resource is logged on
to the system, it can receive work for execution and it can be tracked and displayed in the
warehouse management monitor.
A resource belongs to a resource type (a grouping of resources with similar technical or
physical qualifications) and a resource group (a grouping of resources for queue assignment
purposes).
Note:
Although a resource can work in a non-RF environment, several features of
working with resources are only available when using mobile devices.

Figure 9: Resources in EWM
Resource Management
Resource management maximizes the efficiency of warehouse processes by:
● Facilitating the management and distribution of work using queues
● Enabling the execution of work by resources in an RF and non-RF environment
● Optimizing the selection of warehouse orders for resources requesting work
● Enabling effective monitoring and controlling of resources
Assignment of Warehouse Orders to a Resource

Warehouse Orders (WOs) can be assigned to resources in RF and non-RF environments.
In an RF environment, WOs can be assigned manually or automatically. In a non-RF
environment, WOs are assigned manually.
For automatic WO assignment to a resource, the WOs must belong to a queue to which the
resource is assigned.

Lesson: Managing Resources
Figure 10: Assignment of Warehouse Orders to a Resource
Warehouse Order (WO) Assignment to a Resource

Non-RF Environment RF Environment
1 - A resource logs on to the RF environment
2 The warehouse manager assigns the WO One of the following occurs:
to the resource using the Assign Rsrce
● The warehouse manager assigns a WO
monitor method.
to the resource using the Assign Rsrce
3 The warehouse manager prints out the warehouse management monitor
WO and gives it to the resource. method.
● The resource requests work by choos-
ing a system-guided option from the
RF menu. In such a case, the system
assigns the most appropriate WO to
the resource.
● The resource requests work by choos-
ing a manual option from the RF menu
(for example, Pick by HU). In such a
case, the system assigns to the re-
source the specific WO.
Hint:
Any available WOs can be manually assigned to a resource, including those from
queues to which the resource is not assigned.

Queues
A queue is a logical file to which warehouse orders for processing are assigned. Queues define
movements by which work in the warehouse is managed and assigned.
The management and distribution of work in the warehouse is accomplished by the
assignment of resources and WOs to queues. In addition, a resource working within a
particular operating environment may execute only those WOs that belong to a queue in the
same operating environment.
Note:
You assign the operating environment of a queue during queue definition in
customizing. The operating environment of a resource is determined when the
resource logs on to the RF or non-RF environment.
Figure 11: Queues
Assignment to Queues
Resource Assignment to Queue
You can assign a resource to a specific queue, or assign its resource group to a sequence of
allowed queues. WO selection is performed according to the resource’s assigned queue, and,
in the absence of an assigned queue, according to the resource group’s queue sequence.
Warehouse Order Assignment to Queue
When the system creates a WT, it searches for an appropriate queue to assign to it, based on
the following WT parameters:
● Source activity area
● Destination activity area
● Bin access type
● Warehouse process type
● Activity

Note:
That means that the queue determination is for each warehouse task, but in the
end the queue is only visible in the warehouse order. Which also means that the
WTs in one WO must find the same queue. It is an automatic sort criteria in the
warehouse order creation rule (like the activity area).
Resource Setup
You define a resource in the transaction for resource maintenance. On the EWM Index screen,
choose Extended Warehouse Management → Master Data → Resource Management →
Maintain Resource.
Figure 12: Resource Setup
Resource Type
A resource type is a grouping of resources with similar technical or physical qualifications.
The resource type determines the following for its corresponding resources:
● Horizontal and vertical velocity:
The velocity of a resource can influence the latest starting date (LSD) of a warehouse
order.
● Applicability of position management:
Position management enables an RF device user to validate HUs by their position number,
rather than by their HU number. This is particularly useful when the HU number tags are
not readily accessible, such as when the HUs are stacked on top of each other.
● Layout type:
The layout type is used for the pick by cart app and for the resource-based warehouse
order optimization.

● Qualifications and preferences (reflected by priority values) regarding bin access types
and HU type groups.
Resource Group
A resource group is a grouping of resources for queue assignment purposes. The resource
group determines the sequence of allowed queues for its corresponding resources, which can
influence which warehouse orders are selected for a resource.
To use system-guided processing, the queues must be assigned to the resource groups in the
desired sequence. As the WOs are selected from the queues according to the queue
sequences, this represents a prioritization of the WOs for this resource type.
Resource Execution Constraints

Resource execution constraints allow you to control the number of working resources in
defined areas of the warehouse. You define these areas by assigning a resource execution
constraint (REC) storage group to your storage bins.
The individual REC storage groups can correspond to an aisle, storage section, storage type,
or another area in your warehouse. You can define the maximum number of permitted work
resources for these REC storage groups in such a way that the resources can perform your
work without disruption.
Figure 13: Resource Execution Constraints
Resource Types
The REC consists of a group of different resource types, each having a maximum number of
work resources. You identify the group uniquely using an ID. You can assign the same ID to
different REC storage groups, and define whether:
● Only one resource type is allowed to be kept in the REC storage group at a time (parameter
OR).
● Multiple different resource types are allowed to be kept in the REC storage group at a time,
for example, a forklift and a warehouse worker. For each resource type, the maximum
defined number of work resources in the REC storage group is allowed (parameter AND).

For example, resource types RT01 and RT02 are assigned to resource execution constraint
A1, with a maximum number of two and three respectively. REC storage group GAN is
assigned to constraint A1 with the parameter "AND". This means that a maximum of three
resources of type RT02 and two resources of type RT01 can work in A1 at the same time.
Calculated Times
The REC control is based on calculated times. Each time a resource enters the REC storage
group, the system calculates the estimated exit time. This time includes the following:
● Move time for moving the resource from the current position to the entry point of the REC
storage group
● Working time in the REC storage group
● Exit time of the resource from when it leaves the location of the last completed warehouse
task to the exit point of the REC storage group
When a resource wants to enter the REC storage group, the system compares the estimated
exit times of the resources working in this area with the entry time of the resource. The
system calculates the times, compares the calculated values with the number of permitted
resources, and allows or denies the resource access to the REC storage group.
The system calculates optimal routes for the resources based on the travel distance
calculation. The actual times may deviate from the optimal times.
This function works using the average confirmation time for warehouse tasks. If you have
activated LM in your SAP EWM system, the system uses the engineered labor standard
values. If you are not using LM, you must define the extract time determination for warehouse
tasks.
Pick By Cart
With the pick by cart app, you can pick multiple orders with a pick cart in a single trip through
the warehouse. For the app you have a tablet which shows you the individual positions of the
pick-HUs on the pick cart.
Figure 14: Pick by Cart

The app works inside the standard RF framework. The user works with a warehouse order
which is automatically assigned by the queue, or he chooses a warehouse order manually.
The user cannot choose the queue in which they want to work.
LESSON SUMMARY

Unit 1
Lesson 3
Distributing Work to Resources
LESSON OBJECTIVES
Warehouse Order Selection

A warehouse order (WO) can be directly assigned to a resource, for example by the
warehouse manager, or the resource can manually select a WO. The expectation is that
resource work system-guided, means that the system automatically assigns the next WO
after a WO has been completed. For this assignment several things are checked and the WOs
are sorted automatically.
Figure 15: Distribute Work to Resources
First the system checks if a queue is directly assigned to the resource. If that is not the case,
the system checks the resource group which is assigned to the resource, and the queues in
the sequence assigned to the resource group.
When there is more then one queue assigned to the resource group, the system always
assigns a WO from the first queue in the sequence (if no other conditions are violated). The
next queue is only used if the queue before is empty, or if no WO can be assigned. For
assigning WOs from alternating queues, you need to look up “task interleaving”.

A resource also can select system-guided by queue: then the sequence of queues is not
observed - but a resource group with this queue must still be assigned to the resource.
Skipping Warehouse Orders

In system-guided picking, a resource can skip a warehouse order because, for example, the
source storage bin is blocked. However, you can skip a warehouse order only if it hasn't been
started yet, meaning that there are no confirmed warehouse tasks. You skip a warehouse
order using exception code SKWO and the resource can then continue with the next
warehouse order which is assigned to it.
When you skip a warehouse order, it isn't skipped permanently as the system still proposes
the warehouse order to other resources. Also, the system can propose a skipped warehouse
order to the same resource again after that resource either started working on another
warehouse order, or re-entered the RF transaction.
Note that you can't skip warehouse orders in combination with pick, pack and pass, or when
using pick-by-voice features.
Warehouse Order Sorting

The warehouse orders are sorted as follows:
● In ascending order, by latest starting date
● In descending order, by execution priority
Figure 16: Warehouse Order Sorting
Latest Starting Date

The latest starting date (LSD) is the latest time by which execution of a WO should
commence, so that it is completed by the due date.
Note:
Latest starting date does not mean that the WO can not be started before, it only
shows which WO is due first.
The LSD for each WO is calculated as follows:
● Latest Starting Date = WO due date - (planned execution duration + planned travel time
duration).
The due date is taken from one of the following:

Lesson: Distributing Work to Resources
● The picking completion date in the warehouse tasks (WTs). This would come from a wave
template and the selected option. If the warehouse request is not part of a wave, the
completion time can also be set by the durations assigned to process steps in the
warehouse process that is used.
● If there is no picking completion date in the WT, the planned goods issue date in the
warehouse request.
Note:
The standard document type for outbound processes in EWM, “OUTB”, only
includes a “goods issue” time or date on the item level. On the header level you
can find a “departure from yard” time. This time is determined from the goods
issue times on item level (so it corresponds to that time).
● For lack of relevant dates in inbound deliveries, the due date is calculated using the
“planned duration of movements” time. This duration is defined in Customizing (SCM
Extended Warehouse Management → Extended Warehouse Management → Cross-
Process Settings → Warehouse Task → Define Planned Duration of Movements in
Warehouse). The "due date" is then calculated from the current time using the maintained
duration. This is superseded again if planned durations are assigned to the process steps
in the warehouse process that is used.
The planned execution duration in the warehouse order is calculated using various
information, depending on the settings and activated options.
When labor management is not used, the system calculates the extract time for each
warehouse task. The formula for this calculation is:
● E=X+qxY
- E is the extract time.
- X is the constant portion of the extract time.
- Y is the variable portion of the extract time.
- q is the quantity for which the extract time is to be calculated.
For the calculation you can define the following details:
1. Unit of measure load categories. The unit of measure load category is assigned to a unit of
measure from the product or to a handling unit type.
2. Product load categories. This is used to group products that are similar with regards to
their workload and handling. It is assigned in the warehouse product.
3. Warehouse activities. A warehouse activity for the extract time calculation is assigned to a
warehouse process category (like putaway or stock removal). It is a 1:1 assignment to the
warehouse process category, so it is usually sufficient to define a stock removal and a
putaway activity.
4. Extract time calculation. In the extract time table, you can define a constant and a variable
extract time in seconds for each warehouse number, bin access type, warehouse
operation, UoM load category, and product load category.

5. Optimize the access strategy. You can define multiple access strategies for each
warehouse number that are processed in the sequence specified. If no suitable entry is
found in the extract time table, the next table entry is tried.
E is then doubled in the warehouse task.
Note:
By design the system calculates the extract time for the source and for the
destination bin. As you can use the bin access type for the extract time calculation,
you can therefore calculate the time properly depending on the bin (access type).
If the bin access type is not used in the calculation, the result in the warehouse
task will always show double the time of what is set up in customizing.
If a preparation time is assigned in the warehouse order creation rule, this is added to the
extract time in the warehouse order. The standard rules UNDE and DEF have no preparation
time.
If the warehouse order is relevant for labor management, then the complete planned
execution duration of the WO is calculated using engineered labor standards. For details see
the course EWM125 - Labor Management in SAP Extended Warehouse Management.
The planned travel time duration is calculated by using the travel distance calculation and
using the resource with the slowest velocity. Details about the travel distance calculation are
described separately.
The LSD can be rounded off by the relevant mode.
Mode
A mode determines the following:
● Weighting factors used for warehouse order execution prioritization
● Time intervals and units of measure for round the LSD
In the warehouse task, the mode is set either:

● By the wave. The mode can be included in the wave template, or it can be assigned directly
when manually creating a wave.
● By determination for the warehouse number and the activity.
As the mode is set for each warehouse task in a warehouse order, the system uses the
rounding time interval of the mode of the first WT in the WT sequence.
Note:
The mode only influences the LSD, not the planned duration in the WO.
Warehouse Order Execution Priority

Warehouse order (WO) prioritization ensures that the system selects the most suitable WO
for a resource. For the full calculation you maintain the following:
● For a resource type the priorities are for:
- Bin access type (BAT) and

- HU type group (HUTG)
The priority values reflect the preferences of a resource type to work in a particular bin
access type, or with a HU type group.
● The warehouse process type (WPT) priority.
Note:
While the documentation mentions the warehouse process category, the
assignment is actually to the warehouse process type.
The priority is a value between 1 and 10.

Then you maintain the priority weightings per mode (a value between 1 and 100). The
weighting of a priority parameter reflects the relative importance of the parameter in
determining the total priority of a warehouse task (WT). The weightings may vary according
to activity, which is reflected by the mode.
The execution priority is calculated for each WT with the following formula:
● Priority = (BAT Weighting / 100 x BAT Priority Value) + HUTG Weighting / 100 x HUTG
Priority Value) + (WPT Weighting / 100 x WPT Priority Value)
The weightings are based on the mode of the first WT in the WT sequence.
The total priority of the WO is set from the highest priority of its constituent WTs.

Note:
Sometimes during warehouse order processing the problem might come up that
one specific warehouse order needs to be processed as soon as possible and the
question comes up: how do you make sure that this happens?
Technically you have options like:
● Assign the WO to one specific resource. If the resource is currently not
processing another WO, that is an option. But then you must know where the
resource is and if there are other issues which may prohibit the resource from
working.
● Change the latest starting date. It is possible to change the date and time, so
then the next resource in this queue will get this WO.
The best option is actually:

● Assign the WO to the Express Queue.
What is the “Express Queue”? You can define a queue which is assigned to all
relevant resource groups at the first position. This way whatever next resource
is available in any of these resource groups will get this warehouse order (you
have to consider of course if all resources are able to process this WO, in a
complex warehouse your assignments of bin access types and HU type groups
might limit that).
Additionally, such an express queue could also be found based on the queue
determination criteria (like activity, warehouse process type) to make sure that
specific WOs, for example, express orders are processed first, independent of
all other settings.
Travel Distance Calculation Method

The travel distance calculation calculates the distance that a warehouse worker must travel to
execute a warehouse order. In addition to calculating the travel distance, the system
determines the time required by a worker to execute the warehouse order, depending on the
speed of the resource used.
The result of the travel distance calculation is used for:
● Calculating the latest start time for a warehouse order
● Calculating engineered labor standards (ELS) and the workload, if you have activated
Labor Management (LM)
Methods for Travel Distance

SAP EWM uses two different methods for the distance calculation:
● Direct distance:
The system calculates the travel distance using the direct distance, based either on the
Euclidean metric or Manhattan metric. The upper part of the following figure shows the
direct distance between two storage bins of a storage type. The solid line corresponds to
the Euclidean metric; the dotted line represents the Manhattan metric.
● Distance based on networks:

The travel distance calculation can also be based on an existing valid network. The valid
routes represent the edges. The lower part of the following figure shows the distance
between two storage bins of a storage type. The resource moves across the valid routes.
Travel Distance Calculation
Figure 17: Travel Distance Calculation
Calculating the Travel Distance

The system calculates the travel distance needed to execute a warehouse order more than
once, namely when:
● Creating a warehouse order for planning purposes
● Confirming a warehouse order for evaluation purposes
When calculating the distance while creating the warehouse order, the system uses the
following values:
● For the speed, the system uses the speed of the slowest resource (pessimistic approach).
● Instead of the known position of the resource, a default distance to be covered to reach the
first position in a storage type is specified.
● The route network used (if available) contains all defined routes without resource type
restrictions.
The executing resource is only known after the confirmation, so then the system is able to
access more detailed information, like:
● Speed of the resource
● Last position of the resource prior to executing the warehouse order
● The route network allowed for the resource, if available
If LM is activated, the system saves the result of the travel distance calculation in the planned
and executed workload.

Networks
Networks define the valid routes (paths) in the warehouse on which the resources move. A
network consists of edges and nodes. Edges are connected to each other by way of nodes.
Edges represent the valid routes in the warehouse, and nodes represent crossings.
There are two different kinds of networks:
● Storage-type-specific networks:
These networks consist of edges that map the individual aisles, and edges that represent a
connection of different aisles. You assign storage bins of a storage type to:
- An edge, if the storage bins are located in an aisle, and an edge exists for the aisle
- A node that matches your X and Y coordinates, if you have not assigned an edge
● Global networks:
The global network connects the defined, storage-type-specific networks to each other. If
no storage-type-specific networks are defined, the network connects the storage bins to
each other directly.
Figure 18: Travel Distance Calculation with Storage-Type-Specific and Global Networks
Edges
Edges have the following properties:
● Each edge has a start node and end node.
● An edge is usually passable in both directions, however it can also be defined as a one-way
street. The direction is defined through the start and end nodes.
● For each edge, you can define which resource types are allowed to pass.
● You can assign an edge to an aisle.
● An edge has a length that is used by the system to calculate the travel distance, if the edge
is passed by a resource.

Defining Networks
You can use the program, Generating Storage-Type-Specific Networks, to generate storage-
type-specific networks for the travel distance calculation in SAP EWM automatically.
On the SAP EWM Index screen, choose Extended Warehouse Management → Settings →
Travel Distance Calculation → Generate Network. The edges for the aisles automatically have
the following properties:
● Edges are only created for aisles that have more than one storage bin.
● Edges can be passed in both directions.
● The length of the edges corresponds to the Euclidean distance between the start and end
nodes.
● If storage bins are located on both sides of the aisle, the edges are located in the center of
the aisle.
● If there are only storage bins on one side of the aisle, the edges lie half a bin depth away
from the aisle.
● The edges start and end outside the aisle (half a bin depth).
The system generates connecting edges between neighboring aisles by connecting both the
start and end nodes of two neighboring aisles with an edge.
The storage-type-specific network can also be created manually, but it is possible and
therefore better to change settings like the direction (unidirectional, bidirectional) after the
generation by the system. You can also exclude resource types from edges. In addition, you
can add an average distance for a storage type, this is the distance that is used when the
resource and the start point is not known (Customizing, in the definition of the storage type).
You can define global networks manually and make the following settings for the edges:
● X and Y coordinates for the start of the edge
● X and Y coordinates for the end of the edge
● Define edge direction (unidirectional, bidirectional)
● Define edge length in the unit of length of the warehouse number
● Define excluded resource types
Both types of networks (storage-type-specific and global) can also be uploaded with the help
of a CSV file. This feature was introduced with SAP EWM 9.5.
Travel Distance Calculation

The travel distance is calculated for the storage bin list. A storage bin list is a list of storage
bins that are to be approached sequentially for a warehouse order.
Features
● The system differentiates between horizontal (X and Y coordinates) and vertical
movements (Z coordinates).
● The total travel distance is the sum of travel distances between the storage bins lying next
to each other on the list.

● The system generates the list of storage bins from the warehouse order creation rules. The
order is fixed, meaning the travel distance calculation does not sort the storage bin list.
For the movements, we assume the following:

● The resource moves to the storage bin in a horizontal direction.
● The resource then executes the vertical movement to the storage bin and back to the floor.
● The resource then moves to the next storage bin in a horizontal direction.
● The total travel distance in a vertical direction therefore corresponds to twice the Z
distance of the storage bins to the floor (point of origin Z = 0).
For horizontal movements, a distinction is made between direct movements and movements
within a network.
Direct Movements
This system uses the direct distance for the following movements:
● Movements between storage bins within a storage type, if no valid storage-type-specific
network is available
● Movements between storage bins from different storage types, if no valid global network
exists
● Movements within an aisle. Here, the direct distance between storage bins is used to
calculate the travel distance
Figure 19: Direct Movements within an Aisle
Connecting Storage Bins with the Network

A storage bin can be connected with the network in the following ways:
● With the nodes of an edge, if the storage bin is in an aisle, and an edge exists for the aisle.
Fundamentally, four options exist. For a one-way route, only one option is allowed —
entering the edge at the start node and leaving it at the end node.
● With the next node, if no edge has been assigned (the node comes from the storage-type-
specific network, or if the storage-type-specific network does not exist, the node comes
from the global network).

Figure 20: Connections of Storage Bins with the Network
Movements within a Network

Movements within a network take place if the storage bins are located as follows:
● In the same storage type but not in the same aisle, and a valid storage-type-specific
network exists
● In different storage types and a valid global network exists
For the calculation within the network (valid global network and any existing valid storage-
type-specific networks), the system connects the storage bins with the nodes of the
respective edge or with the next node. Then, the travel distance within the network between
the storage bins is added to the assigned nodes. Four options are available for this
calculation: 1) from the start node of the first edge to the start node of the second edge, 2)
from start node to end node, 3) from end node to start node, and 4) from end node to end
node.
Examples for the Travel Distance Calculation
The following are some examples for the calculation of the travel distance:
● Travel distance calculation within a storage type
● Travel distance calculation between two storage types with valid networks
● Travel distance calculation between two storage types with a global valid network
Travel Distance Calculation within a Storage Type

The warehouse manager wants to calculate the travel distance from storage bin 1 to storage
bin 3 within a storage type with a valid network.
1, 2, and 3 are storage bins from which warehouse worker X withdraws goods.
The travel distance comprises the following:
● Direct distances A (within an aisle), B, and D (connection between storage bin and
network)

● Distance C (connecting edge) within the network
Of the four possible calculations, the system uses the first option as that represents the
shortest travel distance.
Figure 21: Travel Distance Calculation within a Storage Type
Note:
The sequence of the storage bins is defined in the sort rule of the warehouse
order. The sequence is fixed, meaning the travel distance calculation calculates
the shortest distance, but does not change the sequence of storage bins.
Travel Distance Calculation Between Two Storage Types with Valid Networks
This example shows a travel distance calculation between two storage types that each have a
valid storage-type-specific network and a valid global network.
● Direct distances A and C (connection between storage bin and network)
● Distance B within the entire network (local and global)

Figure 22: Two Storage Types with Storage-Type-Specific Networks
Travel Distance Calculation Between Two Storage Types with a Valid Global
Network
This example shows the travel distance calculation between two storage types with a valid
global network.
Only one storage type has a valid network.
● Direct distances A and C (connection between storage bin and network)
● Distance within network B
Figure 23: Two Storage Types with One Storage-Type-Specific Network

Heuristics for the Travel Distance Calculation

Two heuristics exist for the travel distance calculation within a network. The system calls both
by default. You can control the heuristics using the Business Add-Ins (BAdIs) for the travel
distance calculation.
● Depth-first search:
This system attempts to find a route between the specified nodes of a network in the
shortest time possible. Here, the search runs in the direction of start node to end node.
The search finishes when the first complete route is found.
● Breadth-first search:
The system looks for all possible routes in the network, and selects the one that has the
shortest distance. This heuristic is more performance intensive at runtime, and is only
appropriate for small networks.
The stopping criterion quickens the breadth-first search. This may have a negative impact
on the solution quality, and the system may fail to find the shortest route. The parameter
restricts the number of nodes that can be visited by a route, in relation to the route found
by the depth-first search.
BAdls for the Travel Distance Calculation

The following BAdIs are available:
● Change storage bin list for travel distance calculation /SCWM/EX_TDC_BIN_LIST
You can do the following:
- Sort the list
- Delete storage bins from the list
- Add new storage bins to the list
You can also influence the default distance to the first storage bin in the storage bin list.
● Travel distance calculation using the storage bin list /SCWM/EX_TDC_START
The system calls this BAdI to calculate the travel distance of a warehouse order. If you
implement this BAdI, you can define your own logic for calculating the travel distance
along the sorted storage bin list transmitted to the BAdI.
Travel Time Calculation

The main goal of calculating the travel distance is to use it for a travel time calculation.

Figure 24: Travel Time Calculation
Default Travel Time Calculation

By default, the total travel time is calculated as follows: Horizontal travel time + Vertical travel
time = Total travel time. The horizontal travel time is calculated using the total horizontal
travel distance and the horizontal speed for the resource type. The vertical travel time is
calculated using the total vertical travel distance and the vertical speed for the resource type.
Travel Time Calculation Using BRFplus
If you want to use a more complex travel time calculation, you can maintain your own set of
calculation rules in BRFplus. SAP EWM provides a standard BRFplus application /SCWM/
TDC_SYS and function /SCWM/TDC_CALC_TIME to which you can assign your own rulesets.
The interface of the standard function includes the following:
● The total horizontal travel distance
● The total vertical travel distance
● Consolidated section information of horizontal movements
● Section information of vertical movements
● Resource type information (such as speed)
● Business information (such as activity area)
When you define your own rules, you can use any or all of the above information as input.
In contrast to the total travel distance, consolidated section information lets you consider
each section of the calculated travel path separately. For example, you might want to
consider turns and stops in the travel path, because they limit the maximum speed of a
resource. The shorter a straight segment is, the less likely it is for the resource to travel at its
maximum speed.
SAP Warehouse Insights

SAP Warehouse Insights is an advanced planning tool to optimize warehouse operations. It
visualizes the warehouse layout, analyzes warehouse operation KPIs, simulates resource
utilization, and optimizes warehouse operations in real time. SAP Warehouse Insights is not a
new Warehouse Management System, hence it does not execute warehouse tasks such as

pick, putaway, etc. It complements SAP Extended Warehouse Management’s functions and
capabilities by leveraging cloud computing and scalability. SAP Warehouse Insights is built
and delivered on the SAP Cloud Platform.
Figure 25: SAP Warehouse Insights
If you are interested to get more information about SAP Warehouse Insights, go to the SAP
Help Portal (https://help.sap.com) and search for “warehouse insights”.
LESSON SUMMARY

Unit 1
Lesson 4
Optimizing The Work of Resources
LESSON OBJECTIVES
System-guided versus Semi-system-guided Work

You can use semi-system-guided processing within system-guided processing. This is useful
for source storage bins that have more than one HU. In system-guided processing, the
system proposes one particular HU to the user for processing. Finding this particular HU can
prove time-consuming. If the source storage bin contains multiple HUs, it is more efficient if
the system instructs the warehouse worker to go to a particular source storage bin and
remove any HU.
Figure 26: System-guided and Semi-system-guided Work
Semi-system-guided Processing
To use this function, you set the queue to semi-system-guided processing. When selecting a
WO, the system checks if a queue has been set to semi-system-guided processing. If it has,

the system sets the session to semi-system-guided. This affects processing in the following
ways:
● The user verifies the source storage bin only.
● The HU field is empty. The user can scan it.
After scanning, the system checks whether:

● The scanned HU is available in the specified storage bin.
● An open warehouse task exists for this HU.
● The reported resource is allowed to process the HU.
Note:
To use semi-system-guided processing, it is necessary that one warehouse order
contains only one warehouse task/handling unit. The queue does not control this,
but if your warehouse order contains more then one HU, processing leads to an
error in the RF dialog.
System-guided Processing Semi-system-guided Processing
The screen shows you various data, such as You only see the source storage bin and the
HU, product, quantity, batch, and so on. input field for the HU.
The warehouse task is locked. The warehouse task is not locked, because it
is still not clear which HU is being selected.
The semi-system-guided processing screen contains a button that allows you to activate the
display of available HUs. You can also trigger other queries for the HU, such as a queue or a
storage bin.
Task Interleaving
The aim of task interleaving is to minimize not utilized resources through an optimized
distribution of the warehouse tasks, and to reduce the travel times in the warehouse. For
example, after putaway, a forklift does not return empty to the goods receipt area. Instead, it
is given a new task before returning to that area, such as a stock removal order.

Lesson: Optimizing The Work of Resources
Figure 27: Without Task Interleaving
With Task Interleaving

After completing a WO, the system immediately assigns a new warehouse order to the
warehouse worker, which is from a different queue.

Figure 28: With Task Interleaving
RF Interleaving
You set RF interleaving for resource types. You assign each interleaving-relevant queue to a
queue type and to a queue sequence.
RF Interleaving Standard RF Function
1. The resource processes a warehouse order 1. The same queue is processed until it is
from a queue. empty.
2. The subsequent warehouse order comes 2. The next queue is processed according to
from another queue, based on the defined the defined queue sequence.
queue type sequence.
Caution:
This function is only available within system-guided processing.
Resource-based Warehouse Order Optimization

When the system creates a warehouse order for warehouse tasks, it is not known yet which
resource is to process the warehouse order. This means that the limit parameters in the
warehouse order creation rule must be modeled to fit the smallest resource of all the
resources working in the same activity area. This leads to unsatisfactory assignments in other
cases, where a resource, which can handle a bigger load or a higher number of HUs, is not
fully utilized.

Lesson: Optimizing The Work of Resources
Figure 29: Resource-based Warehouse Order Optimization
The BAdI /SCWM/EX_RSRC_REBUNDLE can be used to group warehouse tasks of existing

warehouse orders into a new warehouse order to be processed next by a resource. The
example implementation /SCWM/CL_EI_RSRC_REBUNDLE determines the capacity of a
resource type and then the corresponding handling unit (HU) warehouse tasks that need to
be grouped into new warehouse orders.
LESSON SUMMARY


Unit 1
Lesson 5
Setting Up the Pick, Pack, and Pass Process
LESSON OVERVIEW
In this lesson you learn about the pick, pack, and pass process during picking. You learn about
the features and requirements of the pick, pack, and pass function. You also learn about
warehouse orders for pick, pack, and pass.
LESSON OBJECTIVES
Pick, Pack, and Pass During Picking

You use this function to coordinate picking, packing, and the transportation of products in
different activity areas of your warehouse. For example, you transport products from one
activity area to another using a conveyor belt. From an organizational point of view, an activity
area can correspond to an aisle for which a warehouse worker is responsible. When the
warehouse worker has picked a WO in an area, the goods are passed to the next area.
Figure 30: Pick Pack and Pass Process
The movement from one activity area to the other can be done by an automatic conveyor
system. There may also be pick-to-light systems in the various zones to support the picking
process within the zone.
Features of the Pick, Pack, and Pass Function

You can use pick, pack, and pass only in an RF environment. The process flow is the same as
for standard RF picking.

The destination storage bins are different when using pick, pack, and pass in comparison to
standard RF picking. In pick, pack, and pass, warehouse workers pass the product from
activity area to activity area until it arrives at the destination storage bin.
Picking Destination Storage Bin
RF picking A destination storage bin, such as goods is-

sue area
RF picking using pick, pack, and pass An end point of an activity area from where
the product moves to the next activity area
You can use a system-controlled pick, pack, and pass function or a user-controlled pick, pack,
and pass function.
System-controlled Pick, Pack, and, Pass Function
With this setting, the system specifies the sequence for processing the WOs and
corresponding pick HUs.
It creates a higher-level WO that contains all the WOs that have been created. Only the first
WO in the sequence is active; all other WOs are inactive. The sequence in which the system
orders the WOs corresponds to the sequence that you have defined in Customizing for the
activity areas in the WO creation rules.
1. During WO creation, the pick HU determination determines the suitable pick HUs for all
WTs of the WO.
2. The system checks the WO type. If you activated the pick, pack, and pass function, the
system creates a higher-level WO that contains multiple WOs sorted by activity area. The
system only passes on the standard WOs to resource management in SAP EWM.
User-controlled Pick, Pack, and Pass Function

With this setting, the system creates the WOs and the corresponding pick HUs the same as
for the system-controlled pick, pack, and pass function. However, all created warehouse
orders are active, and no sequence for processing them exists. The user takes a warehouse
order that is valid for a specific activity area.
Requirements for Pick, Pack, and Pass
Figure 31: Activity Areas Start and End Points for Pick, Pack, and Pass

Lesson: Setting Up the Pick, Pack, and Pass Process
Each picking zone must be mapped as an individual activity area. Additionally, the activity
areas must be joined, and for the system-driven option they must be in the required sort
sequence.
If you work with the system-driven method, you have to define which bins represent the start
point and end point for each picking zone.
You need a WO creation rule that supports the top WO creation for the pick, pack, and pass
process.
The creation categories for this are:
● System-driven: The sequence of the WOs in the top WO is determined according to the
sort sequence of the assigned in the configuration settings for joining the activity areas.
● User-driven: The sequence is manually determined during the execution, which means it
can also be done by the material flow system (MFS).
Warehouse Orders for Pick, Pack, and Pass

If you use pick, pack, and pass, the system creates a higher-level WO that contains the pick
HUs for all WTs that are to be created, which you pick one after the other. The warehouse
worker also receives the WO created for an activity area, together with its warehouse tasks.
Figure 32: Warehouse Orders for Pick, Pack, and Pass
Warehouse Scenario
The warehouse workers pick in the three activity areas PP01, PP02, and PP03 in a system-
controlled way using pick, pack, and pass.
1. The system creates a higher-level warehouse order containing several warehouse tasks
for the three activity areas PP01, PP02, and PP03, and determines the pick HUs for all
warehouse tasks.
2. It then distributes the warehouse tasks across the three activity areas.
3. Each of the three warehouse workers receives their own warehouse order.
4. The first warehouse worker takes the pick HU from the start point of the first activity area.
5. The worker performs picking and drops the pick HU at the end point of the activity area.

6. The pick HU is moved from the end point of the activity area to the start point of the next
activity area.
7. The process is repeated from step 4. When it comes to the final activity area (PP03), the
worker puts the pick HU in the original destination bin, such as the goods issue area,
instead of in the end point of the activity area.
Note:
Usually, you would not want the worker from the last activity area to move to
the goods issue area, the worker should also drop the pick HU at the end point.
To achieve this, you would use layout-oriented storage control.
LESSON SUMMARY

Unit 1
Learning Assessment
1. The SAP RF framework offers which of the following RF functionalities?

Choose the correct answers.
X A Work execution transactions for warehouse processes
X B Split screen
X C Logon
X D Log off
X E Recovery
2. What do you have to define to adapt verification fields in RF screens?

X A A verification profile
X B The verification profile determination
X C A combined picking profile
3. What matching attributes must exist for a combined picking profile?

X A Source bin
X B Pick HU
X C Start date
X D Product
4. WOs can only be assigned to resources in non-RF environments.

Determine whether this statement is true or false.
X True
X False

Unit 1: Learning Assessment
5. Which options does a user have for the selection of the warehouse order, when working
with the Pick by Cart app?
X A The user manually selects the warehouse order.
X B The user chooses a queue and processes the warehouse order which is assigned to
him.
X C The user processes the warehouse order which is assigned to him by a queue.
6. How are warehouse orders sorted for automatic assignment?

Choose the correct answer.
X A By latest starting date in ascending order and by execution priority in descending

order
X B By latest starting date in ascending order and by number of warehouse tasks
X C By storage type
7. What is the travel distance calculation used for?

X A To sort the warehouse tasks in the optimum sequence
X B To determine the optimal resource for execution
X C To calculate the required travel time.
8. SAP EWM uses the direct distance and distance based on networks to calculate the travel
distance.
X True
X False
9. When working with semi-system-guided queues, after scanning the system checks which
of the following?
X A The scanned HU is available in the specified storage bin.
X B The HU field is empty.
X C An open warehouse task exists for this HU.
X D The reported resource is allowed to process the HU.

Unit 1: Learning Assessment
10. What is the function of task interleaving?
11. What are the requirements for pick, pack, and pass?
X A A WO creation rule
X B Queue types
X C Define which bins represent the start point and end point for each picking zone
X D Each picking zone must be mapped as an individual activity area

Unit 1
Learning Assessment - Answers
1. The SAP RF framework offers which of the following RF functionalities?

X A Work execution transactions for warehouse processes
X B Split screen
X C Logon
X D Log off
X E Recovery
Correct. In the SAP RF framework, you can use work execution transactions for
warehouse processes and use the logon, log off, and recovery function.
2. What do you have to define to adapt verification fields in RF screens?

X A A verification profile
X B The verification profile determination
X C A combined picking profile
Correct. You have to define a verification profile and verification profile determination to
adapt verification fields in RF screens.
3. What matching attributes must exist for a combined picking profile?

X A Source bin
X B Pick HU
X C Start date
X D Product
Correct. Matching attributes of warehouse tasks to be combined are the source bin, the
pick HU, and the product.

Unit 1: Learning Assessment - Answers
4. WOs can only be assigned to resources in non-RF environments.

X True
X False
Correct. WOs can be assigned to resources in RF and non-RF environments.
5. Which options does a user have for the selection of the warehouse order, when working
with the Pick by Cart app?
X A The user manually selects the warehouse order.
X B The user chooses a queue and processes the warehouse order which is assigned to
him.
X C The user processes the warehouse order which is assigned to him by a queue.
Correct. When working with the Pick by Cart app the user manually selects the warehouse
order and processes the warehouse order which is assigned to him by a queue.
6. How are warehouse orders sorted for automatic assignment?

X A By latest starting date in ascending order and by execution priority in descending

order
X B By latest starting date in ascending order and by number of warehouse tasks
X C By storage type
Correct. For automatic assignment, the warehouse orders are sorted by latest starting
date in ascending order and by execution priority in descending order.
7. What is the travel distance calculation used for?

X A To sort the warehouse tasks in the optimum sequence
X B To determine the optimal resource for execution
X C To calculate the required travel time.
Correct. The travel distance calculation is used to calculate the required travel time.

Unit 1: Learning Assessment - Answers
8. SAP EWM uses the direct distance and distance based on networks to calculate the travel
distance.
X True
X False
Correct. SAP EWM uses the direct distance and distance based on networks to calculate
the travel distance.
9. When working with semi-system-guided queues, after scanning the system checks which
of the following?
X A The scanned HU is available in the specified storage bin.
X B The HU field is empty.
X C An open warehouse task exists for this HU.
X D The reported resource is allowed to process the HU.
Correct. The system checks if scanned HU is available in the specified storage bin and if
reported resource is allowed to process the HU.
10. What is the function of task interleaving?
The aim of task interleaving is to minimize unutilized resources through an optimized

distribution of the warehouse orders and to reduce the travel times in the warehouse.
11. What are the requirements for pick, pack, and pass?
X A A WO creation rule
X B Queue types
X C Define which bins represent the start point and end point for each picking zone
X D Each picking zone must be mapped as an individual activity area
Correct. You need a WO creation rule that supports the top WO creation for the pick, pack,
and pass process. Define which bins represent the start point and end point for each
picking zone. Each picking zone must be mapped as an individual activity area.

UNIT 2 Control of Physical Movements
in the Warehouse
Lesson 1
Setting Up Layout-Oriented Storage Control 59
Lesson 2
Integrating a Material Flow System 67
UNIT OBJECTIVES
● Set up layout-oriented storage control

● Enhance the Pick, Pack, and Pass Process
● Set up a basic material flow system scenario

Unit 2: Control of Physical Movements in the Warehouse

Unit 2
Lesson 1
Setting Up Layout-Oriented Storage Control
LESSON OVERVIEW
In this lesson, you will learn about the set up and usage of layout-oriented storage control.
This lesson guides you through the complete process for layout-oriented storage control.
LESSON OBJECTIVES
Layout-oriented Storage Control

You can use the layout-oriented storage control if stock movements in your warehouse do not
travel from a source storage bin to a destination location directly, but instead travel through
an intermediate storage bin.
Layout-oriented storage control can occur due to the physical layout of your warehouse or
when you have certain resources that only move in specific parts of your warehouse. In the
case of automated storage and retrieval systems, you need identification points and pick
points to connect these systems to the rest of your warehouse. In SAP EWM, you use the
layout-oriented storage control to describe these intermediate storage bins.

Figure 33: Complex Warehouses - Layout-oriented Storage Control
Layout-oriented storage control can only be used with handling units.
Layout-oriented Storage Control Setup

Optionally, you first define the storage groups. The storage group for layout-oriented storage
control is a logical or physical breakdown of a storage type. Within a storage type, you can
combine a series of storage bins for an area. The criteria for doing this should depend on the
physics of the storage bin. For example, all storage bins in an aisle are grouped in a storage
group, since the goods have to be brought during picking from this aisle to an intermediate
storage bin at the end of the aisle.
In the settings for the layout-oriented storage control, an intermediate storage type is
assigned for each required source or destination storage type or storage group. You can also
choose an intermediate storage section or enter an intermediate storage bin. You can use this
to specify in more detail where the product should be moved to. If you do not enter an
intermediate storage section or bin, SAP EWM uses the defined putaway strategies to find the
necessary data. Additionally, you can choose a handling unit type group, to specify that a
certain handling unit type, for example wire baskets, should always be moved using a specific
intermediate storage type.
You can also choose the warehouse process type that should be used to create the
warehouse task to the intermediate storage type. You use this to specify which activities
should be performed during warehouse task processing (for example, whether replenishment
should be triggered automatically, or whether the quantities should be rounded). If the
intermediate storage type is an identification point, the system does not use the warehouse
process type.
Access Strategy Storage Control

The following is the matrix for the access strategy for determining the interim storage types.

Lesson: Setting Up Layout-Oriented Storage Control
Ac- Source Stor- Source Stor- Destination Destination HU Type Whole HU

cess age Type age Group Storage Storage Group
Type Group
01 X X X X X X
02 X X X X X
03 X X X X X
04 X X X X
05 X X X X X
06 X X X X
07 X X X X
08 X X X
09 X X X X X
10 X X X X
11 X X X X
12 X X X
13 X X X X
14 X X X
15 X X X
16 X X
17 X X X X
18 X X X
19 X X X
20 X X
21 X X X
22 X X
23 X X
24 X
25 X X X X
26 X X X
27 X X X
28 X X
29 X X X
30 X X
31 X X
32 X

Ac- Source Stor- Source Stor- Destination Destination HU Type Whole HU

cess age Type age Group Storage Storage Group
Type Group
33 X X
34 X
35 X
Usage of Layout-oriented Storage Control
Figure 34: Layout-oriented Storage Control for HU Moves
In the figure, Layout-oriented Storage Control for HU Moves, a product pallet is to be moved
from storage area A to storage bin Z. But in the layout-oriented storage control table for the
movement from A to Z the intermediate point B is defined. That means that the WT from A to
Z is created in an inactive state, and that an additional WT from A to B is created.
Once the movement from A to B is confirmed, the system changes the source location for the
inactive WT, which is changed to B. The system checks if this movement is possible and if the
WT can be activated. But as the LOSC table defines that this movement requires the
intermediate point C, the WT from B to Z continues to be inactive and a new, active WT is
created for the movement from B to C.

Figure 35: Warehouse Tasks in Layout-oriented Storage Control
This process continues until the system finds no intermediate point for the inactive
warehouse task. Then the WT is activated, a warehouse order creation rule is determined, and
it can be processed.
Note:
“Intermediate points” in the text above can be separate storage types or just
storage bins in the same storage type.
As LOSC requires the use of HUs, this can give a confusing picture in a picking process. When
picking a full HU, LOSC is visible from the beginning. But in case of a partial pick, the WT from
the source bin has no HU and therefore LOSC is not triggered. There is no inactive WT and not
WT to the intermediate storage type.
LOSC is only triggered when confirming the WT with a pick-HU. The destination bin for the
pick WT is dynamically changed, and the next WT is created with the confirmation to the
intermediate bin. This means that LOSC in such a scenario is only possible when working with
mobile devices. A confirmation with the desktop app or in the Warehouse Management
Monitor would not use LOSC.
Identification Points and Pick Points

While a movement via an Identification Point or Pick Point is also controlled through layout-
oriented storage control, the details of the movements are different then with other storage
types.
Identification Point
When a destination storage type has the setting Putaway Using Identification Point Active, all
goods movements first go to the identification point. The storage type for the identification
point has the storage type role A - Identification Point or C - Identification and Pick Point and is
assigned as an intermediate storage type in the layout-oriented storage control.

Figure 36: Identification Point
When a warehouse task is created for the destination storage type, the system creates a WT
for the movement to the identification point - but the movement stops here. No inactive WT
for the final destination storage type is created, also after the confirmation of the WT to the
identification point no new WT is automatically created.
Note:
It must be said that this corresponds to the standard ERP WM function, where an
identification point is usually used in connection with an external warehouse
control unit. After a weight/volume/contour check at the identification point a
new WT for the destination storage type is created.
When using the material flow system in SAP EWM, similar identification point
scenario would be set up differently. The identification point is represented by a
communication point with an indicator which identifies it as identification point.
But you would not use a storage type with this storage type role A or C.
Pick Point
A pick point is used to force the system to move a complete HU (and its content) to this point,
independently of the quantity is required for picking (which corresponds to the complete
stock removal required indicator in ERP WM).
The complete HU is moved to the storage type with the storage type role B - Pick Point or C -
Identification and Pick Point. The required quantity is picked from the HU and the HU with the
partial quantity is moved back to the source storage type (or another storage type, if no
partial quantities are stored in the source storage type).

Figure 37: Pick Point
The source storage type has the setting Withdrawal Via Pick Point Active and the pick point is
assigned as intermediate storage bin in the layout-oriented storage control. The LOSC gives
you the options to control if all pick movements should go via the pick point, or if the picking
of the full handling unit quantity does not require a movement via the pick point (or maybe via
another pick point).
For the pick point you also define a work center. Here, you can repack and trigger the putaway
of the partial quantity.
If another WT requires stock which can be picked from the same source HU, the system
creates more than one inactive WT, which refers to the same HU. In the source storage type
you can additionally activate the setting Consider Stock on Resource. Then the system can
also use stock in an HU which is already on the way to the pick point.
Layout-oriented vs. Process-oriented Storage Control

While layout-oriented storage control (LOSC) and process-oriented storage control (POSC)
are both defined as “storage control”, there are some basic, but important differences
between these two types.
● While POSC has a limited number of process steps, there is no limit to the number of
warehouse tasks in LOSC.
● Each WT in POSC has its own process step. In LOSC the WT from the origin to the
destination bin and all its WTs in between have the same steps.
● With the exception of the pick point, you cannot use LOSC to move via work centers.
● In LOSC a confirmation of one WT always triggers the creation of the next WT (or the
activation of the inactive WT). In POSC this is only possible for certain process steps. For
steps which end at a work center, you have to “complete the process step for the HU” to
trigger the next WT.
POSC and LOSC can be combined. The system always first determines the process, so the
relevant POSC is active. For each process step with a physical movement, LOSC can
additionally be determined, if the direct movement is not possible according the LOSC
settings.

The Pick, Pack, and Pass Process combined with Process-Oriented and Layout-
Oriented Storage Control
In one of the previous lessons the pick, pack, and pass process was introduced. In the settings
for the process we added a separate start and end bin for each lower level activity area, so a
resource moves from the start to the end bin for the picking process. But at the last relevant
activity area the resource had to bring the pick-HU to the goods issue staging area.
Figure 38: Complex Pick, Pack, and Pass Process
In a more practical scenario, the next place to go would be a packing work center. This would
be possible by the determination of a warehouse process. But additionally you would not want
the resource from the activity area to make this movement to the work center, the resource
assigned to the activity area should ideally always stop at the end bin. In order to control that,
the layout-oriented storage control is used.
LESSON SUMMARY

Unit 2
Lesson 2
Integrating a Material Flow System
LESSON OVERVIEW
In this lesson, you learn about the functions and structure of a material flow system. You are
also shown how to set up and integrate a material flow system.
LESSON OBJECTIVES
Material Flow System

The material flow system (MFS) enables you to connect an automatic warehouse to SAP
EWM without the need for an additional warehouse control unit. SAP EWM communicates
directly with the control level.
You can set up the MFS in such a way that WTs (from an identification point to a storage bin in
an automatic high-rack storage area, for example) are subdivided into smaller tasks. These
are passed on, step-by-step, to the programmable logic controller (PLC) responsible in each
case using telegram communication. The putaway and removal from storage of HUs can then
proceed without the use of another software system.
You can define capacity limits for communication points, conveyor segments, or resources.
The SAP EWM system then holds back tasks for the PLC as soon as these limits are exceeded.
The same applies if the PLC reports that one of the individual elements of conveyance
(vehicles, legs, or communication points) are subject to malfunction.
Figure 39: Scenario for a Material Flow System

Besides dispensing with an additional software system, this offers a close connection
between the material flow and warehouse management. Therefore, warehouse management
system strategies can be adjusted to the condition and utilization of automatic storage
retrieval more efficiently. Additionally, the system provides the material flow system with
functions and data, for example, for destination inquiries. In this way, system mapping
accurately represents physical movements in the warehouse.
MFS Functions in an Automatic Warehouse

If you use SAP EWM to manage an automatic warehouse, you can use the following functions:
● Configurable paths through storage control
● Automatic identification of HUs using scanners on the automatic storage retrieval facility
● Automatic diversion of HUs that cannot be stored (incorrect contours, excessive weight,
unidentified)
● Full automatic putaway of HUs in the storage bin using any number of interim steps; these
interim steps are represented by communication points
● Malfunctions reported by the controls taken into account
● Configurable capacity limits for communication points, conveyor segments, and vehicles
taken into account
● Reduction in empty traveling paths for stacker cranes through interleaving
● Goods-to-man picking principle
● Stocks are also available for deliveries during transportation within the system
● Stable telegram communication between EWM and the PLC using parallel, bidirectional
communication channels
● Monitoring and troubleshooting as part of the regular warehouse management monitor
Logical System Levels

In automatic warehouses, various types of technology are used including the following:
● Conveyor lines (belts, chain conveyors, roller conveyors) for containers, boxes, pallets,
and wire baskets
● Stacker cranes for accessing storage bins without a driver
● Transfer cars for moving storage units (handling units) horizontally to different leg stages
or buffer spaces
● Scanners, sensors for contour control, and scales
Programmable Logic Controller

These devices are usually controlled by means of a real-time system, called a programmable
logic controller (PLC) that monitors and switches the sensors and actuators (light barriers,
switches, motors, and so on). These real-time systems obtain their orders from the
superordinate warehouse control level, which derives them from the warehouse requests.

Lesson: Integrating a Material Flow System
Figure 40: Communication to a Programmable Logic Controller
In SAP ERP Warehouse Management, the connection to a PLC required separate, 3rd party
software. Information between this software and WM was sent using IDocs.
Note:
The technology for this kind of communication also exists in SAP EWM, so it is
possible for customers to continue with such a setup with little upgrade effort.
With SAP Extended Warehouse Management no additional software is required anymore.
Note:
In previous SAP EWM releases, an additional RFC Adaptor was required for the
TCP communication (for which SAP PCo (Plant Connectivity) could be used. Since
SAP EWM 9.4, you can use the ABAP Push Channel TCP socket communication
layer of SAP NetWeaver to communicate directly between SAP EWM and
programmable logic controllers (PLCs).
Differences Between Automated Warehouse and Manual or RF-operated Warehouse

The following differences exist between automated warehouses and warehouses operated
manually or by radio frequency:
● The resources are passive (as in the case of stacker cranes).
● Capacity bottlenecks must be watched and controlled much more closely.
● Technical malfunctions must be taken into consideration.
● Logistical malfunctions must not block the material flow (for example, occupied bin or an
unknown HU on the automatic storage retrieval system).

Structure of a Material Flow System

This sample warehouse consists of an automatic high-rack storage area with three aisles and
automated putaway and removal. A distribution trolley links the putaway and picking area
with the high-rack storage area.
Figure 41: MFS Components
From the MFS perspective, this warehouse is operated with four controls. Three are for the
stacker cranes and one is for the distribution trolley and the conveyor lines of the preliminary
(pre-storage) zone. The warehouse has a single depth, and the distribution trolley and stacker
cranes each have just one load-handling attachment.
MFS Components
In the MFS, the warehouse to be controlled is mapped with the following components:
● Programmable logic controller (PLC):
The PLC is the underlying real-time system controlling the physical transportation of HUs
on conveyor systems and their components. It evaluates signals from the connected
automatic storage retrieval or conveyor system, or other controls, and activates or
deactivates motors, appliances, sensors, readers, and so on. Each control that
communicates with the SAP EWM system must be defined as a PLC. In larger installations,
head controls may be in use, which regulate local controls. The SAP EWM system
communicates with the head controls, so in that scenario you only define the head
controls.
At least one communication channel must be defined for each PLC.
● Communication channel:
The communication channel is the connection for transmission of messages between MFS
and a control facility, defined by an IP address and a port. You can define certain
properties, such as the length of the messages and whether telegram confirmations are to
be used. Using the application menu, you also create the settings for the IP address and
the port through which the PLC can be reached. You can use several channels to

Lesson: Integrating a Material Flow System
communicate with the same PLC. Each of these must use a separate port. You can specify
that certain telegrams are to be sent on a particular port and other messages on a
different port. Messages from a communication channel are communicated sequentially.
One communication channel per control is sufficient.
Further MFS Components

Communication Points:
SAP EWM maps the system to be controlled by means of communication points.
Communication points are stations in the automatic storage retrieval system from which
SAP EWM communicates with the PLC. Here, the PLC registers HUs (on the basis of
scanner information or material flow tracking) and awaits new destination specifications.
More communication points lead to closer material flow tracking in SAP EWM, but also to
more intensive communication and consequently more load on the SAP EWM system.
For each stage between communication points, a warehouse task is created. Every
communication point is also a storage bin, but only the storage bins on the automated
storage retrieval system are also communication points, whereas the storage bins in the
actual warehouse are not.
Conveyor segments:
Conveyor segments physically transport handling units (HUs) from one communication
point to the next. You can define a capacity limit for conveyor segments. As in the case of
communication points, the capacity relates to the number of HUs that can
simultaneously be transported using the relevant conveyor segment. If the capacity of a
conveyor segment is full, SAP EWM restricts further orders. You assign conveyor
segments to your start and end points in layout-oriented storage control. You can
combine conveyor segments to form a conveyor segment group, which in turn is
assigned a conveyor segment group type. This can be used, for example, to set several
conveyor segments inactive at the same time, by setting this for the conveyor segment
group type in case of a malfunction. The system then holds back orders for these
conveyor segments. You only need to define conveyor segments if you want to check
their status (readiness, capacity) in SAP EWM. In many cases, it is enough to record
capacity and status at communication points.
Resources:
In the MFS, a resource is a vehicle that transports an HU from one communication point
(or storage bin) to another. A resource moves to the pickup point in an empty state,
takes on the load, and then discharges the load at its destination. To reduce the number
of empty travel paths, you must optimize the sequence of the orders.
SAP EWM contains an interleaving strategy for stacker cranes with:

● Just one load handling attachment (which means that only one HU can be loaded)
● Putaway and removal bin at the same end of the aisle
● To optimize the movements of stacker cranes from within SAP EWM, the stacker cranes
must be mapped in SAP EWM as resources. Conveyor lines are not mapped as resources.
To transport HUs, SAP EWM generates WTs and WOs and arranges them in queues. In the
MFS, each warehouse order is assigned one WT only. To execute warehouse tasks, the
SAP EWM system generates telegrams and sends these to the appropriate PLC.
MFS for Case Conveyor Systems

For systems such as those described above, the routing of the MFS movements is done using
the layout oriented storage control and creates warehouse tasks for every single movement.
With MFS for case conveyor systems, SAP EWM offers routing decisions based on the current

location of a handling unit (HU) and context information related to the HU (such as general
information regarding putaway or picking destination data).
Handling unit (HU) movements in MFS for case conveyor systems are not immediately
modeled as warehouse tasks. Instead, the initial routing decision is made based on HU
information, location information, and warehouse tasks or warehouse orders that might exist
for final putaway or picking. As a result, a telegram is created and sent to the PLC. This
telegram has no direct connection to a warehouse task. Nevertheless, the HU movement,
which is based on the routing decision, can be modeled as a warehouse task in the system.
You can do this in the following ways:
● The PLC executes the movement after it receives the routing decision from the EWM
system. After this, it sends a new telegram with the actual routing information for the HU
to EWM. EWM creates a warehouse task for this movement. This warehouse task is
immediately confirmed.
● If the PLC is not able to send the actual routing information for the HU to EWM, it can
trigger an asynchronous posting to the location of the routing decision.
Case conveyor systems use a different routing logic to other conveyor systems, which use
layout-oriented storage control. With this routing logic you can enter different destinations for
the following:
● Activity areas
● HUs without an MFS error
● HUs with an MFS error
● Empty HUs without a warehouse order (WO) or warehouse task (WT)
● HUs containing content without a WO or WT
● HUs that do not fit any of the previous criteria
You can specify a default direction. The system uses the default direction if no appropriate
entry has been customized. For example, two entries have been customized, one for HUs
without an error and one default. If a HU has an error or no WT exists, the system chooses
the default entry.
Figure 42: MFS Case Conveyor Systems
LESSON SUMMARY

Unit 2
Learning Assessment
1. For layout-oriented storage control the use of storage groups is mandatory.

X True
X False
2. For layout-oriented storage control, you need:

X A A work center for packing
X B A material flow system (MFS)
X C Handling units
3. In the MFS, the warehouse can be mapped using which of the following components?
X A Conveyor segment
X B Conveyor line
X C Communication channel
X D Communication point

Unit 2
Learning Assessment - Answers
1. For layout-oriented storage control the use of storage groups is mandatory.

X True
X False
Correct. Storage groups are optional for layout-oriented storage control.
2. For layout-oriented storage control, you need:

X A A work center for packing
X B A material flow system (MFS)
X C Handling units
Correct. For layout-oriented storage control, you need handling units.
3. In the MFS, the warehouse can be mapped using which of the following components?
X A Conveyor segment
X B Conveyor line
X C Communication channel
X D Communication point
Correct. In the MFS, the warehouse can be mapped using conveyor segment,
communication channel, and communication point.

EWM15

Uploaded by

Copyright:

Available Formats

EWM15

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EWM15

Uploaded by

Copyright:

Available Formats

EWM115

Resource Management in SAP

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

American English is the standard used in this handbook.

This information is displayed in the instructor’s presentation

Related or Additional Information

User interface control Example text

Window title Example text

© Copyright. All rights reserved. iii

vii Course Overview

1 Unit 1: Optimization of Resources and Processes

3 Lesson: Using Mobile Devices

57 Unit 2: Control of Physical Movements in the Warehouse

59 Lesson: Setting Up Layout-Oriented Storage Control

© Copyright. All rights reserved. v

© Copyright. All rights reserved. vii

● Use mobile devices

© Copyright. All rights reserved. 1

2 © Copyright. All rights reserved.

By providing an RF framework, error-free data communication can be attained in the

© Copyright. All rights reserved. 3

Figure 1: Using Mobile Devices

Support for GUI, Character-based, and Browser-based Devices

Figure 2: Character-based or Browser-based Devices

4 © Copyright. All rights reserved.

Character-based devices are linked to the system through SAPConsole. SAPConsole

Screen Layout Personalization

© Copyright. All rights reserved. 5

2. Direct navigation to transaction:

6 © Copyright. All rights reserved.

Function Function Key Shortcut Description

© Copyright. All rights reserved. 7

Figure 4: Standard RF Function Keys

8 © Copyright. All rights reserved.

- Number of buttons available for the screen

SAP delivers three display profiles:

© Copyright. All rights reserved. 9

10 © Copyright. All rights reserved.

Figure 5: Pick By Voice

Adapting Verification Fields

© Copyright. All rights reserved. 11

Figure 6: RF Verification Profile

Verification Profile Determination

Asynchronous WT Confirmation and Pick-HU WT Creation

12 © Copyright. All rights reserved.

Figure 7: Synchronous vs. Asynchronous Warehouse Task Confirmation

© Copyright. All rights reserved. 13

Other Settings to Improve Performance

Combining Warehouse Tasks

Figure 8: Combine Warehouse Tasks

14 © Copyright. All rights reserved.

● Warehouse task attributes:

A warehouse worker is asked to confirm the combined picking of 23 pieces of product A.

© Copyright. All rights reserved. 15

● Optimize mobile device processing

16 © Copyright. All rights reserved.

© Copyright. All rights reserved. 17

Figure 9: Resources in EWM

Assignment of Warehouse Orders to a Resource