6/4/2022

Extended Warehouse Management (EWM)

Generated on: 2022-06-04 09:06:49 GMT+0000

SAP S/4HANA | 2021 Latest

PUBLIC

Original content: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/9832125c23154a179bfa1784cdc9577a?locale=en-

US&state=PRODUCTION&version=2021.002

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 6/4/2022

Resource Management

Use
Resource management maximizes the efficiency of warehouse processes by:

Facilitating the management and distribution of work via queues

Enabling the execution of work by resources in a radio frequency (RF) and non-RF environment

Optimizing the selection of warehouse orders for resources requesting work

Enabling effective monitoring and controlling of resources

Features
Controlled Distribution of Work via Queues

The assignment of resources to queues enables focused management and distribution of work in the warehouse.

For more information, see Queue.

Warehouse Order Execution in RF and Non-RF Environments

Resources can execute work via RF and non-RF transactions.

For more information about RF transactions, see Standard RF Functions.

Manual and Automatic Assignment of Warehouse Orders to Resources

Warehouse orders (WOs) can either be manually assigned to a resource by a warehouse manager, or automatically assigned by
the system.

For more information, see Assignment of Warehouse Order to Resource.

Optimized Warehouse Order Selection

Resources that require system-guided work are offered the most appropriate WOs. Here a number of factors are taken into
consideration, for example, the mode, latest start date (LSD), execution priorities, assigned queues, quali cation of resource
type, and WO status.

For more information, see Warehouse Order Selection.

Resource Controlling and Monitoring

Warehouse managers can use the warehouse management monitor to do the following:

Analyze resource workload

Monitor WO execution by resources

Send messages to resources

Logon and logoff resources

Assign resource groups to queues and remove this assignment

This is custom documentation. For more information, please visit the SAP Help Portal 2
 6/4/2022
Create and maintain users and resources

Change the queue of a WO

Change the LSD of a WO

For more information, see Monitor Methods.

See also:

Resource Management Using Radio Frequency.

Resource

De nition
A resource is an entity representing a user or equipment, which can execute work in the warehouse.

Use
A resource 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 can be tracked and displayed in the
warehouse management monitor .

 Note
For more information about logging on to an RF environment, see Logon .

For more information about how resources receive work, see Assignment of Warehouse Order to Resource .

This is custom documentation. For more information, please visit the SAP Help Portal 3
 6/4/2022

Structure
A resource belongs to a resource type and resource group .

 Note
You de ne a resource in the transaction for resource maintenance. To do so on the launchpad, choose Extended Warehouse
Management Master Data Resource Management /SCWM/RSRC - Maintain Resource . Alternatively you can de ne a
resource by using the warehouse management monitor ( method Maint. Resource ).

Resource Type

De nition
A resource type is a grouping of resources with similar technical or physical quali cations.

Use
The resource type determines the following for its corresponding resources :

Horizontal velocity

The velocity of a resource can in uence the LSD of a warehouse order (WO).

For more information, see Latest Starting Date (LSD) .

Applicability of position management

For more information, see Position Management .

Quali cations and preferences (re ected by priority values) regarding bin access typesand HU type groups

The quali cations and priority values in uence which WOs are selected for a resource requesting work.

For more information, see Warehouse Order Selection .

 Note
You de ne resource types, and assign to them quali cations, in Customizing for Extended Warehouse
Management Cross-Process Settings Resource Management De ne Resource Types.

You maintain the quali cation priority values using the execution priority maintenance transaction, accessed on the
launchpad ( Extended Warehouse Management Master Data Resource Management /SCWM/EXECPR - Maintain
Execution Priorities ).

Resource Group

De nition
A resource group is a grouping of resources for queue assignment purposes.

Use
The resource group determines the sequence of allowed queues for its corresponding resources, which can in uence which WOs
are selected for a resource. For more information, see Warehouse Order Selection.

This is custom documentation. For more information, please visit the SAP Help Portal 4
 6/4/2022
You assign/unassign a resource group to/from a queue using the De ne Queue Sequence - Resource Group app, accessed on
the launchpad (Extended Warehouse Management Master Data Resource Management ), or from the warehouse
management monitor (Assign Queue/Unassign Queue methods).

Assignment of Warehouse Order to Resource

Purpose
Warehouse orders (WOs) can be assigned to resources in radio frequency (RF) and non-RF environments.

In an RF environment, WOs can be assigned manually or automatically, while in a non-RF environment, WOs are only manually
assigned.

Prerequisites
In the case of automatic WO assignment to a resource, the WOs must belong to a queue to which the resource is assigned, and
which the resource is authorized to work in.

Process

Warehouse Order Assignment to a Resource

Non-RF Environment RF Environment

1. A resource logs on to the desktop A resource logs on to the RF environment.

environment.

2. The warehouse manager assigns the WO to One of the following occurs:

the resource via the Assign Rsrce monitor
The warehouse manager assigns a
method.
WO to the resource via the Assign
Rsrce warehouse management
monitor method.

 Note
Any available WOs can be
manually assigned to a resource,
including those from queues to
which the resource is not
assigned.

The resource requests work by

choosing a system-guided option
from the RF menu.

In such a case, the system assigns to the

resource the most appropriate WO. For
more information, see Warehouse Order
Selection.

The resource requests work by

choosing a manual option from the
RF menu (for example, Pick by HU).

In such a case, the system assigns

to the resource the speci c WO.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 5
 6/4/2022

Non-RF Environment RF Environment

You can also ensure that a new

3. The warehouse manager prints out the WO
WO is automatically assigned to
and gives it to the resource.
a resource after con rmation of
a WO. You de ne this in
Customizing for Extended
Warehouse Management under
Mobile Data Entry Radio
Frequency (RF)
Framework De ne Logical
Transaction Flow .

Warehouse Order Selection

When a resource chooses a system-guided radio frequency (RF) transaction, the system nds the most appropriate warehouse
order for the resource.

Process
1. A resource requests work using a system-guided RF transaction.

2. The system checks for available warehouse orders that are manually assigned to the resource by the warehouse
manager. For more information about manual assignment, see Assignment of Warehouse Order to Resource.

If the resource chose a System-Guided by Queue option, the warehouse orders must also belong to the selected queue.

If a warehouse order belongs to a queue, the queue's operating environment must be consistent with that of the
resource.

If more than one warehouse order is assigned to the resource, the list of possible warehouse orders for selection is
sorted in the following order:

Warehouse orders belonging to the resource's assigned queue

Warehouse orders belonging to the resource group's assigned queues, according to the de ned queue sequence

Warehouse orders that don't belong to any queue

If more than one warehouse order falls within any of these queue classi cations, the warehouse orders are sorted as
follows:

In ascending order, by latest starting date

In descending order, by execution priority

For more information, see Warehouse Order Prioritization.

3. If there are no manually assigned warehouse orders, the system checks for available warehouse orders.

The warehouse orders must comply with the following conditions:

The warehouse orders belong to one of the resource's or resource group's assigned queues.

The warehouse orders belong to queues in which the resource is authorized to work.

The warehouse orders belong to queues with the same operating environment as the resource.

If the resource chose a System-Guided by Queue option, the warehouse orders must also belong to the selected
queue.

This is custom documentation. For more information, please visit the SAP Help Portal 6
 6/4/2022
4. The warehouse orders can be executed by the requesting resource type (according to its bin access type and handling
unit type group quali cations).

The warehouse orders are sorted as follows:

In ascending order, by latest starting date

In descending order, by execution priority

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 con rmed warehouse
tasks. You skip a warehouse order using exception code SKWO and the resource can then continue with the next warehouse
order according to the criteria mentioned above.

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 (warehouse order creation rule of category
Pick, Pack, and Pass: System-Driven or Pick, Pack, and Pass: User-Driven) or when using pick-by-voice features.

You can track skipped warehouse orders based on existing exception code handling. You track skipped warehouse orders by
selecting the With Hist. (Control Indicator for History) checkbox for exception code SKWO in Customizing for Extended
Warehouse Management under Cross-Process Settings Exception Handling De ne Exception Codes . You can then view the
usage history of the exception code in the warehouse management monitor under Alert Exception .

Related Information
Resource
Queue
Resource Group
Latest Starting Date (LSD)

Mode

De nition
A mode is a state that determines the following:

Weighting factors used for warehouse order prioritization

Time intervals and units of measure for rounding latest starting dates (LSDs)

Use
When a warehouse task (WT) is grouped into a warehouse order (WO), its mode is set as:

The mode assigned to the corresponding wave , if applicable.

 Note
You can assign a mode to a wave in one of the following ways:

This is custom documentation. For more information, please visit the SAP Help Portal 7
 6/4/2022
By de ning the mode in the wave template (to do so, on the launchpad, choose Extended Warehouse
Management Work Scheduling Wave Management /SCWM/WAVETMP - Maintain Wave Templates )

By de ning the mode in a wave directly (to do so, on the launchpad, choose Extended Warehouse
Management Work Scheduling Wave Management /SCWM/WAVE - Maintain Wave )

The mode assigned to the following determination criteria:

Warehouse

Activities associated with the WTs

 Note
You de ne modes and their determination criteria in Customizing for Extended Warehouse
Management Cross-Process Settings Resource Management De ne Modes.

The mode is then used to calculate the LSDs and priorities of the WTs.

When determining the LSD of the warehouse order containing the WTs, the system uses the rounding time interval of the mode
of the rst WT in the WT sequence.

Latest Starting Date (LSD)

De nition
The latest starting date (LSD) is the latest time by which execution of a warehouse order should commence, so that it is
completed by the due date.

The LSD for each warehouse task of a warehouse order is calculated as follows:

LSD = warehouse order due date - (planned execution duration + planned movements duration)

The due date is taken from one of the following:

The picking completion date in the warehouse task

If there is no picking completion date in the warehouse task, the planned goods issue date in the warehouse
request

The planned execution duration is taken from the warehouse order

The planned movements duration is equal to distance/velocity. The following rules apply here:

Distance is calculated according to the bins' coordinates, using the manhattan metric

Velocity is the lowest horizontal velocity from all resource types that are quali ed to execute the warehouse task

Use
The system calculates the LSD of a warehouse order by:

1. Calculating the LSD of each warehouse task as described above

2. Taking the worst-case scenario LSD (that is, the earliest LSD)

3. Rounding down this LSD according to the rounding time interval of the relevant mode (that is, the mode of the rst
warehouse task in the warehouse task sequence)

This is custom documentation. For more information, please visit the SAP Help Portal 8
 6/4/2022
The LSD is one of the factors that in uence warehouse order selection. For more information, see Warehouse Order Selection.

Warehouse Order Prioritization

Use
Warehouse order (WO) prioritization ensures that the system selects for a resource the WO that is most suitable for it.

Prerequisites
You have assigned bin access typesand handling unit type groupsto resource types in Customizing for Extended Warehouse
Management Cross-Process Settings Resource ManagementDe ne Resource Types.

Activities
1. You maintain the following using the execution priority maintenance transaction (on the launchpad, choose Extended
Warehouse Management Master Data Resource Management /SCWM/EXECPR - Maintain Execution Priorities ):

Bin access type (BAT) and handling unit type group (HUTG) priorities per resource type (a value from 1-10 )

The priority values re ect the preferences of a resource type to work in a particular bin access type, or with a HU
type group.

Warehouse process category (WPC) priority (a value from 1-10 )

Priority weightings per mode (a value from 1-100 ).

The weighting of a priority parameter re ects 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 re ected by the mode.

 Note
If you do not maintain a BAT or HUTG priority value for a particular resource type, the resource type is not quali ed to work in
the bin access type or with the HU type group.

1. When a WT is combined into a WO, it is assigned a total priority, calculated as follows:

Priority = (BAT Weighting/100 x BAT Priority Value) + (HUTG Weighting/100 x HUTG Priority Value) + (WPC
Weighting/100 x WPC Priority Value)

 Note
The weightings are based on the mode of the rst WT in the WT sequence.

2. The total priority of the WO is set from the highest priority of its constituent WTs.

Example

 Note
In the following example, we assume that the warehouse process category for all WTs is the same, and therefore ignore the
warehouse process category priorities.

You maintain the following execution priorities for resource type A:

This is custom documentation. For more information, please visit the SAP Help Portal 9
 6/4/2022

Bin Access Type Priorities

Bin Access Type Priority

BAT1 6

BAT2 8

BAT3 4

Handling Unit Type Group Priorities

HU Type Group Priority

HUTG1 5

HUTG2 3

HUTG3 9

You also maintain the following mode priority weightings:

Mode Priority Weightings

Mode Priority Parameter Weighting

1 Bin Access Type 45

1 HU Type Group 30

1 Process Type 15

2 Bin Access Type 30

2 HU Type Group 50

2 Process Type 10

Resource A is currently assigned to queue 5, to which the following WOs are assigned:

WO 4432

Warehouse Task Mode Bin Access Type HU Type Group

LB 342 1 BAT3 HUTG3

LB 355 2 BAT2 HUTG1

WO 4435

Warehouse Task Mode Bin Access Type HU Type Group

LB 364 2 BAT1 HUTG2

LB 340 1 BAT2 HUTG3

The priority values for resource A are calculated as follows:

WO 4432

Priority (WT 342)

= (0,45*4) + (0,3*9)

This is custom documentation. For more information, please visit the SAP Help Portal 10
 6/4/2022
= 1,8+ 2,7

=4,5

Priority (WT 355)

= (0,3*8) + (0,5*5)

= 2,4 + 2,5

= 4,9

Total priority of WO 4432 = 4.9

WO 4435

Priority (WT 364)

= (0,3*6) + (0,5*3)

= 1,8 + 1,5

= 3,3

Priority (WT 340)

= (0,45*8) + (0,3*9)

= 3,6 + 2,7

= 6,3

Total priority of WO 4435 = 6.3

Queue

De nition
A queue is a logical le to which warehouse tasks (WTs) for processing are assigned. Queues de ne movements by which work in
the warehouse is managed and assigned.

Use
The management and distribution of work in the warehouse is accomplished by the assignment of resources and WOs to
queues.

A resource may execute only those WOs that belong to one of its allowed queues (unless the WOs are manually assigned). This
means a queue to which the resource or resource group is assigned, and in which the resource is authorized to work. 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 determine the operating environment of a queue during queue de nition (Customizing for Extended Warehouse
Management Cross-Process Settings Resource Management De ne Queues ).
This is custom documentation. For more information, please visit the SAP Help Portal 11
 6/4/2022
The operating environment of a resource is determined when the resource logs on to the RF or non-RF environment.

Resource Assignment to Queue

You can assign a resource to a speci c queue, or assign its resource group to a sequence of allowed queues. WO selection will be
performed rst according to the resource's assigned queue, and, in the absence of an assigned queue, according to the
resource group's queue sequence. For more information, see Warehouse Order Selection .

 Note
You assign a resource to a queue using the Maintain Resources app, accessed on the launchpad (Extended Warehouse
Management Master Data Resource Management ), or from the warehouse management monitor (Maint. Resource
method).

You assign/unassign a resource group to/from a queue using the De ne Queue Sequence - Resource Group app, accessed
on the launchpad (Extended Warehouse Management Master Data Resource Management ), or from the warehouse
management monitor (Assign Queue/Unassign Queue methods).

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

The search is performed in accordance with the access sequence, with the initial search being for an entry with all of these
parameter values. If no queue is found, the queue determination table is read again, according to the next entry in the
sequence.

 Note
You de ne queue determination criteria and access sequences in Customizing for Extended Warehouse Management Cross-
Process Settings Resource Management De ne Queues .

Radio Frequency Framework

Extended Warehouse Management (EWM) includes the implementation of a radio frequency (RF) framework.

The RF framework satisfying the following objectives:

Decouples business logic from the physical presentation of application data on a selected presentation device

Supports a large variety of device sizes, device types, and data entry types

Provides appropriate forms of data presentation according to application data, device capabilities, and user preferences

Calls appropriate services according to resource inputs (such as veri cation/input data, keystroke, or logon request)

Enables personalized menus and screens

Enables exible and user-friendly screen and ow logic generation and modi cation

This is custom documentation. For more information, please visit the SAP Help Portal 12
 6/4/2022
By providing an RF framework, greater efficiency and fast error-free data communication can be attained in the warehouse,
through the use of mobile RF devices.

Prerequisites
You've made the relevant settings in Customizing for Extended Warehouse Management under Mobile Data Entry . For
example, you can do the following:

De ne modules for logical transactions and to create logical transactions for the RF framework

Change the default navigation after ending logical RF transactions

De ne RF menus

Change the appearance of RF presentation screens

Assign function keys to standard functions

Note that you can change the settings in the Customizing activity De ne Steps in Logical Transactions using the following
Business Add-Ins (BAdIs):

BAdI: Change of Inter-Transaction Flow

BAdI: Change of Step Screen

BAdI: Change of RF Step Flow

BAdI: Change of Function Code Pro les

BAdI: Change of Validation Pro les

For more information about these BAdIs, see Customizing for Extended Warehouse Management under Business Add-Ins for
Extended Warehouse Management Mobile Data Entry Radio Frequency (RF) Framework .

Features

Support for GUI and Character-Based Devices and Browser-Based Devices

The RF framework supports both GUI and character-based devices, as well as browser-based devices.

GUI devices are connected to the SAP system just like any other client-dependent PC. The screens can be touch screens, using
prede ned pushbuttons, or they can be operated using a keyboard. If you're using touch screens, you simply touch the
appropriate positions on the touch screen instead of clicking with the mouse on a pushbutton.

Character-based devices are linked to the system through SAPConsole. SAPConsole operates on a 32-bit Windows server and
interacts with the RF terminals connected to it. This concept is currently supported by the leading providers of RF terminals.

The system uses ITSMobile or SAP GUI for HTML for connecting browser-based devices. For more information about SAP GUI
for HTML, see SAP Note 3048632 .

Bar Code Support

In EWM, you can use the GS1-128 standard to decode bar codes according to an international numbering standard, de ned by
GS1. This means that within the supply chain, GSI-128 can be used to transmit data from instance to instance.

The RF framework supports the use of bar codes for identi cation and veri cation purposes. You can scan bar codes with a
length of up to 255 characters. SAP currently supports GS1-128 bar code types, but you can also support other types within the

This is custom documentation. For more information, please visit the SAP Help Portal 13
 6/4/2022
RF framework. You can enhance the standard bar code logic or de ne your own bar code decoding logic in Customizing for
Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Mobile Data
Entry Bar Code Speci cation .

Screen Layout Personalization

Using the RF screen manager, you can customize the appearance of RF presentation screens, so as to ensure that they're
consistent with the attributes of the presentation devices being used.

For more information about the RF screen manager, see Customizing for Extended Warehouse Management under Mobile Data
Entry Radio Frequency (RF) Framework RF Screen Manager .

 Note
SAP provides screens based on a screen size of 8x40 on devices in landscape mode and 15x26 on devices in portrait mode.

Menu Personalization

Using the RF menu manager, you can de ne your own menus and menu hierarchy for the RF device transactions.

For more information about the RF menu manager, see Customizing for Extended Warehouse Management under Mobile Data
Entry Radio Frequency (RF) Framework RF Menu Manager .

 Note
SAP provides a standard menu and menu hierarchy.

Standard RF Features

The SAP RF framework provides standard RF features, including the following:

Logon

Logoff

Recovery

Work execution transactions for the following warehouse processes:

Picking

Putaway

Loading

Unloading

Deconsolidation

Packing

Physical Inventory

Replenishment

Receiving

Maintaining Handling Units

Performing Floor Checks

This is custom documentation. For more information, please visit the SAP Help Portal 14
 6/4/2022
Labor Management

RF Navigation
You can navigate from radio frequency (RF) menus to transactions, as well as navigate within transactions.

Process
Menu Navigation

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 eld.

3. Virtual Navigation

Unlike the rst options where navigation is accomplished from the displayed menus, this option enables "virtual"
navigation between menus. You enter the numbers of all required menu items, including the menu items not displayed
on the current screen, but rather displayed on subsequent screens.

 Note
If you enter 415 in the Menu eld on the main menu screen, you navigate to the Pick by HU transaction.

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 eld is open. You enter the data by scanning bar codes. If you enter data manually, you
choose Enter after entering the value.

Where the content provider lls elds with content, the input elds may either be closed, or hidden (depending on Customizing
for Extended Warehouse Management Mobile Data Entry Radio Frequency (RF) Framework De ne Logical Transaction Step
Pro les De ne Validation Pro le ). Where the input elds are closed, you verify the values by scanning the bar codes.

After all input elds on the screen are lled, one of the following occurs:

If the Skip Shortcut indicator is set, the posting (for example, warehouse task con rmation) is automatically triggered.

If the Skip Shortcut indicator isn't set, you automatically navigate to the Shortcut eld.

 Note
You can set the Skip Shortcut indicator when maintaining screens using the RF screen manager in Customizing for
Extended Warehouse Management under Mobile Data Entry Radio Frequency (RF) Framework RF Screen Manager .

You can invoke functions by choosing the corresponding function key button or entering the function key in the Shortcut eld.

Where necessary, you enter exception codes in the Shortcut eld (for example, for differences).

This is custom documentation. For more information, please visit the SAP Help Portal 15
 6/4/2022

 Note
You de ne exception codes in Customizing for Extended Warehouse Management under Cross-Process Settings Exception
Handling De ne Exception Codes .

RF Function Keys
You can use standard function keys and transaction-speci c function keys on your radio frequency (RF) devices.

Standard Functions Keys

You access standard function keys using a function key or shortcut, they aren't displayed in the function key line of an RF screen.
The following function keys are available:

Function Function Key Shortcut Description

More F5 05 Display the next pushbuttons in

the sequence (if there are more
than four buttons for a screen)

Clear F6 06 Clear a selected input eld or

all input elds

Back F7 07 Return to previous screen or

step

List F8 08 Display the list screen (showing

the possible input values) for a
selected eld

Full message F9 09 Display the full message on a

separate screen

 Note
Function key F9 or shortcut 09 also displays the text of deliveries or hazardous substances on a separate screen. Normally,
it's indicated on the screen that text is available. If there's a message and text available, you see the message rst and use
the function key F9 on the message screen to see the text.

If you're using an RF device that doesn't have function keys, you need to add buttons to the screen to be able to use the
standard functions. You can de ne the button groups for the standard functions on the SAP Easy Access screen for Extended
Warehouse Management under Master Data Maintain Presentation Devices . For example, you can add and sort the buttons
according to their function keys or to the end of the button groups.

If you want to de ne function codes and add them as buttons, you can use Business Add-In Addition of Standard Function Codes
as Buttons (/SCWM/EX_RF_ADD_FC_AS_PB) in Customizing for Extended Warehouse Management under Business Add-Ins
(BAdIs) for Extended Warehouse Management Mobile Data Entry Flow Processing of RF Framework .

Transaction-Speci c Function Keys

Transaction-speci c function keys are displayed in the function key line of an RF screen. If more than four function keys or
buttons exist for a screen, > is displayed, and you can then choose F5 to display the other buttons.

The following list includes only those function keys that appear as buttons on the screen:

This is custom documentation. For more information, please visit the SAP Help Portal 16
 6/4/2022

Function Pushbutton Text Description

Adjust HU Adjust Adjust any issues with a handling unit (HU)

found in an RF oor check

Bin empty EmBn Report that the storage bin being counted is
empty

Change HU measures HUMes Call screen to enter HU measures or

retrieve measures from a device

Change length, width, and height of HU ChgM Change the length, width, and height of the
HU

Change volume of HU ChgV Change the volume of the HU

Change weight of HU ChgW Change the weight of the HU

Close HU Close End work on the putaway HU

Clear all ClrAll Clear the contents of all input elds on the
screen

Clear sum ClSum Reset the quantity to zero during counting

or select the checkbox for zero stock

Complete HU container CpHUC Complete loading of the HU container

Complete receiving or unpacking End Complete the receiving or unpacking

process

Condense HU Cond Condense the nested deconsolidation HU

into a single-level HU

Convert HU Conv Convert the deconsolidation HU to a

putaway HU

Create HU HUCr Create a pick-HU

Delete HU Delete Delete the HU

If a pick-HU is already assigned to the

warehouse order, the system displays the
number of the existing HU

Delete HU DelHU Delete the HU from the list

Details Detail Display the details of the warehouse order

Display content information ConIn Display the content information

Display detail information Det. Display the detail information

Display HU list HULi Display the HU list

Display HU container list HUCLi Display the HU container list

Does not exist NotEx Report that the HU doesn't exist at this
location

Empty bin EmBn Report that the storage bin is empty

Enter device number Dev Enter the device number

Find HU HUCr Enter information about the found HU

This is custom documentation. For more information, please visit the SAP Help Portal 17
 6/4/2022

Function Pushbutton Text Description

HU completed HUCmp Report that the HU content count is

complete (HU content isn't counted, but
rather taken as the system quantity)

HU details HUDet Display the HU details

HU empty HUEmp Report that the HU is empty

HU items list ItList Display the items (product and lower-level

HUs) of the HU

HU list List List all the HUs

HU overview HUOv Display the HU overview

HU screen HU Navigate to the HU screen

HU withdrawal HUWd Report that you picked the whole pallet

Loading complete Comp Complete loading for the transportation unit

Nested HUs N.HUs Pick from the lower-level HUs of the nested
HU

New item NewItm Create a new product

Pick HU introduction PHUIn Navigate to the pick-HU introduction screen

(screen 0200)

Product detail PrdDet Display product details

Print Prnt Print information based on BAdI: Print WO

and HU Papers from RF Transactions
(/SCWM/EX_RF_PRT_WO_HU), BAdI
method PRINT

Product Prod Navigate to a screen where you can scan a

product number to display the relevant
warehouse tasks

Product detail ProDe Show detailed product data

Propose bin Prop Propose a new storage bin for the product
or HU warehouse task

Read data from device GetD Get weight, volume, and dimensions from
the device

Recover resource RcvRe Select a resource to continue working on (if

there's a work interruption when you were
logged on to more than one resource)

Remaining quantity RQty Report the remaining quantity during a zero

stock check

Reverse Revers Reverse the order of entries in the list

Reverse goods receipt UnGR Reverse the goods receipt

Reverse loading Undo Reverse the loading

Reverse sequence RvSeq Reverse the sequence of warehouse tasks

in a warehouse order

This is custom documentation. For more information, please visit the SAP Help Portal 18
 6/4/2022

Function Pushbutton Text Description

Select WT WT Navigate to a screen where you can scan a

warehouse task number to display the
warehouse task

Set freight booking time frame ChFBR Set the time frame used to read open
freight bookings

Set To Be Clari ed status TbCl Set the status of the HU to redirect HU to

the clari cation zone

Show handled HU list FinHU Display the HUs that are already processed

Show loaded HU list LoaHU Display the HUs that are already loaded

Show open HU list OpnHU Display the HUs that aren't processed yet

Show planned HU list PlnHU Display the HUs that are planned but not
loaded yet

Skip Skip Skip the entry and start at the next one in
the list

Skip to end Skip Place the current entry to the end of the list

Stock overview StOv Display the available stock of a product

Unassign Unasn Unassign a warehouse order from the

resource

Undo complete HU container UnCp Reverse the completion of the HU container

Unload HU container UnLo Reverse the loading of the HU container

WT list WTLst Display the list of warehouse tasks in the

warehouse order

Yes or no Yes/No Answer a query message

Zero stock ZeroSt Report that the product count for the
storage bin is zero, and so select the
checkbox for zero stock

Standard RF Functionalities
Use

The radio-frequency (RF) framework supports standard RF functionalities, including the following:

Logon and logoff – implemented as steps within a master transaction

Recovery – implemented as a state of the logon step

Radio Frequency Transaction Log

Request work/inquiry – implemented as a step of the master transaction, which initiates another transaction

Logon

Use

This is custom documentation. For more information, please visit the SAP Help Portal 19
 6/4/2022
Logon to the radio-frequency (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.

Prerequisites
You have logged on to the system.

Features
Automatic and Manual Logon

The RF framework supports automatic logon triggered by a presentation device, or triggered by a user.

Triggered by Presentation Device (Background Processing)

If a presentation device can identify itself (for example, by IP address), the application uses this identi cation to
determine the default resource. User-related parameters are based on the prede ned default data of the user.

Triggered by User

If a default resource and warehouse are de ned for a user, and a default presentation device is de ned for the default
resource, then automatic logon occurs when the user chooses to logon to the RF environment. Depending on
Customizing, the user may either be logged on automatically, or presented with the logon screen, with all default
parameters displayed.

For manual logon, a user must identify the resource to which he or she logs on, as well as the warehouse and presentation
device.

Multiple Logons

The RF framework supports the logging on of a user to multiple resources.

Activities
You de ne a user, using the user maintenance transaction (Extended Warehouse Management Master Data Resource
Management /SCWM/USER - Maintain User on the launchpad).

Automatic Logon, Triggered by Device Automatic Logon, Triggered by User Manual Logon

This is custom documentation. For more information, please visit the SAP Help Portal 20
 6/4/2022

Automatic Logon, Triggered by Device Automatic Logon, Triggered by User Manual Logon

When de ning the user, you must assign a When de ning the user, you must de ne a On the launchpad, you chooseExtended
default resource and default warehouse. default resource and default warehouse. Warehouse
Management Execution /SCWM/RFUI -
The default resource must have assigned to Log On to RF Environment. .
it a default presentation device.
The logon screen appears.
The device is de ned in Extended
Warehouse Management Master
Data /SCWM/PRDVC - Maintain
Presentation Devices on the
launchpad.

The device is assigned using the

resource maintenance transaction
(Extended Warehouse
Management Master
Data Resource
Management Maintain Resources
on the launchpad).

You de ne a presentation device, using the When de ning the user, you must de ne a You enter the warehouse number, resource,
presentation device maintenance default resource and default warehouse. and presentation device with which to log
transaction (Extended Warehouse on. One or more of these elds may be
Management Master The default resource must have assigned to lled with default parameters, depending
Data /SCWM/PRDVC - Maintain it a default presentation device. on your user and resource de nitions.
Presentation Devices on thelaunchpad).
The device is de ned in Extended
Warehouse Management Master
When de ning the presentation device, you
Data /SCWM/PRDVC - Maintain
must have assigned to it the default If you do not ll the DefPresDvc eld on the
Presentation Devices on the
resource. Logon screen, it is lled with one of the
launchpad.
following:
The presentation device is one that is able
The device is assigned using the
to identify itself. The default presentation device
resource maintenance transaction
de ned for the resource in the
(Extended Warehouse
resource maintenance transaction
Management Master
Data Resource The presentation device set as the
Management Maintain Resources default in the presentation device
on the launchpad). maintenance transaction, if no
default presentation device is
de ned for the resource

This is custom documentation. For more information, please visit the SAP Help Portal 21
 6/4/2022

Automatic Logon, Triggered by Device Automatic Logon, Triggered by User Manual Logon

When you turn on the presentation device, it On the launchpad, you choose Extended You choose Enter to log on.
calls SAPConsole, which initiates the RF Warehouse Management Execution Test
presentation transaction, and logs on RF Environment.
automatically.
If you set the Auto Logon indicator
when de ning the user, you are
logged on automatically.

If you did not set the Auto Logon

indicator, the Logon screen
appears, with the elds being lled
with the default parameters. You
may either keep the default, or
change any of them. You then
choose Enter to log on.

 Note
If you set the Auto Logon
indicator, multiple logons are not
possible.

During logon, the Dynpro layer identi es the display pro le assigned to the speci c presentation device.

The business logical layer does the following:

Addresses the logon to resource management, to perform the logon process

Fetches the resource personalization pro le of the resource, and authorization information

Determines the logical transaction associated with the physical transaction

Sets the initial step and function code

The logon transaction ends only when you log off.

Logoff
A resource can log off from the radio frequency (RF) environment.

Integration
Logoff is a step of the logon logical transaction (see Logon).

Activities
1. You choose F1 Logoff.

2. You enter a reason code for logging off and choose F1 Save.

You can maintain RF-speci c reason codes by de ning a resource group for goods movement code RF Logoff. You
maintain reason codes in Customizing for Extended Warehouse Management under Cross-Process Settings Warehouse
Task Manage Reasons for Goods Movement .

The logoff request of the resource is sent to resource management using the business logic layer package (see Resource
Management).

This is custom documentation. For more information, please visit the SAP Help Portal 22
 6/4/2022
The resource is logged off from the RF environment.

Recovery

Use
During logon, the system checks with the content provider whether the user is logged on as a resource, and if so, whether he or
she was interrupted during warehouse order (WO) execution.

Integration
The recovery functionality is part of the logon transaction.

Activities
1. A user attempts to log on to the system.

2. The system checks with the content provider whether the user was previously logged on to the radio-frequency (RF)
environment.

a. If the user was logged on to a resource, see step 3.

b. If the user was logged on to more than one resource, the logon screen is displayed with the RcvR pushbutton,
enabling the user to select the resource with which to continue.

3. The system checks whether a speci c WO that was assigned to the resource was stopped before completion. It does so
by checking for WOs that ful ll all of the following conditions:

a. The WOs are assigned to the resource.

b. The WOs have already been started.

c. The WOs can be locked.

4. If the system nds any WOs that ful ll these conditions, it does the following:

a. Finds the relevant logical transaction

b. Finds the data of the WO

c. Displays the screen of the relevant step

5. If the system does not nd any WOs that ful ll these conditions, the system displays the Menu screen.

Position Management

Use
Position management enables a radio-frequency (RF) device user to validate handling units (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.

In Customizing for Extended Warehouse Management Cross-Process Settings Resource Management De ne Resource
Types , you have selected one of the following options for the Pos.Mgmt eld:

Manual

This is custom documentation. For more information, please visit the SAP Help Portal 23
 6/4/2022
Automatic

Activities
1. An RF user logged on as a resource navigates to the pick HU introduction screen (0200) and scans a pick HU.

2. If the resource type of the resource has automatic position management, the following occurs:

a. The scanned HU is assigned to the next available position.

b. The cursor moves to the next HU input eld.

3. If the resource type of the resource has manual position management, the following occurs:

a. The cursor moves to the position eld.

b. The resource manually enters the position number.

c. The HU is assigned to the position.

d. The cursor moves to the next HU input eld.

4. In the background, an internal warehouse task (WT) is created to update the HU location and logical position.

Radio Frequency Transaction Log

This is custom documentation. For more information, please visit the SAP Help Portal 24
 6/4/2022
You can log transactions used in the radio frequency (RF) framework to allow you to identify error messages that often occur,
wrong validations, or where your warehouse workers need to use exception codes.

To activate the RF log, on the SAP Easy Access screen, choose Extended Warehouse Management Settings Resource
Management Activate Radio Frequency Log . After you have activated the log, the system writes log entries at different points
in time during an RF transaction process.

You can see the RF log entries in the warehouse management monitor, under Resource Management RF Log .

The system writes the log entries at the following points in time:

A user logs on to a resource

A user logs off from a resource

An RF transaction is started

An RF transaction is ended

A user selects an RF menu item

The system raises a message or an error message

A user triggers a function, either by choosing a function key or a button

A user validates a eld

A user displays an RF screen

The system triggers a function module in the step ow

A user triggers an exception.

A user enters data into a screen eld

You can enhance or change what the system includes in the RF log using the Business Add-In BAdI: Write Radio Frequency Log
Entries (/SCWM/EX_RF_LOGGING).

Work Processing Using Radio Frequency

Use

Work processing provides you with all the functions required to carry out your putaway and stock removal activities.

For the goods receipt process:

Unloading Using Radio Frequency

Deconsolidation Using Radio Frequency

Putaway Using Radio Frequency

Receipt of Handling Units Using Radio Frequency

Receipt of Handling Units Using Radio Frequency

Receipt of Handling Units from Production Using Radio Frequency

Con rmation Correction Using Radio Frequency

For goods issue:

This is custom documentation. For more information, please visit the SAP Help Portal 25
 6/4/2022
Picking Using Radio Frequency

Packing Using Radio Frequency

Loading Using Radio Frequency

Consumption of Products for Production Using Radio Frequency

For internal warehouse processes:

Physical Inventory Using Radio Frequency

Ad Hoc Movements Using Radio Frequency

Yard Movement Using Radio Frequency

Querying Using Radio Frequency

Resource Management Using Radio Frequency

Handling Unit Differences Using Radio Frequency

For transit warehouse processes:

Receipt of Handling Units in Transit Warehouse

Unloading of HU Containers in Transit Warehouse

Loading of HU Containers in Transit Warehouse

Loading of Transportation Units in Transit Warehouse

Floor Check in Transit Warehouse

Handling-Unit Maintenance in Transit Warehouse

If you are working with products that are hazardous-substance-relevant in warehouse activities, the system shows this with the
HazS (hazardous substance) indicator on the respective RF display. If hazardous-substance-relevant texts exist, you can display
them using the F9 function key.

Loading and Unloading Using Radio Frequency

Use
You can also execute loading and unloading using a radio frequency presentation device (RF presentation device).

Prerequisites
You have logged on in the RF environment. For more information, see Logon.

You have de ned a warehouse order creation rule of the type Load/Unload and have speci ed the number of loading
employees who are to execute the higher-level warehouse order in Customizing for Extended Warehouse Management
under Cross-Process Settings Warehouse Order De ne Creation Rule for Warehouse Orders .

Features
You can use this function to have multiple loading employees load or unload a transportation unit, even if the entire
transportation unit corresponds to only one warehouse order. In this case, the system creates a higher-level warehouse order

This is custom documentation. For more information, please visit the SAP Help Portal 26
 6/4/2022
that contains all warehouse tasks (WTs) for the handling units (HUs) of the transportation unit.

For more information about transportation units, see Transportation Unit.

Activities
The following describes an example of unloading a truck with four HUs and two loading employees. Loading works in the same
way.

1. When the system nds a warehouse order creation rule of the type Load/Unload, it creates a higher-level warehouse
order with four WTs.

2. In accordance with the warehouse order creation rule, the system creates two warehouse orders for the two loading
employees who are to unload the HUs. These two warehouse orders are linked to the higher-level warehouse order, but
do not have any WTs.

3. The system transfers the two warehouse orders as executable to resource management. They are now ready to be
processed in the RF environment.

4. The system transfers the two warehouse orders to the two loading employees. They go to the relevant trucks (in
accordance with the warehouse order).

5. As soon as the two loading employees scan the rst HU, the system automatically moves the relevant WT from the
higher-level warehouse order to the warehouse order belonging to the relevant loading employee.

6. Both loading employees unload all the HUs and con rm the corresponding WTs. The higher-level warehouse order no
longer contains any WTs, since the system has distributed them to the lower-level warehouse orders. After the loading
employees have con rmed the last WT, all warehouse orders involved are completed (in other words, con rmed or
canceled). This would also be the case, even if only one loading employee had unloaded the truck.

 Note
If you activated the loading sequence validation, you can bypass or overrule the validation using an exception code. You
de ne the exception code in Customizing for Extended Warehouse Management under Cross-Process Settings Exception
Handling De ne Exception Codes . You must de ne the exception code for business context LPI-Loading of HUs (Stock
Removal) with the execution step L1-RF Loading HU Selection and the internal process code SKLO-Skip Loading Sequence.

Deconsolidation Using Radio Frequency

Use
You are able to execute deconsolidation using a Radio Frequency (RF) presentation device.

Prerequisites
You are logged on to the RF environment. For more information, see Logon.

Features
Logging on to a work center

For most of the transactions within the main menu for deconsolidation you need to log on to a certain work center to get
proposals for several input elds.

Creating multiple handling units (HUs)

This is custom documentation. For more information, please visit the SAP Help Portal 27
 6/4/2022
The creation of multiple empty putaway HUs can be used as preparation for deconsolidation.

Creating a single HU

The creation of a single empty putaway HU can be used as preparation for deconsolidation.

Deconsolidating HUs

Deconsolidation is the repacking/sorting of items from the deconsolidation HU into several putaway HUs. Repacking is
based on warehouse task con rmation. After the warehouse tasks have been con rmed, a new warehouse task is
created that is then used for putaway. Sorting occurs by the consolidation group which is copied from the activity area of
the nal putaway bin to the product warehouse task.

Deconsolidating HUs manually

Deconsolidation can also take place without you logging on to a work center. In this case, the system does not propose a
putaway HU. Instead, you have to enter the putaway HU manually. The system still checks if the destination HU is valid
for the selected warehouse task.

HU overview

The HU overview screen provides an overview of the deconsolidation HU that you want to deconsolidate, for example,
the number of open warehouse tasks, weight, and volume.

Creating a single HU manually

You can create a putaway HU without logging on to a work center. In this case, the system does not propose a packaging
material or a bin. The creation of a single empty putaway HU can be used as preparation for deconsolidation.

Changing HUs

In this RF transaction, you can close a putaway HU, delete an empty HU, convert a deconsolidation HU into a putaway
HU, and condense a deconsolidation HU. Whenever a putaway HU becomes full, you have to close the HU in order for it
to be ready for the next process step such as putaway. If you have created a HU in the system that you no longer need,
you can delete it. To deconsolidate nested HUs, you have to condense them rst.

Receipt of Handling Units Using RF

Use
You use this function to optimize the goods receipt process for handling units (HUs) in the inbound delivery. You pack inbound
deliveries and create HUs according to the speci ed bar code information. You can also post, unload, and put away goods
receipts.

For HUs that already exist in the system, the function supports homogeneous HUs, mixed HUs, and cross-delivery HUs. If you
create a HU, the system only supports homogeneous HUs.

For information about receiving HUs from production without existing inbound deliveries, see Receipt of Handling Units from
Production Using Radio Frequency.

For information about receiving HUs in transit warehousing, see Receipt of Handling Units in Transit Warehouse

Prerequisites
The bar code speci cation is maintained in Customizing for Extended Warehouse Management (EWM).

You do this in Customizing for Extended Warehouse Management by choosing Mobile Data Entry Maintain Bar Code
Speci cation .

This is custom documentation. For more information, please visit the SAP Help Portal 28
 6/4/2022
In the inbound delivery document type, you have speci ed a determination procedure for automatic packing, and have
set the indicator No Automatic Packing. If you have speci ed a determination procedure and set this indicator, the
system does not perform automatic packing when creating an inbound delivery.

To do this, in Customizing for Extended Warehouse Management choose Goods Receipt Process Inbound
Delivery De ne Document Type Determination for Inbound Delivery Process .

The inbound delivery is available in the EWM system.

Features
In the launchpad for Extended Warehouse Management, choose Execution Test RF Environment Inbound Processes Receiving
of Handling Units. . This function comprises of the following process steps:

You select a receipt type. The HUs you can scan depend on the type of entry you select. You can choose between:

Delivery

Shipment

Transportation Unit

Shipping Noti cation

Door

Depending on this selection, the system looks for the corresponding deliveries. You then scan a HU and thereby con rm
receipt. Alternatively, you create a new HU in the background, if the HU does not exist in the system.

Scanning HUs that already exist in the system

When scanning, the procedure differs depending on whether the HU already exists in the system.

If the HU already exists, for example, if a detailed advance shipping noti cation exists, and the HU is assigned to the
current delivery, you scan the Serial Shipping Container Code (SSCC).

You use the enter pushbutton to display the relevant data, such as product number, quantity, packaging material,
or goods movement bin.

You use function key F1 to change the quantity.

You use function key F2 to change the packaging material.

You use function key F3 to change the serial number.

Scanning HUs that do not exist in the system

If the HU does not yet exist in the system, for example because no detailed advanced shipping noti cation exists, you
must scan additional bar code information, such as the Global Trade Item Number (GTIN), batch, production date, or
packed quantity. When all the required data is available, the system is able to create a homogeneous HU with a delivery
reference. If the batch has not been created in the system, the system creates it in the background automatically. If the
products in the HU are serial-number managed, you can manually assign serial numbers. The system can validate
whether the serial numbers are already de ned in the inbound delivery or not.

If you scan a HU that is not noti ed, the system generates the HU automatically. Here, it determines the default
packaging material using the relevant determination procedure. In the determination procedure, you have de ned a
packaging speci cation that contains a default packaging material. If the system does not perform automatic packing, it
uses the determination procedure for determining the packaging material when receiving HUs.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 29
 6/4/2022
If you scan a product for which no inbound delivery item exists but a purchase order or manufacturing order exists,
the system automatically adds an inbound delivery item.

If you are using decentralized EWM based on SAP S/4HANA and you scan a product for which no inbound delivery
item exists but an expected goods receipt exists, the system automatically adds an inbound delivery item.

After scanning existing and newly created HUs, you can:

Unload using function key F1

Post goods receipt using function key F2

Create warehouse tasks using function key F3

Con rm warehouse tasks using function key F4

Exceptions when scanning HUs

If the HU is assigned to another delivery, the system issues an error message. If you then enter the exception
code HUAD, the system looks for the delivery and splits it correspondingly.

If you notice on closing the transaction that a noti ed HU is missing, enter the exception code HUMI. The system
adjusts the delivery correspondingly, meaning the quantity is corrected correspondingly.

For more information about exception codes, see Customizing for Extended Warehouse Management under
Cross-Process Settings Exception Handling De ne Exception Codes .

Mass operations for multiple HUs

When you're receiving HUs, for example, by delivery, you can use function key F3 MulHU to create multiple HUs that
contain the same product. For example, when you receive 40 pallets in a transportation unit, instead of creating one HU
at a time, you can create 40 HUs at the same time.

Additionally, you can also process other operations for multiple HUs at the same time, for example, unload multiple HUs
and perform goods receipts for multiple HUs.

However, you can also process the HUs one by one if you need to.

Note that you perform mass operations only on non-serial-number-managed products.

Receipt of Handling Units from Production Using Radio

Frequency

Use
You use this function to process the receiving of handling units (HUs) from production within your warehouse. You can also
reverse the receipt from production for the HUs, either completely or partially.

For more information about the processes, see Receipt from Production in Advanced Production Integration.

Prerequisites
You have set up a work center with the transaction type Packing – General, and assigned a bin to the work center for the
receiving of the HUs from production.

For more information, see Customizing for Extended Warehouse Management under the following paths:

Master Data Work Center Specify Work Center Layout

This is custom documentation. For more information, please visit the SAP Help Portal 30
 6/4/2022
Master Data Work Center De ne Work Center

On the launchpad for Extended Warehouse Management, choose Master Data Work Center Con gure Work Center .

You have set up packaging speci cations to allow the system to propose packaging materials during the receiving of the
HUs.

If you are working with packaging speci cations, you have de ned the condition type for the packaging speci cation
determination in Customizing for Extended Warehouse Management under Master Data De ne Warehouse Number
Control .

For more information about packaging speci cations, see Packaging Speci cation.

Note that you can maintain packaging speci cations for reference products and assign the reference products to the
product master data to limit the number of required packaging speci cations.

OR

You have assigned a default packaging material to the work center.

On the launchpad for Extended Warehouse Management, choose Master Data Work Center Con gure Work Center .

You are not working with serialized products, products that require valuation quantities, or documentary batches.

If you use GS1-128 barcode labels to identify HUs or products, you have maintained the bar code speci cation in
Customizing for Extended Warehouse Management under Mobile Data Entry Maintain Bar Code Speci cation .

If you use the Rec. HU by Order with Putaway transaction, you have done the following:

You have ensured that there are no Post Processing Framework (PPF) tasks running for goods receipt posting
and warehouse task creation when an inbound delivery is created or changed.

You have selected the Allow Automatic WT Creation via Scan in RF Putaway checkbox for the warehouse process
type in Customizing for Extended Warehouse Management under Cross-Process Settings Warehouse
Task De ne Warehouse Process Type .

If you want to reverse the receipt of products from production, you have a user with the authorization object
/SCWM/SLFU, including the special function RH.

If you want to reverse the receipt of products from production by HU, you have maintained at least one exception code
for the business context RVS Reverse Receipt, in Customizing for Extended Warehouse Management under Cross-
Process Settings Exception Handling De ne Exception Codes . The exception code must have an internal process code
and a process code to reduce inbound delivery quantities upon reversal of the HU.

If you are using decentralized EWM based on SAP S/4HANA, the expected goods receipt for the manufacturing order is
available in EWM.

For more information about expected goods receipts, see Using Expected Goods Receipts.

Features
To use the radio-frequency (RF) transactions, in the RF menu, choose Goods Receipt Processes Receiving of Handling
Units Rec. HU by Manufacturing Order . You log on to the work center for receiving the HUs from production. If you have set up
a default work center for the user or terminal, the system uses that work center.

Receiving HUs

The following transactions are available:

Rec. HU by HU

This is custom documentation. For more information, please visit the SAP Help Portal 31
 6/4/2022
You use this transaction to receive HUs with identical content for the same manufacturing order, one after another.
There is no need to scan barcode labels on the physical HUs.

Rec. HU by EAN

You use this transaction to receive multiple HUs for the same manufacturing order, but you have to scan the barcode
label on the physical HU. For example, the barcode can contain additional information such as product, batch number,
production date, or shelf life information.

Rec. HU by Order

You use this transaction to receive HUs for several manufacturing orders. You enter the manufacturing order for each
HU.

Rec. HU by Order with Putaway

You use this transaction to receive one HU after another and perform putaway for the HU immediately after the
receiving.

In each transaction, you enter the manufacturing order for the HU. The system displays the list of items referring to the
manufacturing order, that is, the product, the co-product, and the by-product. You have the following options:

You scan the barcode label

You press enter to receive the main product of the manufacturing order

You choose F1 ChSel to select the item-by-item selection from the table

After you have chosen the item, the system proposes the data to receive. You have the following options:

F1 ChDt: change the batch number and dates

F2 ChPm: change the packaging material and HU type

F3 ChQty: change the quantity and unit of measure

F4 HUCr: receive a HU with an internal HU number

Shift + F3 ChUoM: switch to another unit of measure

Shift + F4 nHUC: change the number of HUs to be created at one time

This function is only available if you are working with internal HU numbers and using function F4 HUCr.

Enter: If you have entered or scanned a HU, when you press enter, the system creates the HU with the data entered

SAP provides some business add-ins (BAdIs) to allow you to in uence the data proposed by the system, in Customizing for
Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Mobile Data
Entry Receipt from Production with Radio Frequency .

Reversing HUs

You can reverse the receipt of a HU from production. You can reverse the full HU or a partial quantity of the HU.

In the following situations, you cannot reverse the receipt from production:

The putaway of the HU to the nal bin is already complete.

The HU is currently not in a bin and is not a planned HU.

The HU has multiple stock items in it, or the stock is not directly in the HU.

This is custom documentation. For more information, please visit the SAP Help Portal 32
 6/4/2022
The stock in the HU refers to a document for quality inspection that is released and cannot be canceled.

After you have entered the HU, the system displays information about the stock in the HU. You have the following options:

F1 Rev: reverse the quantity displayed in the reversal quantity eld

F2 RemQ: switch to the remaining quantity eld, instead of the reversal quantity

F3 RevQ: switch to the reversal quantity eld, instead of remaining quantity

F4 FullQ: set the reversal quantity to the quantity of the complete HU

Shift + F3 ChUoM: switch to another unit of measure

Putaway Using Radio Frequency

Use
You can perform putaway of handling units (HUs) using a radio frequency (RF) presentation device.

Prerequisites
You have logged on in the RF environment.

The destination storage bins of the warehouse orders to be processed are always in the same activity area.

Features
Transactions for Putaway Usings RF

Putaway by Handling Unit

For more information, see Putaway by Handling Unit.

Putaway by Handling Unit (Clustered)

For more information, see Putaway by Handling Unit (Clustered).

Putaway by Warehouse Order

For more information, see Putaway by Warehouse Order.

Exceptions in Putaway Using RF

HU Warehouse Task Con rmation

You can specify an exception for the putaway process. Once you have speci ed the exception, you can change the
destination storage bin or skip the HU warehouse task that is currently to be processed.

 Example
The aisle is blocked, and you cannot get to the source storage bin or destination storage bin.

You enter the exception. During the putaway process, the system no longer shows you this HU warehouse task, and
you do not need to con rm the source data and destination data.

Product Warehouse Task Con rmation

This is custom documentation. For more information, please visit the SAP Help Portal 33
 6/4/2022
You can specify an exception for the putaway process. Once you have speci ed the exception, you can do the following:

Change the destination storage bin.

Record differences.

For example, if an item in the product quantity is damaged, you can enter a smaller product quantity rather than
con rm the entire quantity.

Change the batch.

Skip the product warehouse task that is currently to be processed.

 Example
The aisle is blocked, and you cannot get to the source storage bin or destination storage bin. You enter the
exception. During the putaway process, the system no longer shows you this product warehouse task, and you
do not need to con rm the source data and destination data.

Putaway by Handling Unit

You can put away handling units one at a time.

Prerequisites
If you want to create warehouse orders for HU putaway when the HU is scanned, you have con gured the warehouse process
type in Customizing for Extended Warehouse Management under Cross-Process Settings Warehouse Tasks De ne Warehouse
Process Type .

Context
You perform the putaway of a single handling unit (HU) by scanning the HU label, and con rming the destination data.

If no open putaway warehouse order exists for the HU, the system can create the warehouse order for the HU immediately.

Procedure
1. You scan the HU you want to put away.

2. The system nds the corresponding warehouse order.

If the system cannot nd a warehouse order for the HU, it creates a warehouse order and warehouse tasks for the HU.

3. Depending on whether the warehouse task is based on the HU or on the product, the system displays the following data:

If the warehouse task is based on the HU, the system displays the following data:

Source HU

Destination storage bin

Destination HU

If the warehouse task is based on the product, the system displays the following data:

Source HU

Product

Quantity

This is custom documentation. For more information, please visit the SAP Help Portal 34
 6/4/2022
Batch

Destination storage bin

Destination HU

If there are several product-based warehouse tasks for the HU, the system displays the rst product warehouse task
found according to the sort sequence of the destination storage bins in distributive putaway.

4. You con rm the data.

5. If there are several product warehouse tasks for the HU, the system proceeds with the next product warehouse task.

Putaway by Handling Unit (Clustered)

You can collect multiple handling units together and put them away as part of one warehouse order.

Prerequisites
If you want to create warehouse orders for HU putaway when the HU is scanned, you have con gured the warehouse process
type in Customizing for Extended Warehouse Management under Cross-Process Settings Warehouse Tasks De ne Warehouse
Process Type .

Context
You perform the putaway of several handling units (HUs) collectively by scanning the HU labels one after the other. You then
move the HUs to the destination bins, and con rm the destination data. If no open putaway warehouse order exists for a HU,
the system can create the warehouse order for the HU immediately.

Procedure
1. You scan the HU you want to put away.

2. The system nds the corresponding warehouse order.

If the system cannot nd a warehouse order for the HU, it creates a warehouse order and warehouse tasks for the HU.

3. You scan all the HUs you want to put away at the same time as the rst HU.

4. You perform the putaway either as guided by the system, or according to warehouse task, product, or HU.

5. Depending on whether the warehouse task is based on the HU or on the product, the system displays the following data:

If the warehouse task is based on the HU, the system displays the following data:

Source HU

Destination storage bin

Destination HU

If the warehouse task is based on the product , the system displays the following data:

Source HU

Product

Quantity

Batch

Destination storage bin

This is custom documentation. For more information, please visit the SAP Help Portal 35
 6/4/2022
Destination HU

If there are several product warehouse tasks for a HU, the system displays the rst product warehouse task found
according to the sort sequence of the destination storage bins in distributive putaway.

6. You con rm the data.

7. The system proceeds with the next warehouse task.

Putaway by Warehouse Order

Context
You perform the putaway of one handling unit (HU), or several HUs or products by scanning the warehouse order and
con rming the source and destination data.

In the RF environment, if a warehouse order contains more than one warehouse task, you can do the following:

Skip a warehouse task

Reverse the sequence in which the system displays the warehouse tasks

Place the displayed warehouse task at the end of the warehouse order

Procedure
1. You scan a putaway warehouse order or enter it manually.

2. The system nds the corresponding warehouse tasks.

3. Depending on whether the warehouse task is based on the HU or on the product, the system displays the following data:

If the warehouse task is based on the HU, the system displays the following data:

Source storage bin

Source HU

If the warehouse task is based on the product, the system displays the following data:

Product

Quantity

Batch

Source storage bin

4. You con rm the data.

5. Depending on whether the warehouse task is based on the HU or on the product, the system displays the following data:

If the warehouse task is based on the HU, the system displays the following data:

Source HU

Destination storage bin

Destination HU

If the warehouse task is based on the product, the system displays the following data:

Product

This is custom documentation. For more information, please visit the SAP Help Portal 36
 6/4/2022
Quantity

Batch

Destination storage bin

6. You con rm the data.

7. If the warehouse order contains more than one warehouse task, the system proceeds with the next warehouse task.

Consumption of Products for Production Using Radio

Frequency

Use
You can post consumption for products used by production using radio frequency (RF). When you post consumption, the system
posts a goods issue for the products.

You can post consumption for products that have been packed into a handling unit (HU), or for unpacked products.

You can reverse the consumption of products that have been posted as consumed by production.

To use the transactions, in the RF environment, choose Outbound Processes Consumption .

Features
Consumption by Manufacturing Order

You can post consumption based on the manufacturing order. You can post consumption for partial quantities, for the full
quantity of the manufacturing order, or for more than was requested in the manufacturing order. You can post
consumption for a full HU, or for speci c quantities of unpacked products.

Reversal of Consumption by Manufacturing Order (HU)

You can reverse the posting of consumption for products that have been posted for consumption but have not actually
been consumed. You can use this transaction to reverse the consumption of products that were packed into a HU.

Reversal of Consumption by Manufacturing Order (Bin)

You can reverse the posting of consumption for products that have been posted for consumption but have not actually
been consumed. You can use this transaction to reverse the consumption of products that were consumed directly from
a bin.

Con rmation Correction Using Radio Frequency

Use
You can also use a radio-frequency (RF) device to correct warehouse tasks in the goods receipt process that have already been
con rmed.

Prerequisites
You have logged on in the RF environment.

You have de ned a completion delay for inbound deliveries (see Con rmation Correction, under Prerequisites).

This is custom documentation. For more information, please visit the SAP Help Portal 37
 6/4/2022
You are using a document type and item type with a status pro le for which you have activated the status DWM (see
Con rmation Correction, under Prerequisites).

Features
You can specify the following selection criteria for putaway warehouse tasks (WTs):

Warehouse order (WO)

Putaway WT or a stock identi cation

Storage bin

In each case, the system shows you the assigned putaway WTs for the correction. You can correct the batch and the quantity.
The system then adjusts the posted stock correspondingly.

Activities
1. You specify the selection criterion, such as con rmation correction by WO, and the WO number.

2. The system displays the relevant putaway WTs.

3. You choose ^ (Page up) or v (Page down) to navigate to the putaway WT you want to correct.

4. You specify an exception code. This renders the elds Btch (batch) and AQty (quantity) ready for input.

5. You enter the changes and save them by choosing ENTER.

Picking

Use
You are able to execute picking using a radio-frequency (RF) presentation device.

Prerequisites
You are logged on to the RF environment.

Features
System-Guided Picking

The system presents the optimal warehouse order for execution, using the WO selection mechanism.

System-Guided Picking by Queue

You enter a queue (from one of your allowed queues), and the system presents for execution the optimal warehouse order from
the queue, using the warehouse order selection mechanism.

Picking by Warehouse-Request

You enter a warehouse-request number, and the system nds the corresponding warehouse order.

Picking by Warehouse Order

This is custom documentation. For more information, please visit the SAP Help Portal 38
 6/4/2022
You enter a warehouse order number, and the system presents the warehouse order for execution.

Picking by HU

You enter a handling-unit (HU) number, and the system nds the corresponding warehouse order.

RF Picking Flow

Use
This section shows the ow of the standard screens, in the context of the logical transactions and steps, when a user performs
radio frequency (RF) picking.

Process

This is custom documentation. For more information, please visit the SAP Help Portal 39
 6/4/2022

System-Guided Picking System-Guided Picking Picking by WR Picking by WO Picking by HU

by Queue

After logging on to an RF presentation device, you choose 04 Goods Issue 01RF Picking Main Menu .

You choose 01 System- You choose 02 System- You choose 03 Pick by You choose 04 Pick by You choose 05 Pick by
Guided Picking. Guided by Queue. WR. WO. HU.

You select a queue. You select a warehouse You select a warehouse You select a handling unit
request (WR). order (WO). (HU).

The system selects and locks a WO for selection, pursuant to the WO selection mechanism.

The pick HU introduction screen appears.

If HUs or packaging products are assigned to the WO, you can use the existing HUs. Otherwise, you can create your own by selecting
packaging product, printing labels, and scanning the HU numbers.

This is custom documentation. For more information, please visit the SAP Help Portal 40
 6/4/2022

System-Guided Picking System-Guided Picking Picking by WR Picking by WO Picking by HU

by Queue

After introducing one or more pick HUs, you navigate to the source screen of the rst transportation order (TO) of the WO. Depending on
the TO, one of the following screens is displayed:

Pick product screen – if the TO is for picking a quantity of product from a non-bulk storage type

Pick bulk product screen – if the TO is for picking a quantity of product from a bulk-storage type

Pick HU screen – if the TO is for picking HUs which are not known in the TO

In the case of the pick product screen, you validate the source bin, source HU, product, quantity, and destination HU (or position).

In the case of the pick HU screen, you validate the source bin, source HU, and destination HU.

The pick bulk product screen is the same, except you must scan a source HU number.

After all products are picked, and have been put into the resource’s pick HUs, the place HU screen appears.

In case of no pick HU, the place product screen appears.

In the case of the place product screen, you validate the destination bin, position, product, and quantity.

In the case of the place HU screen, you validate the destination bin and the destination HU. For multiple HUs, you can avoid redundant
validation of the destination bin and destination HU with a single destination scan. For more information, see Placement of Multiple HUs

Skip Pick-HU Screen During RF Picking for Replenishment

You can skip the screen for creating pick-handling units (pick-HUs) in the radio frequency (RF) environment (transaction
/SCWM/RFUI) or in voice-based picking (transaction /SCWM/RFUI_PBV).

If pick-HUs are already created during warehouse order creation or if the picking process does not need a pick-HU, for example,
for replenishment of full pallets, you can skip the screen for creating pick-HUs so that your users do not need to continue the
process by choosing the Next button.

Prerequisites
You have speci ed the settings for skipping the screen in Customizing for Extended Warehouse Management under Mobile Data
Entry Control Display of Pick-HU Screen During RF Picking .

Combined Picking Using Radio Frequency

You can use combined picking to collectively pick warehouse tasks with the same attributes.

Use
You can combine the warehouse tasks in the radio frequency (RF) picking transaction.

Prerequisites
You have speci ed settings for combined picking pro le in Customizing for Extended Warehouse Management under Mobile
Data Entry De ne Combined Picking Pro le .

Features

This is custom documentation. For more information, please visit the SAP Help Portal 41
 6/4/2022
Warehouse task combination

You can perform the single pick con rmation for the total quantity of the combined warehouse tasks. The warehouse
tasks can be combined if they have the following matching attributes:

Attributes Description

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 codes

You can use the standard exception codes in the RF picking transaction. The exception codes are applied to the
combined warehouse tasks. Examples of exception codes are as follows:

Pick denial (entire quantity): you can use exception codes such as BIDU or BIDF for full denial of the combined
quantity. The system applies the full denial to all the warehouse tasks that were combined.

Pick denial (partial quantity): 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

Warehouse task 2: To pick 8 pieces of product A

Warehouse task 3: To pick 5 pieces of product A

A warehouse worker is asked to con rm 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 speci ed in the system. The worker enters the BIDP exception code. The
system performs the following pick con rmation:

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.

Combination cancellation

You can choose the F3 UnCom button to cancel the combination of warehouse tasks that were combined previously by
the system.

Collective entry of serial numbers

This is custom documentation. For more information, please visit the SAP Help Portal 42
 6/4/2022
To pick serial-number managed products, you can collectively enter or scan all serial numbers for the combined
warehouse tasks.

Adjusted planned duration calculation in executed workload

In Labor Management, the system calculates the adjusted planned duration of executed workload based on the
warehouse tasks that are picked with combined picking.

Monitoring of combined warehouse tasks

In the warehouse management monitor, you can see whether a warehouse task is combined or not and in which
combination group it belongs to.

 Note
The system does not combine the warehouse tasks in the following cases:

Picking warehouse tasks with valuation quantity input. That is, products that are catch weight relevant and their
warehouse process types are customized with valuation quantity input for warehouse task con rmation.

Picking products of nested handling units.

Picking warehouse tasks with different destination handling units or destination bins.

Placement of Multiple HUs

Use
If multiple handling units (HUs) exist with the same destination bins in one warehouse order for RF picking, you can optimize the
placements of HUs. This enables you to avoid redundant validation of destination bin and HU combination with a single
destination scan.

Prerequisites
You have speci ed settings in the views /SCWM/V_MPHU_DTS and /SCWM/V_MPHU_DET in the transaction SM30.

Features
Single destination for all HUs

You need to validate the destination bin and number of HUs only once to con rm all the HU warehouse tasks.

Multiple destination bins for handling units

You can choose the destination bin in which you want to place HUs. For each destination bin you choose, you need to scan
the bin only once and con rm the number of HUs that should be placed in it, or you can validate the handling units
individually. For the last destination bin you choose, you need to validate the destination bin and the number of handling
units only once.

Error Handling

Use
If errors occur during warehouse task con rmation, the assumption is that most errors, which are not already shown as part of
veri cation, cannot be resolved by the picker. Therefore, the system sends the pick-handling unit (pick-HU) to a dedicated
clari cation bin so that the error can be analyzed and resolved. The picker can follow the guidance of the pick by voice system.

This is custom documentation. For more information, please visit the SAP Help Portal 43
 6/4/2022
You can specify a clari cation bin for each activity area and activity on the launchpad under Extended Warehouse
Management Master Data Storage Bin De ne Start and End Bin - Activity Area or by entering the transaction code
/SCWM/SEBA. If you do not specify a clari cation bin, the system displays error messages instead. Note that this situation does
not relate to errors the picker must be noti ed about, such as veri cation errors. Therefore if, for example, the picker scans the
wrong source bin, an error is still shown to the picker and he or she has to correct the error.

The following error scenarios are possible:

The con rmation of the pick warehouse task from the source bin to the destination bin fails.

This error scenario can happen if, for example, the Customizing settings for the storage type allow the available quantity
to be a negative value. Thus, a warehouse task can be created with a quantity which exceeds the quantity actually
available in the bin. However, if the available quantity on the bin has not increased, the warehouse task cannot be
con rmed during picking. The pick warehouse task stays open but is no longer assigned to a picker for processing, and
the pick-HU is sent to the clari cation bin. If a pick-HU warehouse task to the original destination already exists, it is
canceled and a new one to the clari cation bin is created.

The asynchronous creation of the pick-HU warehouse task fails.

This error scenario can happen if, for example, the destination bin of the pick-HU is blocked. In this case, the Remote
Function Call (RFC) queue contains an entry for the HU that cannot be processed. The system creates a warehouse task
with the clari cation bin as its destination, and deletes the entry from the queue. The system always creates warehouse
tasks to the clari cation bin synchronously, to ensure stable error handling.

 Note
If a clari cation bin is maintained and an error occurs, the picker is directed to the clari cation bin. This situation can
happen for different kinds of errors. The assumption is that these errors should be checked by a supervisor at the
clari cation bin. However, this situation could include errors the picker might resolve himself or herself. But still he or
she is directed to the clari cation bin. The errors can be, for example:

A batch-neutral warehouse task is con rmed by the picker with a batch that physically has enough stock.
However according to the system, there is not enough stock.

The picker picks the goods of too many warehouse tasks into the same pick-HU and exceeds the capacity of
the pick-HU.

The source storage bin or destination storage bin is locked by another user.

The clari cation bin should not be located in a storage type with the staging area role. If it is, the staging area of the
outbound delivery item referenced by the warehouse task is set to the clari cation bin. The staging area is set to the
clari cation bin because the delivery is updated with the current warehouse task data during warehouse task
con rmation.

If the warehouse task con rmation aborts with an error, the system moves the pick-HU to the clari cation bin for further
processing. The warehouse task is marked internally as faulty, and stays open but is not assigned to a picker for processing any
more.

Prerequisites
If you want to in uence error handling using clari cation bins during RF picking, you must implement the Restriction of
Clari cation Bin (/SCWM/EX_RF_PICK_CLF_BIN) Business Add-In in Customizing for Extended Warehouse Management
under Business Add-Ins (BAdIs) for Extended Warehouse Management Mobile Data Entry Picking with Radio Frequency (RF) .

Features
Warehouse Order Split

This is custom documentation. For more information, please visit the SAP Help Portal 44
 6/4/2022
If a picker leaves the picking transaction while some warehouse tasks of the processed warehouse order are still open, he or she
can send the remaining warehouse tasks back to the queue so a different picker can process them. The system then splits the
warehouse order so the open warehouse tasks are moved to a new warehouse order. This situation also happens if you delete
the assignment of a warehouse order to a resource in the warehouse management monitor.

Warehouse tasks that are still open due to an error remain in the original warehouse order, as they have already been
processed. This means that the erroneous warehouse tasks remain assigned to the picker that actually processed them.

Exception Codes

If an error occurs during warehouse task con rmation, an internal exception code is raised. The following internal exception
codes are available for pick by voice:

RF01 - Error during WT con rmation in RF

The system displays this exception code if the con rmation of a pick warehouse task from the source bin to the resource
fails.

RF02 - Error during WT creation in RF

The system displays this exception code if the con rmation of the pick-HU warehouse task from the resource to the
destination bin fails.

For all the internal exceptions, de ne exceptions for the execution step Data Veri cation in Background in Customizing for
Extended Warehouse Management under Cross-Process Settings Exception Handling De ne Exception Codes .

By assigning an exception code to the internal exception code, an exception can be triggered to inform the worker responsible
for checking the HUs on the clari cation bin. The exception code must be valid for the business context TPI – Con rm
Warehouse Task (Stock Removal) and TIM - Con rm Warehouse Task (Intern. Movemnt) with the execution step A0 – Data
Veri cation in Background, which is used for exceptions triggered by the system.

In the warehouse management monitor node you can display the exceptions under Alert Exception . From this node you can
also navigate to the faulty warehouse order using the monitor method Display WO of WT. Here you can con rm warehouse
tasks that were left open due to errors after the problem is solved. In order for your exception to be displayed in this monitor
node, you must activate the With History option for your exception code.

In addition, you can con gure your previously mentioned exceptions to raise an alert in the Alert Monitor by maintaining a
follow-on alert for the respective exception code, business context, and execution step. You can nd the Alert Monitor on the
SAP Easy Access screen under SCM Basis Alert Monitor Alert Monitor or by entering the transaction code /SAPAPO/AMON1.
For information about alert pro les and alert noti cations, see Alert Monitor.

Clearing Errors

When a pick-HU is rerouted to the clari cation bin, you must check the HU, con rm any pick warehouse tasks that are still open,
and forward the HU to its original destination.

When you are informed by an alert that a HU is being sent to the clari cation bin, you must rst use the Alert Exception monitor
node to identify the erroneous warehouse order. You can check here whether some of the pick warehouse tasks are still open. If
multiple pick-HUs were sent to the clari cation bin, you rst have to check which one the product of the warehouse task was
picked into. Since the remaining warehouse tasks could not be con rmed, they still point to the original destination and not to
the pick-HU. When you have matched the warehouse tasks that are still open with the correct HUs, con rm the warehouse
tasks in the foreground and change their destination to the appropriate pick-HU.

After solving the issue, we recommend that you mark the corresponding exception as solved using the Set Exception to Solved
method of the Alert Exception warehouse management monitor node. On a regular basis, solved exceptions can be
reorganized using the report Reorganization of Exception Code Records (/SCWM/R_REORG_EXCEPTION_SOLVED).

This is custom documentation. For more information, please visit the SAP Help Portal 45
 6/4/2022
After you nish processing a HU in the clari cation bin, you must create an ad hoc warehouse task to the HU's original
destination. You can create this ad hoc warehouse task using the Create Warehouse Tasks - Handling Units app (/SCWM/ADHU)
which you can nd on the launchpad under Extended Warehouse Management Work Scheduling Create Warehouse Task
Without Reference . If you work with process-oriented storage control, the system tries to determine the destination data
automatically. For more information, see Process-Oriented Storage Control.

More Information
Exceptions

Improving Performance

Improving Performance

Use
You can optimize system performance during radio frequency (RF) picking.

Features
Asynchronous Processing

 Recommendation
Use asynchronous processing only when necessary as quicker response times increase system load, which can have a
negative effect on the required system sizing.

Asynchronous Delivery Update

During pick warehouse task con rmation, the system also updates the corresponding outbound delivery order item. To improve
the response time of the warehouse task con rmation step, the system can perform the delivery update asynchronously in a
Remote Function Call (RFC) queue. You can monitor the queue for message queue group /SCWM/INT1 - Warehouse Internal
Messages in the warehouse management monitor under Tools Message Queue .

You can activate asynchronous delivery update on the launchpad under Extended Warehouse
Management Settings Performance Settings Asynchronous Delivery Update - Activate .

Asynchronous Pick Warehouse Task Con rmation

To improve the response time of the warehouse task con rmation step, you can activate asynchronous pick warehouse task
con rmation. With asynchronous pick warehouse task con rmation, the system presents the next RF screen before updating
the database. You can activate asynchronous pick warehouse task con rmation on the launchpad under Extended Warehouse
Management Settings Performance Settings Activate Asynchronous Update - Radio Frequency .

The asynchronous pick warehouse task con rmation can fail if, for example, the Customizing settings for the storage type allow
the available quantity to be a negative value. For more information, see Error Handling.

Asynchronous Creation of Pick-Handing Unit Warehouse Tasks

The system creates the pick-handling unit (pick-HU) warehouse task from the resource to the destination bin when con rming
the rst pick warehouse task into the HU. To improve the response time of the warehouse task con rmation step, the system
creates the pick-HU warehouse tasks asynchronously in an RFC queue. You can monitor the queue for message queue group
/SCWM/INT1 - Warehouse Internal Messages in the warehouse management monitor under Tools Message Queue .

This is custom documentation. For more information, please visit the SAP Help Portal 46
 6/4/2022
You can activate the asynchronous creation of pick-HU warehouse tasks on the launchpad under Extended Warehouse
Management Settings Performance Settings Activate Asynchronous Update - Radio Frequency .

The asynchronous creation of pick-HU warehouse tasks can fail if, for example, the destination bin for the pick-HU is blocked. For
more information, see Error Handling.

Switching Off Printing

Warehouse task printing and HU printing are called during warehouse task creation and warehouse task con rmation. 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.

The queue has a eld (QUEUE_PRINT) for setting up printing during warehouse task creation and con rmation. The eld has
the following possible values:

' ' – call PPF

1 – do not call PPF

You can change the value of this eld in Customizing for Extended Warehouse Management under Cross-Process
Settings Resource Management De ne Queues .

The resource has a similar eld (RSRC_PRINT) with the following values:

1 – call PPF

2 – do not call PPF

' ' – the queue value decides whether or not to call the PPF

You can change the value of this eld on the launchpad under Extended Warehouse Management Master Data Resource
Management Maintain Resources .

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 launchpad under Extended
Warehouse Management Master Data Resource Management Deactivate Messages - Resources .

Picking at a Pick Point Using Radio Frequency

Use
You are able to pick at a pick point using a radio frequency (RF) presentation device. This function is part of the goods issue
process.

In this type of picking, the handling unit (HU) arrives at the warehouse worker (goods-to-man). In standard RF picking, it is the
other way round: the warehouse worker gets the HU (man-to-goods).

At the pick point, you withdraw products from a handling unit (HU), and pack these into pick handling units. The pick point is
de ned as a work center in Extended Warehouse Management (EWM).

This is custom documentation. For more information, please visit the SAP Help Portal 47
 6/4/2022

Prerequisites
You have made the following settings in Customizing for EWM:

In the storage type that contains the stock, you have set the Pick Point indicator to Active in stock removal control.

In Customizing for EWM, choose Master Data De ne Storage Type .

In the storage type that contains the pick point, you have set the Storage Type Role eld as B (Pick Point) or C (ID and
Pick Point).

In Customizing for EWM, choose Master Data De ne Storage Type .

In the layout-oriented storage control, you have entered the storage type of the pick point for the inventory-managed
storage type in the Intermediate Storage Type eld. You have also made an entry in the warehouse process type. You
can also de ne the intermediate storage section and intermediate location. You have set the Pick Point indicator

In Customizing for EWM, choose Cross-Process Settings Warehouse Task De ne Layout-Oriented Storage Control .

In the work center layout, you have de ned the transaction type Packing - General.

In Customizing for EWM, choose Master Data Work Center De ne Work Center Layout .

If you are using process-oriented storage control, you have entered the following in the work center:

External step

Storage type of the pick point

Work center layout

Warehouse process type for putback from the pick point

Return storage type (inventory-managed storage type)

If you are using consolidation groups, you have set the value in the Check Cons. Group eld to Check When Unpacking
HUs and Products.

If you want to enter external HU numbers as well, you have selected the eld RF: HU Ready for Input. In Customizing for
EWM, choose Master Data Work Center De ne Work Center .

 Note
If the indicator is not selected, you cannot specify a HU number. The system determines the HU number from the
internal number range.

Features
Logging On to the Work Center

Before using the pick point function, you have to log on to the work center. You then select the function from the RF
menu, or the system calls it, if the user selects another function for the rst time, such as Process HU.

Creating a Pick-HU

You choose this function directly from the menu, or by choosing function key F12 in the pick point function, to create an
empty pick-HU:

1. If a packaging material or storage bin is de ned for the work center, it is displayed.

2. To create a pick-HU, you must enter at least the packaging material and the storage bin.

This is custom documentation. For more information, please visit the SAP Help Portal 48
 6/4/2022
3. If you specify a HU number, the system creates a pick-HU with the same number.

4. If you do not specify a HU number, the system uses a number from the internal number range. If you also enter a
consolidation group, this is stored with the HU, and you can then use the HU for this consolidation group only.

Additional Processing Options:

Delete empty HU

Maintain attributes of the HU, such as consolidation group, total weight, total volume, maximum weight,
maximum volume, weight tolerance, volume tolerance, length, width, height, and logical position

Create a warehouse task manually for transporting an HU

Trigger the print function manually

Complete a pick-HU in process-oriented storage control

Trigger automatic creation of a warehouse task for return transport of the source HU

Pick Point

1. The user enters the number of the HU that was transported from the warehouse to the pick point, and that
contains the product that is to be picked.

2. The user withdraws the required quantity, and packs it into a pick-HU. If a suitable pick-HU already exists, the
system proposes it to the user. If multiple suitable pick-HUs exist, the user can select another.

If no suitable pick-HU exists, the user can call function Creation of an HU directly, and create one. This is then
copied automatically into the pick point dialog.

3. The user can display how many open stock movements for the current wave and consolidation group are still to
come to his pick point, and how great the weight and volume of these stock movements is. The system also
displays the maximum length, width, and height of the products in these stock movements. This information is
important for selecting the correct packaging material.

Block Storage Bins for Open Warehouse Tasks Using RF

Use
You use this function to consider blocked storage bins during putaway and picking after creating a warehouse task (WT). When
you block a storage bin, you use an exception code to de ne what is to happen to the relevant WT when processing using radio
frequency (RF).

When creating WTs, the system checks whether a storage bin is blocked. When blocking storage bins, the system does not check
whether open WTs exist for it. If a storage bin is blocked after you have created the WT, this does not have any effect on the
open WT. The system also does not check the lock indicators when con rming this WT.

This enables you to block storage bins that cannot be used for whatever reason (due to damage, for example) for further
putaway or picking.

For more information about blocking storage bins for open WTs in the EWM system, see Block Storage Bins for Open Warehouse
Tasks.

Prerequisites
In Customizing, you have de ned the exception codes that apply when you block storage bins with open WTs.

This is custom documentation. For more information, please visit the SAP Help Portal 49
 6/4/2022
To do this, in Customizing for Extended Warehouse Management (EWM) choose Cross-Process Settings Warehouse
Task De ne Control for Blocking Storage Bins .

Features
In the RF environment, in addition to the options described in the EWM system, you can issue messages.

You create a WT with a particular warehouse process type, which in turn is dependent on the warehouse process type. When
selecting a warehouse order for a WT with a blocked storage bin, in the RF environment, the system checks whether:

1. The source or destination storage bin is blocked

2. An exception is de ned for the current case in the Customizing activity (see table below)

3. A message is to be issued, stating that the source or destination bin is blocked. To output messages, in the Customizing
activity select the elds Mess. Src RF (Message Control for Blocked Source Storage Bin in RF) and/or Mess Dest RF
(Message Control for Blocked Destination Storage Bin in RF.

When processing WTs with blocked storage bins using RF, the internal process codes listed in the table are allowed for radio
frequency depending on the business context and bin type.

Business Context Execution Step Internal Process Code

Con rm WT (internal movement: TIM) RF Blocked source storage bin (B3) BIDF (cancel WT and create new WT)

Con rm WT (internal movement: TIM) RF Blocked source storage bin (B3) WTCA (cancel WT)

Con rm WT (internal movement: TIM) RF Blocked destination storage bin (B4) CHBD (change destination storage bin)

Con rm WT (internal movement: TIM) RF Blocked destination storage bin (B4) WTCA (cancel WT)

Con rm WT (stock removal: TPI) RF Blocked source storage bin (B3) BIDF (cancel WT and create new WT)

Con rm WT (stock removal: TPI) RF Blocked source storage bin (B3) WTCA (cancel WT)

Con rm WT (stock removal: TPI) RF Blocked destination storage bin (B4) CHBD (change destination storage bin)

Con rm WT (putaway: TPT) RF Blocked destination storage bin (B4) CHBD (change destination storage bin)

Con rm WT (putaway: TPT) RF Blocked destination storage bin (B4) WTCA (cancel WT)

Packing Using Radio Frequency

Use
You are able to execute packing using a Radio Frequency (RF) presentation device.

Prerequisites
You have logged on to the RF environment.

For more information, see Logon.

Features
Pack Station Logon

This is custom documentation. For more information, please visit the SAP Help Portal 50
 6/4/2022
For most of the transactions within the main menu for packing, you need to log on to a work center type that is speci ed
as your packing station. Especially if you work with the functions Automatically repack HU or Automatically repack HU
item, the system will consider all handling units (HUs) located at the packing station to propose destination HUs.

Shipping HU Creation

The creation of a single empty HU can be used as preparation for packing.

Automatic Repacking of HU

Packing HUs means consolidating several pick HUs into a destination HU. The system proposes the destination HU
based on the consolidation group for a scanned pick HU. If all repacked HUs contain the same consolidation group, the
destination HU is also assigned to that consolidation group.

Automatic Repacking of HU Items

Packing HU items means deconsolidating several pick HU items into destination HUs. The system proposes the
destination HU based on the consolidation group of the pick TO that belongs to the scanned HU item. If all repacked HU
items contain the same consolidation group, the destination HU is also assigned to that consolidation group.

Shipping HU Creation Without Logon to Packing Station

You can also create a new HU without logging on to a packing station. In this case, the system does not propose a
packaging material or a bin. The creation of a single empty shipping HU can be used as preparation for repacking HU
items or HUs.

Manual Repacking of HU

You can also repack HUs without logging on to a packing station. In this case, the system does not propose a destination
HU. Instead, you have to enter the destination HU manually. The system still validates the consolidation group of the
destination HU against the consolidation group of the pick HU.

Manual Repacking of HU Item

You can also repack HU items without logging on to a packing station. In this case, the system does not propose a
destination HU. Instead, the user scans the destination HU. The system still validates that the consolidation group of the
HU item matches the one of the destination HU

HU Maintenance

You can use HU maintenance to check and/or change the weight and volume of a HU, for example.

Manual Repacking of all HU Items

You can repack all line items for product in one step by selecting and scanning the source HU and the destination HU. You
can create a new destination HU during the process, for example, to merge and move pick HUs from one shipping HU to
another shipping HU.

Physical Inventory Using Radio Frequency

Use
You can also enter the count results using a radio frequency (RF) device. In this case, you must not print a physical inventory
count document or transfer the count results from the physical inventory count document to the system. Moreover, the data is
transferred to the system in a timely way.

Prerequisites
You have logged on in the RF environment. For more information, see Logon.

This is custom documentation. For more information, please visit the SAP Help Portal 51
 6/4/2022

Features
You can use physical inventory documents to perform physical inventory counting and enter the count results in the RF
device. The device automatically records the count time and the counter. The remaining steps are the same as for
physical inventory without an RF device. For more information, see Physical Inventory.

You can perform ad hoc physical inventory counting without using a physical inventory document. You enter the storage
bin to start counting in the RF device. The device automatically creates the physical inventory document and records the
count time and the counter. The remaining steps are the same as for physical inventory without an RF device. For more
information, see Physical Inventory.

If the storage bin is handling-unit managed, you can carry out the physical inventory counting with handling unit
collective counting using the RF device. For more information, see Collective Counting Using Radio Frequency.

Activities
You carry out a physical inventory count and enter the count results in the RF device. The device automatically records the
count time and the counter. The remaining steps are the same as for physical inventory without radio frequency. For more
information, see Physical Inventory.

Collective Counting Using Radio Frequency

Use
On the RF device, you can perform handling unit (HU) counting by entering the total count results without verifying each HU
number.

Prerequisites
You have selected both HU Complete checkbox and Display Item Objects at Time of Count Entry checkbox in
Customizing for Extended Warehouse Management under Internal Warehouse Processes Physical Inventory Physical-
Inventory-Area-Speci c Settings De ne Physical Inventory Area .

You have activated HU collective counting by selecting HU Count or HU Item Count in HU Count eld in Customizing for
Extended Warehouse Management under Internal Warehouse Processes Physical Inventory Physical-Inventory-Area-
Speci c Settings De ne Physical Inventory Area .

You have logged on in the RF environment. For more information, see Logon.

You have performed the inventory counting in the storage bin with the HU Requirement eld selected as X in the
Storage Type De nition tab in Customizing for Extended Warehouse Management under Master Data De ne Storage
Type .

You have created a storage-bin-based physical inventory document.

Features
You can carry out physical inventory counting in the following ways:

By entering the number of HUs in a storage bin. If the total number matches, the RF device displays COMPLETE for all
HUs.

This is custom documentation. For more information, please visit the SAP Help Portal 52
 6/4/2022
By entering the number of products in full HUs and partial HUs of a storage bin. If the total number matches, the RF
device displays COMPLETE for all HUs.

Ad Hoc Movements Using Radio Frequency

Use
You can carry out ad hoc movements for products and handling units (HUs) using a radio frequency presentation device (RF
presentation device).

Prerequisites
You have logged on in the RF environment.

Features
Log on at a work center.

For most transactions within the main menu for the ad hoc movement, you have to log on at a speci c work center to
receive proposals for different entry elds.

You do not select the required data from the stock overview. Instead, you either scan it in or enter it directly:

Scan in storage bin

Scan in product

Manually enter the quantity

Manually enter the warehouse process type

Manually enter the reason (optional)

If a product with different stock characteristics (batches) is contained in the storage bin, you can use a list to select the
desired product.

For handling units, you cannot unpack or repack the products by creating a product warehouse task in the HU warehouse
task.

For more information about ad hoc movements, see Ad Hoc Movement or Executing an Ad Hoc Movement.

Activities
Executing Ad Hoc Movements Using Product Warehouse Tasks

1. You manually create a product warehouse task.

a. You have to specify the source storage bin and the product.

The system displays a further screen if the source storage bin and product speci ed by you do not lead to a
unique stock determination. You select the corresponding stock, for example, product A from the free stock B.

You can specify a reason for the ad hoc movement.

You can call up the product details. The system displays the following:

The product short text

This is custom documentation. For more information, please visit the SAP Help Portal 53
 6/4/2022
If applicable, whether the product contains a hazardous substance

If the product contains a hazardous substance, you can view this information by choosing Display
Hazardous Substance Detail Information.

If applicable, the product batch

The available quantity in operative unit of measure

If there is more than one stock of the product, you can also display the stock overview for that product.

b. You specify the process type so that the system can create the product warehouse task.

c. You specify the source quantity in operative or base unit of measure.

You can also manually specify the destination storage bin. If you do not enter a destination storage bin, the
system determines it according to the storage type putaway strategies.

2. The system creates the product warehouse task..

3. You transfer the products to the destination storage bin and con rm the product warehouse task by scanning at the
destination storage bin.

If you can only enter an insufficient quantity at the destination storage bin, for example because you have damaged a
product during the transfer, you can enter this insufficient quantity and include an exception code. You can use this
exception code to trigger follow-up actions that you have de ned in Customizing.

Executing Ad Hoc Movements Using HU Warehouse Tasks

1. You manually create a HU warehouse task.

a. You scan the HU.

The system displays the following:

The source storage bin

The HU type

If applicable, whether the HU contains a hazardous substance

If the HU contains a hazardous substance, you can view this information by choosing Display Hazardous
Substance Detail Information.

You can display the contents of the HU for information purposes.

b. You specify the process type and a reason (optional) so that the system can create the HU warehouse task.

c. You manually enter either the destination storage bin or the destination HU.

If you do not enter anything, the system determines the destination storage bin or destination HU according to
the storage type putaway strategies.

2. The system creates the HU warehouse task.

3. You transfer the HUs to the destination storage bin or destination HU and con rm the HU warehouse task by scanning
the destination storage bin or destination HU.

Yard Movement Using Radio Frequency

Use

This is custom documentation. For more information, please visit the SAP Help Portal 54
 6/4/2022
You can also execute yard movements in a radio frequency (RF) environment.

Prerequisites
You have logged on in the RF environment (see Logon).

Activities
Create Warehouse Task

1. Scan the transportation unit (TU) and specify the standard carrier alpha code (SCAC) or carrier.

The system creates a warehouse task (WT) for the handling unit that is assigned to the TU.

2. Con rm the WT on the desktop.

Create and Con rm Warehouse Task

1. Scan the TU.

The system creates a WT for the handling unit that is assigned to the TU.

2. Con rm the WT by scanning the destination storage bin.

Querying Using Radio Frequency

Use
You can query the following in a radio-frequency (RF) environment:

A handling unit (HU)

A stock

A warehouse order (WO)

Prerequisites
You have logged on in the RF environment. On the launchpad, you choose Extended Warehouse Management Execution Test
RF Environment. . Specify a warehouse number, a resource, and a presentation device. The system displays an overview with
menu options. Choose 05 Internal Processes. The system displays the next menu options. Choose 03 Query.

Features
You can start queries using both the launchpad and the respective function keys in the RF transactions, such as for picking or
putaway.

You have the following options when querying using RF:

HU query (01 HU Query)

Stock query (02 Stock Query)

By storage bin (01 Stock Query by Storage Bin)

By product (02 Stock Query by Product)

This is custom documentation. For more information, please visit the SAP Help Portal 55
 6/4/2022
WO query (03 WO Query)

By WO (01 WO Query by WO)

By warehouse task (WT) (02 WO Query by WT)

By queue (03 WO Query by Queue)

By HU (04 WO Query by HU)

Activities
HU Query

1. Scan the HU number.

The system displays the corresponding products and, in the case of nested HUs, it also displays lower-level HUs. This
means that you can navigate through the whole HU hierarchy up to product detail level.

2. If necessary, display the detailed HU data.

If you are working with nested HUs, you can also display the products of all HUs within the HU hierarchy. Additionally, you
can navigate back to the highest-level HU.

3. Specify a line number for a HU or a product.

The system displays either the corresponding HU level with its products and the lower-level HUs, or the detailed product
data.

Stock Query by Storage Bin

1. Scan the storage bin.

The system displays the corresponding products and their quantities.

2. If necessary, display the detailed storage bin data.

3. Enter a line number.

The system displays the stock details.

Stock Query by Product

1. Scan the product.

The system displays the corresponding storage bins and their quantities.

2. If necessary, display the detailed product data or sort the storage bins by stocks in descending order.

3. Enter a line number.

The system displays the storage bin details.

WO Query by WO, WT, or Queue

1. Depending on the menu option that was selected rst, you scan the WO, the WT, or the queue.

The system displays the relevant WTs.

2. If necessary, display the detailed WT data.

Additionally, you can restrict the WT display to open WTs or con rmed WTs, or you can display all WTs

This is custom documentation. For more information, please visit the SAP Help Portal 56
 6/4/2022
WO Query by HU

1. Scan the HU.

2. Choose whether the system searches for WTs that have the scanned HU as the source HU, the destination HU, or both.

The system displays the relevant WTs.

3. If necessary, display the detailed WT data.

Additionally, you can restrict the WT display to open WTs or con rmed WTs, or you can display all WTs.

Resource Management Using Radio Frequency

Use
You can change the assignment of the default queue, that is, the assignment of the queue that the system checks rst to see if
any work exists for a resource. Additionally, you can change the assignment of resources to groups.

Prerequisites
You have logged on in the radio-frequency (RF) environment. On the launchpad, you choose Extended Warehouse
Management Execution Test RF Environment . Specify a warehouse number, a resource, and a presentation device. The
system displays an overview with menu options. Choose 05 Internal Processes. The system displays the next menu
options. Choose 05 Resource Management.

When you specify a new queue, you must have de ned it within the resource group. To do so, on the launchpad, choose
Extended Warehouse Management Master Data Resource Management De ne Queue Sequence - Resource Group .

Features
You have the following options for resource management using RF:

Changing the queue (01 Change Queue)

You can specify a new queue directly or select a new queue via the input help.

Changing the resource group (02 Change Resource Group)

You can specify a new resource group and a new queue.

Handling Unit Differences Using Radio Frequency

Use
You can enter differences for handling units (HUs) in the radio-frequency (RF) environment.

Prerequisites
You have logged on in the RF environment. On the launchpad, you choose Extended Warehouse Management Execution Test
RF Environment . Specify a warehouse number, a resource, and a presentation device. The system displays an overview with
menu options. Choose 05 Internal Processes. The system displays the next menu options. Choose 07 Enter HU Difference (if
necessary, use v to scroll down).

This is custom documentation. For more information, please visit the SAP Help Portal 57
 6/4/2022

Features
You can enter a difference quantity for a HU at product detail level. The system posts the difference quantity according to this
exception code, for example, in the goods receipt process at the expense of the supplier.

Activities
1. Specify the HU, the warehouse task relevant to this HU that was con rmed last, and an exception code.

The system displays the corresponding products and, in the case of nested HUs, it also displays lower-level HUs. This
means that you can navigate through the whole HU hierarchy up to product detail level.

2. If necessary, display the detailed HU data.

If you are working with nested HUs, you can also display the products of all HUs within the HU hierarchy. Additionally, you
can navigate back to the highest-level HU.

3. Specify a line number for a HU or a product.

The system displays either the corresponding HU level with its products and the lower-level HUs, or the detailed product
data.

4. Specify the quantity difference for a HU at product detail level and book it out.

Receipt of Handling Units in Transit Warehouse

Use
You can receive handling units (HUs) or HU containers into a transit warehouse.

Prerequisites
The freight order document is available in Extended Warehouse Management.

The transportation unit is docked at a door.

If you are working in the rst transit warehouse in the chain, you have printed the labels for the HUs to be received.

Features
You can search for the freight order by transportation unit (TU), door or door bin using radio frequency (RF) transaction
Receiving by TU/Door (TW). In the RF menu, choose Inbound Processes Receiving of Handling Units Receiving by TU/Door
(TW) .

In the transaction, you can get a list of HUs that are expected in the freight order and the HUs that have already been received.

If measures such as weight, volume, or dimensions of the HU are missing, you can enter them manually or retrieve from a
device, such as a scale.

You can direct HUs that require clari cation, such as HUs where the HU attributes do not match the attributes of the planned
items, to the clari cation area.

If more physical HUs than are expected in the freight order arrive, you can create HUs for them in the system and receive the
HUs.

This is custom documentation. For more information, please visit the SAP Help Portal 58
 6/4/2022
If fewer HUs than are expected in the freight order arrive, you can complete receiving for the freight order despite the missing
HUs. The missing HUs are deleted from the freight order.

Unloading of HU Containers in Transit Warehouse

Use
You can unload handling unit (HU) containers in a transit warehouse.

Prerequisites
You have received the HU container.

The HU container is not blocked for unloading.

If you are working in the rst transit warehouse in the series, you have printed the labels for the HUs to be received.

Features
You can search for the HU container in the radio frequency (RF) transaction Unload HUC (TW). In the RF menu, choose Inbound
Processes Receiving of Handling Units Unload HUC (TW) .

You can get an overview of HUs that are expected in the HU container and the HUs that have already been received.

If measures such as weight, volume, or dimensions of the HU are missing, you can enter them manually or retrieve from a
device, such as a scale.

You can direct HUs that require clari cation, such as HUs where the HU attributes do not match the attributes of the planned
items, to the clari cation area.

If more physical HUs than are expected in the HU container arrive, you can create HUs for them in the system and receive the
HUs.

If fewer HUs than are expected in the HU container arrive, you can complete unloading the HU container despite the HUs that
have not been received. The system deletes the expected HUs from the freight order.

Loading of HU Containers in Transit Warehouse

Use
You can load handling unit (HU) containers in your transit warehouse.

Prerequisites
The freight booking for the HU container has been created.

You are logged on to a work center type that is speci ed as packing station.

Features
In the radio frequency (RF) menu, choose Outbound Processes Packing Load HUC (TW) .

This is custom documentation. For more information, please visit the SAP Help Portal 59
 6/4/2022
You can search for a freight booking using the following criteria:

Freight booking

HU container or HU that belongs to a freight booking

Master air waybill (MAWB) of a freight booking

Alternatively, you can select a freight booking from the F8 list. By default, the system searches for freight bookings due on the
current date. You can de ne a time range in which the system searches for the freight booking instead.

You can get a list of planned HU containers and HU containers that have already been loaded. You can also get a list of planned
HUs and HUs that have already been loaded.

You can reverse the loading of a loaded HU by choosing the Undo button and scanning the HU.

When you are nished loading, you can close HU container. You can also reverse the closing of the HU container.

Loading of Transportation Units in Transit Warehouse

Use
You can load handling units (HUs) or HU containers into transportation units (TUs) or TU containers in your transit warehouse.

Prerequisites
The TU or TU container has the status Arrived at Door.

Features
In the radio frequency (RF) menu, choose Outbound Processes Loading Loading by TU/Door (TW) .

You can get a list of planned HUs or HU containers and a list of the HUs or HU containers that have already been loaded.

You can reverse the loading of the last HU or HU container.

You can close the TU or TU container.

Floor Check in Transit Warehouse

Use
You use this function to check handling units (HUs) that you have found during a check of the warehouse oor of your transit
warehouse.

Features
In the radio frequency (RF) menu, choose Internal Processes Floorcheck (TW) .

The following issues can have occurred:

The HU does not exist in the system. There is no record of it in the transit warehouse.

This is custom documentation. For more information, please visit the SAP Help Portal 60
 6/4/2022
Open warehouse tasks exist for the HU.

The HU has not yet been received.

According to the system, the HU is in a different storage bin.

According to the system, the HU is in a HU container.

According to the system, goods issue has been posted for the HU.

The HU is assigned to a transportation unit (TU), but the TU is overdue.

You can get detailed data and content information for the HU container or HU in the transaction.

You can indicate that the HU requires clari cation. The system creates a warehouse task to move the HU to the clari cation
zone.

You can trigger automatic adjustment in the system for the following issues:

If the HU is in a different bin in the system, the system posts the HU to the bin that it is actually in.

If the HU is in a HU container in the system, the system unpacks the HU from the HU container and places it in the bin
that it is actually in.

If goods issue has been posted for the HU, the system uses the old data to create the HU in the bin that it is actually in.

In addition, you can solve the following issues manually:

If there are open warehouse tasks for the HU, you can process the warehouse tasks using the standard RF transactions,
for example, putaway or picking transactions.

If HU does not exist in the system, you can move the HU to the clari cation area manually, without system support.

If the HU has not yet been received, you can use the standard RF transaction for receiving.

If the HU is assigned to an overdue TU, you can indicate that the HU requires clari cation and trigger a move to
clari cation zone.

Handling-Unit Maintenance in Transit Warehouse

Use
You use this function to maintain handling unit (HU) or HU container data in your transit warehouse.

Prerequisites
The HU has been received in the system.

Features
In the radio frequency menu, choose Internal Processes Maintain HU (TW) .

In this transaction, you can do the following:

Change the weight, volume, and dimensions of the HU or HU container, or retrieve the weight and measures from a
device, such as a scale

This is custom documentation. For more information, please visit the SAP Help Portal 61
 6/4/2022
View the content information for the HU or HU container

Indicate that a HU or HU container requires clari cation, for example, if the HU or HU container has a defect

Trigger printing of HU labels

Optimization Functions of the RF Execution

You can optimize the execution in your radio-frequency (RF) environment by using the following functions:

Interleaving Using Radio Frequency

Semi-System-Guided Processing Using Radio Frequency

Resource Execution Constraints (REC) Using Radio Frequency

Interleaving Using Radio Frequency

Use
This function allows you to optimize the utilization of your resources in a radio frequency (RF) environment by reducing the
travel times in the warehouse. The aim of this function is to minimize unused resources through an optimized distribution of the
warehouse tasks. For example, after putaway, a fork lift 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.

After completing a warehouse task, the system immediately assigns a new task to the warehouse worker, which is located near
to them. Before making each allocation, the system determines the distance, in order to nd out the task that is geographically
closest for the resource.

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. Resource processes a warehouse task of a queue 1. Same queue is processed until it is empty.

2. The subsequent warehouse task comes from another 2. The next queue is processed according to the de ned queue
queue, based on the de ned queue sequence. sequence.

Integration
This function is only available within system-guided processing.

Prerequisites
You have de ned the queue type.

In Customizing for Extended Warehouse Management, choose Cross-Process Settings Resource Management De ne
Queue Type .

You have de ned the queue sequence. By doing this, you de ne the processing sequencing of the warehouse tasks.

On the launchpad, choose Extended Warehouse Management Master Data Resource Management De ne Queue
Sequence - Resource Group .

This is custom documentation. For more information, please visit the SAP Help Portal 62
 6/4/2022
You have assigned the queue to a queue type.

In Customizing for Extended Warehouse Management, choose Cross-Process Settings Resource Management De ne
Queues .

You can exclude queues from the queue sequence.

On the launchpad, choose Extended Warehouse Management Master Data Resource Management De ne Queue
Sequence - Resource Group .

You can exclude resource types.

In Customizing for Extended Warehouse Management, choose Cross-Process Settings Resource Management De ne
Resource Types .

Semi-System-Guided Processing Using Radio Frequency

Use
This function allows you to activate semi-system-guided processing within system-guided processing. This is useful for source
storage bins that have more than one handling unit (HU). In system-guided processing, the system proposes one particular HU
to the user for processing. Finding this particular HU can take up a lot of time. 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. This
is what happens in semi-system-guided processing.

To use this function, you set the queue to semi-system-guided processing, not the source storage bin. When selecting a
warehouse task, the system checks whether a queue has been set to semi-system-guided processing. If this is the case, the
system sets the session to semi-system-guided. This affects processing in the following way:

The user verifes the source storage bin only.

The HU eld is empty. The user can scan it.

After scanning, the system checks whether:

The scanned HU is available in the speci ed storage bin

An open warehouse task exists for this HU

The reported resource is allowed to process the HU

System-guided processing Semi-system-guided processing

The screen shows you various data, such as HU, You only see the source storage bin and the input eld for the HU.
product, quantity, batch, and so on.

Warehouse task is locked Warehouse task is not locked, as it is still not clear which HU is being selected

Integration
Activating this function affects the system behavior of the system-guided processing that is precon gured in the standard
system.

Prerequisites

This is custom documentation. For more information, please visit the SAP Help Portal 63
 6/4/2022
The warehouse task must contain a source handling unit, otherwise the system performs system-guided processing,
where you have to verify the product, quantity, batch and so on. This also applies if the warehouse task has a queue
assigned to it for which semi-system-guided processing is allowed.

Select the Semi-Sys indicator for semi-system-guided processing in Customizing for Extended Warehouse Management..

Choose Cross-Process Settings Resource Management De ne Queues. .

Features
The semi-system-guided processing screen contains a pushbutton that allows you to activate the display of available HUs. You
can also trigger other queries for the HU, such as queue or storage bin.

Example
The system only locks warehouse tasks in semi-system-guided mode after scanning the HU.

Resource RSRC1 is working in system-guided processing. It is given the task to go to source storage bin SRC1, and scan an HU.
However, the storage bin contains one HU only. Resource RSRC1 moves to the source storage bin. This takes up time. Resource
RSRC2, which does not have currently have a task but is moving within the warehouse, sees HU SRC1 in the storage bin, scans
it, and takes it before RSRC1 arrives at the storage bin.

When resource RSRC1 arrives at the source storage bin, it only sees that there is no HU to be moved. The resource needs a new
task:

It restarts the transaction in the menu

Alternativley, it chooses No HU and restarts the transaction.

Resource Execution Constraints (REC) Using Radio Frequency

Use
This function allows you to control the number of permitted work resources in de ned areas of your warehouse. You de ne
these areas by assigned an REC storage group to your storage bins in master data.

The individual REC storage groups can correspond to an aisle, storage section, storage type, or another area in your warehouse.
De ne 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.

The resource execution constraint 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 de ne
the following:

If only 1 resource type can be kept in the REC storage group at a time (parameter OR).

If multiple different resource types can be kept in the REC storage group at a time, for example, fork lift and warehouse
worker. For each resource type, the maximum de ned number of work resources in the REC storage group is allowed
(parameter AND).

 Example
Resource types RT01 and RT02 are assigned to resource execution constraint A1, with a maximum number of 2 and 3
respectively. REC storage group GAN is assigned to constraint A1 with the parameter AND. This means that a maximum of 3
resources of type RT02 and 2 resources of type RT01 can work in A1 at the same time.

This is custom documentation. For more information, please visit the SAP Help Portal 64
 6/4/2022
The REC control is based on calculated times. Each time a resource enters the REC storage group, the system calculates the
estimated exit time when it leaves the area. 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. If a warning is issued,
the warehouse worker can enter the area, but he or she does so at his or her own risk.

The system calculates optimal routes for the resources, based on the travel distance calculation. The actual times may deviate
from the optimal times.

For more information about calculating resource working times, see Travel Distance Calculation.

Prerequisites
1. You have de ned resource types and a speed for these types.

In Customizing for Extended Warehouse Management, choose Cross-Process Settings Resource Management De ne
Resource Types.

2. You have de ned resources, and assigned these to resource types.

On the launchpad, choose Extended Warehouse Management Master Data Resource Management Maintain
Resources.

3. Since the system calculates the working times using the travel distance calculation, you need to have de ned a node for
each activity. You need to have assigned these nodes to aisles.

On the launchpad, choose Extended Warehouse Management Settings Travel Distance Calculation Con gure TDC -
Travel Distance Calculation .

4. You have de ned RECs.

In Customizing for Extended Warehouse Management, choose Cross-Process Settings Resource Management Control
Data De ne Resource Execution Constraints (REC).

5. You have assigned an REC storage group to the storage bins.

On the launchpad, choose Extended Warehouse Management Master Data Storage Bin Create Storage Bins / Edit
Storage Bins / Mass Edit Storage Bins .

6. The function works using the average con rmation time for warehouse tasks.

If you have activated Labor Management in your EWM system, the system uses the engineered labor standard values.

If you are not using Labor Management, you must de ne the bin access type for the REC storage group, in the master
data. You must also de ne the extract time determination for storage bins.

In Customizing for Extended Warehouse Management, choose Cross-Process Settings Warehouse Task De ne Extract
Time Determination.

Enhancement Screen Wizard

This is custom documentation. For more information, please visit the SAP Help Portal 65
 6/4/2022

Use
In the Enhancement Trigger dialog box, you can choose this option to add or remove elds from a radio frequency (RF) screen.

Features
As you go through the process of modifying the RF transition screen, the following features are available:

Each time you add or remove elds from the screen, the wizard generates an updated screen.

The wizard displays a eld catalogue from which you can choose the required elds that you want to display on the
screen. The eld catalogue displays elds from the corresponding screen structure.

You can also choose a eld from another screen structure.

When the process is complete, the wizard creates a new screen and adjusts the Customizing to display the enhanced screen
only to a speci c group of users. If you want to see the new screen, enter the personalization pro le.

The new screen is displayed in Screen Painter, where you can adjust aspects of the screen layout, such as position and eld size.

 Caution
Run this wizard only if you know the layout of the target screen to be created. The wizard does not check or control the
number of elds that can be added to an RF screen.

We recommend that you rst consider how many elds are required and whether they t into the target screen.

Example
The gure below explains how to run the enhancement screen wizard:

This is custom documentation. For more information, please visit the SAP Help Portal 66
 6/4/2022

Split Screen Wizard

Use
In the Enhancement Trigger dialog box, you can choose the Split Screen option to split a screen and distribute the existing
screen elds across several new screens.

Features
As you go through the process of splitting the radio frequency (RF) screen, into multiple screens, the wizard does the following:

Displays a eld catalog comprising existing elds from the current screen.

You can assign a new screen to each of the elds. You should also specify the screen programs and numbers for each new
screen.

Displays the screens based on your preferred sequence.

Enables you to con gure the function codes that are displayed in each resulting screen.

When the process is complete, the wizard creates a new set of screens and adjusts the Customizing to display the enhanced
screens only to the speci ed group of users. If you want to see the new screen, enter the personalization pro le.

 Caution

This is custom documentation. For more information, please visit the SAP Help Portal 67
 6/4/2022
Run this wizard only if you know the layout of the target screen to be created. The wizard does not check or control the
number of elds that can be added to an RF screen.

We recommend that you rst think about how many elds are required and whether they t into the target screen.

Example
The following gure explains the steps to run the Split Screen Wizard:

Pick by Voice

Use
The pick by voice functionality in Extended Warehouse Management (EWM) supports voice-based picking and internal moves in
the warehouse, independently of the radio frequency (RF) picking transaction. It is based on the RF framework, the RF picking
transaction, and the SAP Internet Transaction Server template generator Mobile Devices with Speech Input. It supports bar
code scanning and voice-enabling.

The pick by voice transaction uses SAPGUI dynpros whose elds 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-speci c tags that are interpreted by the Web browsers on the device.

The following dynpro eld speech attributes are supported.

This is custom documentation. For more information, please visit the SAP Help Portal 68
 6/4/2022

Attribute Description

Prompt Text Text to prompt input for a eld, such as "Enter the client".

Filled Text This text is read if speech input is successfully detected.

Help Text Help text for speech input. This text is read if no speech input is
detected or if the speech input does not t to the grammar.

Grammar Simple grammar for identifying the speech input of a given value.

GrammerLnk Complex grammar, loaded as an external le, for identifying the

speech input of a free value.

TimeOut Time in seconds until the help text is read, if no speech input is
made.

NextField Speci es the next eld with speech input.

The system interprets speech input either as a eld input value or as a command. All possible commands must be visible on the
screen and represented by a pushbutton. The RF framework supports up to 16 pushbuttons. You cannot assign commands to
function keys.

To trigger a command, switch to command mode by saying the built-in keyword "Command". Alternatively, if you make entries in
all input elds, the system automatically goes into command mode.

Using the command "Okay" is equivalent to pressing Enter.

The transaction uses the eld properties PromptText, HelpText, FilledText, Grammar, and GrammarLnk. A screen can contain
up to 10 prompt texts, grammars, and help texts.

You can use the start transaction /SCWM/RFUI_PBV to start the RF framework, set a voice-enabling parameter and start the
pick by voice transaction directly. This transaction is not part of the launchpad. The Internet Communication Framework (ICF)
service RFUI_PBV is linked to this start transaction.

You can use the Business Add-In (BAdI) Modify Screen Field Voice Properties to change the voice properties of a screen and its
elds before the screen is displayed to the user. For more information, see Customizing for Extended Warehouse Management
under Business Add-Ins (BAdIs) for Extended Warehouse Management Mobile Data Entry BAdI: Modify Screen Field Voice
Properties .

More Information
RF Navigation

RF Framework for Pick by Voice

Use
The radio frequency (RF) framework for pick by voice uses the display pro le *1. This display pro le controls the new templates,
the message display, and the text length of the pushbuttons and the menus. It is set up with the following data.

Parameter Database Field Value

Screen Height HEIGHT 16

Screen Width WIDTH 40

This is custom documentation. For more information, please visit the SAP Help Portal 69
 6/4/2022

Parameter Database Field Value

Pushbutton Text Length PUSHB_LEN 40

Number of Pushbuttons Available on the PUSHB_QTY 16

Screen

Menu Item and Logical Transaction Text MENU_LEN 40

Length

Message Display MSG_VIEW 0 (=Pop-up message screen)

Template Screen Program TMPL_PROGR /SCWM/SAPLRF_TMPL

Template Screen Number TMPL_NUM 11

Template (with Bottom Message) Screen TMPL_MSG_PROGR /SCWM/SAPLRF_TMPL

Program

Template (with Message Line) Screen TMPL_MSG_NUM 0002

Number

Template Screen Title Program TMPL_TITL_PROGR

Template Screen Title Number TMPL_TITL_NUM

Text TEXT Pick by Voice

The eld Data Entry in the presentation device has an additional xed value 1 –– Voice recognition. The data entry
controls the PbV-speci c functionality, such as setting the prompt text.

The main menu PBV contains the logical transaction PVSYSN.

The template screen contains 16 pushbuttons which contain all possible functions. The user can only trigger the visible
functions. The RF framework can handle up to 16 pushbuttons. These pushbuttons can contain text up to 40 characters.

The standard presentation pro le **** has an additional personalization pro le *1. This personalization pro le contains
the main menu PBV.

Prerequisites
You have entered 1 in the Data Entry eld and *1 in the Displ.Prof eld in the presentation device. You do this on the
launchpad under Extended Warehouse Management Master Data Maintain Presentation Device . You should also leave
the Shortcut eld here blank.

In the RF user settings, you have entered *1 in the Prsn.Prof. eld. You do this on the launchpad under Extended
Warehouse Management Master Data Resource Management Maintain User Settings - Radio Frequency .

More Information
Radio Frequency Framework

Standard RF Functionalities in Pick by Voice

Use
The radio frequency (RF) framework supports standard RF functionalities, including the following:

Logon

This is custom documentation. For more information, please visit the SAP Help Portal 70
 6/4/2022
Logon to the RF framework is voice-enabled. In the RF framework, you can store logon data such as default warehouse,
resource, and presentation device for a given user, according to SAP logon user name. Based on this data, the system
can skip the RF framework logon completely, or populate the elds with the user's data. If the screen is not skipped, the
system populates the elds with the values maintained in master data for the user. If the screen is skipped, the system
says, for example, “You are logged on to warehouse W001 with resource SAP10”.

Logoff

Logoff from the RF framework is voice-enabled. The user can enter a reason for logging off if you have maintained
reasons in Customizing for Extended Warehouse Management under Cross-Process Settings Warehouse Task De ne
Reasons for Warehouse Movements . If warehouse orders are still assigned to the user, the system informs the user of
this. The user can then use a command to unassign the orders.

Menu

The menu entries are customizable. The system informs the user which menu entries are available. The entries are not
numbered.

If the menu only contains one entry, and the RF logon is not skipped, the system triggers this entry.

If the menu contains more than three entries, the system says “Select menu via command” to the user.

If the menu contains more entries than will t on one page, the system says “Select menu via command. More
than one page available” to the user.

Messages

All spoken parts to the user are represented by messages.

In the standard setup, there is no command to repeat the prompt text for a eld. If the user does not speak for a while,
the text of the Help Text is spoken to the user.

More Information
Standard RF Functionalities

Working with RF for Pick by Voice

Use
The pick by voice transaction has no selection screen; only system-guided work is possible. This means that the system assigns
the next warehouse order to the resource. The validation elds are customizable and can be switched on and off according to
user preference and knowledge, and the current process data. You can make these settings in Customizing for Extended
Warehouse Management under Mobile Data Entry Veri cation Control .

Features
The main pick by voice procedure consists of the following steps:

1. Warehouse order overview (PVHUIN)

The user is informed that there is a new warehouse order and gets the activity area where the picking takes place, and
the amount and type of pre-assigned pick-handling units (pick-HUs). The user can con rm the information and continue
with the next step, or trigger printing using a command. The text of the packaging material given to the user is the short
product description of the packaging material from the product master. A maximum of two different packaging materials
are supported in the prompt text. Entries without a HU number are ignored.

This is custom documentation. For more information, please visit the SAP Help Portal 71
 6/4/2022
2. Source storage bin for product warehouse task (PVMTTO)

The user gets the source storage bin information (separated into storage type, aisle, stack, and level), the product, the
quantity, and the destination pick-HU. If the user has more tasks to pick for this warehouse order, the user repeats this
step until all tasks are picked.

The user is guided to the source storage bin and must enter the veri cation value of the storage bin master. In the
standard setup, the product is not validated. For the level, the validation is either the value or the veri cation value from
the storage bin master. For the storage bin validation, the user only has to validate the difference between one storage
bin and the next.

If there is a difference, the user can use the command “Difference”, and then speak the actual quantity that is in the bin.
The difference quantity is calculated from the requested quantity minus the entered quantity. If the default difference
type does not match, the user can trigger a different difference exception from the exception code list screen. You can
maintain a default difference exception code for the internal exception that decides the kind of difference in Customizing
for Extended Warehouse Management under Cross-Process Settings Exception Handling Assign Internal Exception
Codes to Exception Codes .

3. Destination storage bin for HU-WT ( PVPLHU)

The user gets the destination storage bin information (separated into storage type, aisle, stack, and level), and the pick-
HU that has to be put away. If the user has more pick-HUs to put away in different destinations, the user repeats this
step until all of them have been put away.

The validation of the destination bin depends on the storage bin master data. If the master data contains aisle, stack,
and level information, this information is used for the validation. If the user has to put more than one HU at the same
destination, the system does not require the user to validate each HU separately. Instead, the user can place the HUs in
one step.

The following screens are also voice-enabled:

Source storage bin for HU warehouse task

Guides the user to the correct source storage bin to take the HU.

Destination storage bin for product warehouse task

Guides the user to the correct destination storage bin to put away the appropriate quantity of a product.

Stock check

The system has determined a low stock check situation for the current storage bin. This screen is displayed and the user
has to enter the remaining quantity.

Change destination bin

The user realizes that the proposed destination storage bin is full or cannot be reached. Therefore the user enters a new
storage bin or lets the system propose a new storage bin.

Semi-system guided picking

The system identi es that the queue of the resource contains several HU moves from a particular area. The user is
guided to this area and must select a HU there. Then the picking process starts as normal.

HU Validation

The voice-enabled transaction has a speci c veri cation logic for the HU. To avoid the user having to say the complete HU
number, the system determines the minimum number of digits from the end of the HU number that are needed to get a unique
result in the storage bin. The amount of digits is spoken to the user. The user has to say at least two digits, regardless of how

This is custom documentation. For more information, please visit the SAP Help Portal 72
 6/4/2022
many are needed to make the HU number unique in the bin. For example, instead of saying the entire HU number
“376170137518461130”, it could be sufficient to say “30”.

Split of Storage Bin into Separate Fields

Instead of telling the user the complete storage bin, such as “0010-01-05-B”, it is easier to split the storage bin into storage
type (0010), aisle (01), stack (05), and level (B). For storage type, aisle, and stack there is one-to-one validation. For the level,
the validation is either the value or the veri cation value from the storage bin master. The system only tells the user the
difference between the storage bins of the previous warehouse task and the current warehouse task. For example, if the next
bin is in the same aisle as the previous one, the system starts with the stack and not with the storage type. If the aisle, stack,
and level are not maintained in the storage bin master, the system says the entire storage bin to the user.

Determination of Validation Pro le by Data Entry

If a pick by voice user and a radio frequency (RF) user work in the same area of your warehouse, the de ned validation pro le
may not t for both applications. Therefore you can de ne different validation pro les and assign it by using different data entry.
You specify General Data Entry for RF transactions and Voice Recognition for pick by voice transactions.

Voice Property Maintenance

In the pick by voice transaction, voice prompt texts, voice help texts, and voice lled texts are based on voice texts. You can
replace the standard voice texts with your own voice texts in the following ways:

You can change the voice properties of a screen and its elds before the screen is displayed to the user in see
Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse
Management Mobile Data Entry BAdI: Modify Screen Field Voice Properties .

You can change the voice texts directly without any coding in Customizing for Extended Warehouse Management under
Mobile Data Entry Maintain Voice Properties .

 Note
The pick by voice transaction uses aisle, stack, and level to validate the location. If you switch off this validation in
Customizing for Extended Warehouse Management under Mobile Data Entry Veri cation Control , you must change
the voice texts in Customizing.

Voice texts related to aisle, stack, and level (/SCWM/RF_EN 559, 571, 572, 573) always contain the same
parameter values, that is:

&1 = Aisle

&2 = Stack

&3 = Level

&4 = Storage Type

Example

You switch off the validation for aisles using veri cation control. The system does not process message
/SCWM/RF_EN 559 (Storage type &4: Go to aisle &1) because the cursor is positioned in the validation eld of the
stack. Instead, the system says message /SCWM/RF_EN 551 (Go to stack &2) to the user. This means that the aisle
information is missing. You can now create a new message in your namespace and use the relevant parameter values
such as Storage type &4, aisle &1, stack &2. You must then use the new message in the Customizing activity
Maintain Voice Properties.

Bin Veri cation Value

This is custom documentation. For more information, please visit the SAP Help Portal 73
 6/4/2022
If a pick by voice user and an RF user work in the same area of your warehouse, the validation value for the storage bin may
need to be different for both applications. For example, you need a short alphanumeric validation such as A in pick by voice but a
longer more precise validation such as 0101 for the RF transaction. Therefore you can maintain a new value for the validation in
pick by voice in the storage bin master. If you do not maintain a speci c value for pick by voice, the original value is used as
before.

More Information
Exceptions

Exceptions

Use
The list of valid exceptions depends on the type of warehouse task (handling unit (HU) warehouse task or product warehouse
task) and on the current step of the process (source storage bin or destination storage bin).

Features
The following exception steps are available for pick by voice:

P1: PbV HU WT Action on Source Data

P2: PbV HU WT Action on Target Data

P3: PbV Product WT Action on Source Data

P4: PbV Product WT Action on Target Data

The following exceptions are supported in the business contexts TIM — Con rm Warehouse Task (Intern. Movemnt) and TPI —
Con rm Warehouse Task (Stock Removal):

HU warehouse task on source storage bin (Step P1)

DIFF — Post with Difference

HUMI — No Handling Unit Exists

NEXT — Continue

SKVA — Skip Complete Validation

HU warehouse task on destination storage bin (Step P2)

CHBD — Change Destin. Storage Bin (Location)

DIFF — Post with Difference

SKVA — Skip Complete Validation

Product warehouse task on source storage bin (Step P3)

DIFF — Post with Difference

NEXT — Continue

SKVA — Skip Complete Validation

This is custom documentation. For more information, please visit the SAP Help Portal 74
 6/4/2022
SPLT — WT Split

Product warehouse task on destination storage bin (Step P4)

CHBD — Change Destin. Storage Bin (Location)

DIFF — Post with Difference

SKVA — Skip Complete Validation

SPLT — WT Split

The following internal exceptions allow you to trigger exceptions directly with buttons from the main pick by voice screen:

BIDF — Trigger Pick Denial for Entire Quantity

BIDP — Trigger Pick Denial for Partial Quantity

DIFF — Trigger default difference

LIST — Trigger List of Valid Exceptions

The following internal exceptions support error handling in radio frequency (RF) warehouse task con rmation:

RF01 — Error during WT con rmation in RF

RF02 — Error during WT creation in RF

For all the internal exceptions, you must de ne exceptions for execution step Data Veri cation in Background. You de ne these
exceptions in Customizing for Extended Warehouse Management under Cross-Process Settings Exception Handling De ne
Exception Codes .

The exception NEXT only works for the same step. This exception means that at the end of the warehouse task list for the
source step, it is not automatically changed to the destination step. The system says “End of task list. Next task not possible” to
the user.

The internal exceptions BIDF and BIDP are dependent on the quantity the user has entered before the Pick Denial button or
command is triggered. If the quantity eld is empty, the system assumes that there is a full pick denial and triggers the internal
exception BIDF. If the quantity eld is not empty, the system assumes that there is a partial pick denial and triggers the internal
exception BIDP.

The Difference button on the source screen for product warehouse tasks is linked to the internal exception DIFF. You can
maintain a default difference exception code, based on the internal exception, which decides the type of difference, for example,
difference as charges for the warehouse or difference as charges for the storage bin. This exception code is determined by
choosing Difference. The quantity entered is the available quantity, and the difference quantity is calculated from the requested
quantity minus the entered quantity. You can use this to trigger difference reporting easily without navigating to the exception
code list screen.

More Information
Working with RF for Pick by Voice

This is custom documentation. For more information, please visit the SAP Help Portal 75