SAP Radio Frequence Framework

Radio Frequency Framework
PDF download from SAP Help Portal:

http://help.sap.com/saphelp_ewm91/helpdata/en/4d/4fa477c9c20c7ae10000000a42189c/content.htm
Created on August 22, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 29
Table of content
1 Radio Frequency Framework
1.1 RF Navigation
1.2 RF Function Keys
1.3 Standard RF Functionalities
1.3.1 Logon
1.3.2 Logoff
1.3.3 Recovery
1.3.4 Position Management
1.4 Work Processing Using Radio Frequency
1.4.1 Loading and Unloading Using Radio Frequency
1.4.2 Deconsolidation Using Radio Frequency
1.4.3 Putaway Using Radio Frequency
1.4.4 Receipt of Handling Units (HUs) Using RF
1.4.5 Confirmation Correction Using Radio Frequency
1.4.6 Picking
1.4.6.1 RF Picking Flow
1.4.7 Picking at a Pick Point Using Radio Frequency
1.4.8 Block Storage Bins for Open Warehouse Tasks Using RF
1.4.9 Packing using Radio Frequency
1.4.10 Physical Inventory Using Radio Frequency
1.4.11 Ad Hoc Movements Using Radio Frequency
1.4.12 Yard Movement Using Radio Frequency
1.4.13 Querying Using Radio Frequency
1.4.14 Resource Management Using Radio Frequency
1.4.15 Handling Unit Differences Using Radio Frequency
1.4.16 Optimization Functions of the RF Execution
1.4.16.1 Interleaving Using Radio Frequency
1.4.16.2 Semi-System-Guided Processing Using Radio Frequency
1.4.16.3 Resource Execution Constraints (REC) Using Radio Frequency
1.5 Enhancement Screen Wizard
1.6 Split Screen Wizard
1.7 Pick by Voice
1.7.1 RF Framework for Pick by Voice
1.7.2 Standard RF Functionalities in Pick by Voice
1.7.3 Working with RF for Pick by Voice
1.7.3.1 Exceptions
1.7.3.2 Improving Performance
1.7.3.3 Error Handling
PUBLIC
Page 2 of 29
1 Radio Frequency Framework

Extended Warehouse Management (EWM) includes the implementation of a radio frequency (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 verification/input data, keystroke, or logon request)
Enables personalized menus and screens
Enables flexible and user-friendly screen and flow logic generation and modification
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.
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 predefined pushbuttons, or they
can be operated using a keyboard. If you are 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 for connecting browser-based devices.
Bar Code Support
The RF framework supports the use of bar codes for identification and verification purposes. SAP currently supports EAN 128 bar code types, but you can also
support other types within the RF framework.
Screen Layout Personalization
Using the RF screen manager, you can customize the appearance of RF presentation screens, so as to ensure that they are 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.
Menu Personalization
Using the RF menu manager, you can define 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
1.1 RF Navigation
PUBLIC
Page 3 of 29
Purpose
This section describes the process for navigating from RF menus to transactions, as well as navigation 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 field.
3. Virtual Navigation
Unlike the first 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 those not displayed on the current screen, but rather displayed on subsequent screens.
If on the main menu screen, you enter 415 in the Menu field, 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 field 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 fills fields with content, the input fields may either be closed, or hidden (depending on Customizing for Extended Warehouse
Management Mobile Data Entry Radio Frequency (RF) Framework Define Logical Transaction Step Profiles Define Validation Profile ).
Where the input fields are closed, you verify the values by scanning the bar codes.
After all input fields on the screen are filled, one of the following occurs:
If the Skip Shortcut indicator is set, the posting (for example, WT confirmation) is automatically triggered.
If the Skip Shortcut indicator is not set, you automatically navigate to the Shortcut field.
You can set the Skip Shortcut indicator when maintaining screens via the RF screen manager.
For more information, see the Implementation Guide (IMG) for Extended Warehouse Management Mobile Data Entry Radio Frequency
(RF) Framework RF Screen Manager.
You can invoke functions by choosing the corresponding function key pushbutton, or entering the function key in the Shortcut field.
Where necessary, you enter exception codes in the Shortcut field (for example, for differences).
You define exception codes in Customizing for Extended Warehouse Management Cross-Process Settings Exception Handling
Define Exception Codes.
PUBLIC
Page 4 of 29

1.2 RF Function Keys
Use
Function keys are provided with the RF framework.
Features
Standard Functions Keys
Standard function keys are not displayed in the function key line of an RF screen. Rather, they are accessed directly via the function key or shortcut.
Function Function Key Shortcut Description
More F5 05 Displays the next pushbuttons in the
sequence (in case of more than four push
pushbuttons for a screen)
Clear F6 06 Clears a selected input field, or all input
fields
Back F7 07 Returns to previous screen/step
List F8 08 Displays the list screen (showing the
possible input values) for a selected field
Full Message F9 09 Displays the full message on a separate
screen
Transaction-Specific Function Keys
Transaction-specific function keys are displayed in the function key line. If more than four function keys/pushbuttons exist for a screen, > is displayed, and you
can then choose F5 to display the other pushbuttons.
The following list includes only those function keys that appear as pushbuttons on the user interface.
Function Pushbutton Text Description
Bin Empty EmBn Reports that the storage bin being counted is empty
Close HU Close Ends work on a putaway HU
Clear All ClrAll Clears the contents of all input fields on the screen
Clear Sum ClSum Resets the quantity to zero during counting, or resets the
zero stock indicator
Condense HU Cond Condenses a nested deconsolidation HU into a single-level
HU
Convert HU Conv Converts a deconsolidation HU to a putaway HU
Delete HU Delete Deletes an HU
Delete HU DelHU Deletes a selected HU from the list
Details Detail Displays the WO details
PUBLIC
Page 5 of 29
Empty Bin EmBn Reports that the bin is empty
HU Completed HUCmp Reports that the HU content count is complete (HU content
is not counted, but rather taken as the system quantity)
Create HU HUCr Enables you to create a pick HU.
If a pick HU is already assigned to the WO, the system
displays the number of the existing HU
HU Details HUDet Displays details of a selected HU
HU Empty HUEmp Reports that the HU is empty
HU Overview HUOv Displays the HU overview
HU Screen HU Navigates you to the HU screen
HU Withdrawal HUWd Reports that you have picked the whole pallet
HU Items List ItList Displays the items (product and lower-level HUs) of an HU
HU List List Lists all the HUs
Nested HUs N.HUs Enables you to pick from the lower-level HUs of a nested
HU
New Item NewItm Enables you to create a new product
Does not exist NotEx Reports that the HU does not exist at this location
Pick HU Introduction PHUIn Takes you to the pick HU introduction screen (screen 0200)
Product Detail PrdDet Displays details of a selected product
Print Prnt Prints information based on BAdI /SCWM/PRINT_RF,
method PRINT_WO_HU
Product Prod Navigates you to a screen where you can scan a product
number, and the relevant WTs are displayed
Product Detail ProDe Shows detailed product data
Propose Bin Prop Proposes a new bin for the product or HU WT
Recover Resource RcvRe Enables you to select a resource with which to continue
working (in the case of work interruption when you were
logged on to more than one resource)
Reverse Revers Reverses the order of entries in the list
Remaining Quantity RQty Enables you to report the remaining quantity, during a zero
stock check
Reverse Sequence RvSeq Reverses the sequence of WTs in a WO
Skip Skip Skips the entry and starts at the next one in the list
Skip to End Skip Places the current entry to the end of the list
Stock Overview StOv Displays available stock of a selected product
Select WT WT Navigates you to a screen where you can scan a WT
number, and then display the WT
WT List WTLst Displays the list of WTs in the WO
Unassign Unasn Enables you to unassign a WO from your resource
Yes or No Yes/No Answers a query message
Zero stock ZeroSt Reports that the product count for the storage bin is zero,
thus setting the zero stock indicator

1.3 Standard RF Functionalities
Use
The 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
Request work/inquiry implemented as a step of the master transaction, which initiates another transaction

1.3.1 Logon
PUBLIC
Page 6 of 29
Use
Logon to the RF environment enables the tracking of resources, stock on resources, and warehouse order (WO) selection.
After logging on to the system, a resource can operate as an active resource, which can request and execute work in the warehouse.

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 identification to determine the default resource. User-related
parameters are based on the predefined users default data.
Triggered by User
If a default resource and warehouse are defined for a user, and a default presentation device is defined 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
Logon
Automatic Logon Manual Logon
Triggered by Device Triggered by User
1. You define a user, using the user maintenance transaction ( Extended Warehouse Management Master Data Resource
Management /SCWM/USER - Maintain User on the SAP Easy Access screen).
2. When defining the user, you must assign a
default resource and default warehouse.
When defining the user, you must define a
default resource and default warehouse.
The default resource must have assigned to
it a default presentation device.
The device is defined in Extended
Warehouse Management
Master Data
/SCWM/PRDVC - Maintain
Presentation Devices on the
SAP Easy Access screen.
The device is assigned using the
resource maintenance transaction
( Extended Warehouse
Management Master Data
Resource Management
/SCWM/RSRC Maintain
Resource on the SAP Easy
Access screen).
On the SAP Easy Access screen, you
choose Extended Warehouse
Management Execution
/SCWM/RFUI - Log On to RF
Environment.
The logon screen appears.
3.

You define a presentation device, using the
presentation device maintenance
transaction ( Extended Warehouse
Management Master Data
/SCWM/PRDVC - Maintain Presentation
Devices on the SAP Easy Access
screen).
When defining the presentation device, you
must have assigned to it the default
resource.
The presentation device is one that is able
to identify itself.
You enter the warehouse number, resource
and presentation device with which to log
on. One or more of these fields may be
filled with default parameters, depending on
your user and resource definitions.
If you do not fill the DefPresDvc field on
the Logon screen, it is filled with one of
the following:
The default presentation device
defined for the resource in the
resource maintenance transaction
The presentation device set as the
default in the presentation device
maintenance transaction, if no
default presentation device is
defined for the resource
4. When you turn on the presentation device,
it calls SAPConsole, which initiates the RF
presentation transaction, and logs on
automatically.
On the SAP Easy Access screen, you
choose Extended Warehouse
Management Execution
/SCWM/RFUI - Log On to RF
Environment.
If you set the Auto Logon indicator
when defining the user, you are
logged on automatically.
If you did not set the Auto Logon
You choose Enter to log on.
PUBLIC
Page 7 of 29
indicator, the Logon screen
appears, with the fields being
filled with the default parameters.
You may either keep the default,
or change any of them. You then
choose Enter to log on.
If you set the Auto Logon indicator,
multiple logons are not possible.
5. During logon, the Dynpro layer identifies the display profile assigned to the specific presentation device.
The business logical layer does the following:
Addresses the logon to resource management, to perform the logon process
Fetches the resources personalization profile 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.

1.3.2 Logoff
Use
This function enables a resource to log off from the RF environment.

Integration
Logoff is a step of the logon logical transaction.

Activities
1. You choose F1 Logoff .
2. You enter a reason code for logging off and choose F1 Save .
The resources logoff request is sent to resource management, via the business logic layer package.
The resource is logged off from the RF environment.
Depending on the reason code, the WOs assigned to the resource either remain assigned to it, or are unassigned.

1.3.3 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 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 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 e pushbutton, enabling the user to select the resource
with which to continue.
3. The system checks whether a specific WO that was assigned to the resource was stopped before completion. It does so by checking for WOs that fulfill all of
PUBLIC
Page 8 of 29
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 finds any WOs that fulfill these conditions, it does the following:
a. Finds the relevant logical transaction
b. Finds the WOs data
c. Displays the screen of the relevant step
5. If the system does not find any WOs that fulfill these conditions, the system displays the Menu screen.
1.3.4 Position Management
Use
Position management enables an 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.

Prerequisites
In Customizing for Extended Warehouse Management Cross-Process Settings Resource Management Define Resource Types , you have
selected one of the following options for the Pos.Mgmt field:
Manual
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 resources resource type 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 field.
3. If the resources resource type has manual position management, the following occurs:
a. The cursor moves to the position field.
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 field.
4. In the background, an internal warehouse task (WT) is created to update the HU location and logical position.

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
Confirmation Correction Using Radio Frequency
For goods issue:
PUBLIC
Page 9 of 29
Picking Using Radio Frequency
Packing Using Radio Frequency
Loading Using Radio Frequency
For internal warehouse processes:
Physical Inventory Using Radio Frequency
Ad Hoc Movement Using Radio Frequency
Yard Movement Using Radio Frequency
Queries Using Radio Frequency
Resource Management Using Radio Frequency
{0>Handling-Unit-Differenzen mit Radio-Frequency<}0{>Handling Unit Differences Using Radio Frequency<0}
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.
You have defined a warehouse order creation rule of the type Load/Unload and have specified the number of loading employees who are to execute the
higher-level warehouse order in Customizing for Extended Warehouse Management (EWM) under Cross-Process Settings Warehouse Order
Define 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 that contains all WTs for the HUs of the 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 finds 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 first 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 confirm 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 confirmed the last WT, all warehouse orders involved are
completed (in other words, confirmed or canceled). This would also be the case, even if only one loading employee had unloaded the truck.

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.
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 fields.
Creating multiple handling units (HUs)
The creation of multiple empty putaway HUs can be used as preparation for deconsolidation.
PUBLIC
Page 10 of 29
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 transfer order (TO)
confirmation. After the TOs have been confirmed, a new TO is created that is then used for putaway. Sorting occurs by the consolidation group which is
copied from the activity area of the final putaway bin to the product TO.
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 TO.
HU overview
The HU overview screen provides an overview of the deconsolidation HU that you want to deconsolidate, for example, the number of open TOs, 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 first.

1.4.3 Putaway Using Radio Frequency
Use
You can execute putaways using a radio frequency presentation device (RF presentation device).
Prerequisites
The destination storage bins of the warehouse orders to be processed are always in the same activity area.
Features
Putaway According to Handling Unit (HU)
You enter a handling unit number (HU number) and the system searches for the corresponding warehouse order or warehouse orders.
Putaway According to HU (Collective)
You enter more than one HU number and the system searches for the corresponding warehouse orders.
Putaway According to Warehouse Order
You enter a warehouse order number and the system displays the warehouse tasks assigned to the warehouse order that are to be executed.
Activities
Putaway According to Handling Unit (HU)
1. You enter a HU number. EWM thus includes the HU in the resource.
2. The system searches for the corresponding warehouse orders.
3. The system displays the following:
If the system finds a WT for the entire HU, the system displays the source data (HU number, destination storage bin).
If the system finds WTs for the products in the HU, then you are dealing with a distributive putaway. The system displays the first WT it has found
according to the sort sequence of the destination storage bins. The system displays the following data:
Source HU
Product
Quantity
Batch
Destination HU
Destination storage bin
If a warehouse order has more than one WT, you can do the following:
You can skip a WT.
You can reverse the sequence in which the system displays the WTs.
You can place the displayed WT at the end of the execution.
4. You confirm the data of the HU WT or of the first product WT.
5. If a warehouse order has more than one product WT, the system displays the data of the next product WT and the action repeats itself.
Putaway According to Handling Unit (Collective)
1. You enter all desired HU numbers.
2. You decide whether you want to putaway further in a guided manner or according to product number or warehouse task.
3. The system searches for the corresponding warehouse task.
4. The further steps correspond to steps three to five for putaway according to handling unit.
Putaway According to Warehouse Order
PUBLIC
Page 11 of 29
1. You enter a warehouse order number.
2. The system searches for the corresponding warehouse tasks.
3. The system displays the source data (product, quantity, batch, and source storage bin) of the first product WT that belongs to the warehouse order, or the
source data (HU and source storage bin) of the first HU WT that belongs to the warehouse order.
If a warehouse order has more than one WT, you can do the following:
You can skip a WT.
You can reverse the sequence in which the system displays the WTs.
You can place the displayed WT at the end of the execution.
4. You confirm the source data of the first product WT or the source data of the first HU WT.
5. The system displays the destination data of the product WT (product, quantity, batch, and destination storage bin), or the destination data of the HU WT (HU
and destination storage bin).
6. You confirm the destination data of the first WT.
7. If a warehouse order has more than one WT, the system displays the source data of the next WT (product WT or HU WT), and the action repeats itself.
Exceptions to Putaway Using RF
HU WT Confirmation
You can specify an exception for this process and then:
Change the destination storage bin
In general, skip the HU WT that is currently to be processed
For example, if the aisle is blocked, you cannot get to the source storage bin or destination storage bin. During the putaway process, then, the system no
longer shows you this HU WT and you do not need to confirm the source data and destination data.
Product WT Confirmation
You can specify an exception for this process and then:
Change the destination storage bin
Record differences
For example, if a piece of the product quantity is damaged, you can enter a smaller product quantity rather than confirm the quantity.
Change the batch
In general, skip the product WT that is currently to be processed
For example, if the aisle is blocked, you cannot get to the source storage bin or destination storage bin. During the putaway process, then, the system no
longer shows you this HU WT and you do not need to confirm the source data and destination data.

1.4.4 Receipt of Handling Units (HUs) Using RF
Use
You use this function to optimize the goods receipt process for HUs in the inbound delivery. You pack inbound deliveries and create HUs according to the
specified 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, mixed HUs and cross-delivery HUs. If you create an HU, the system only supports
homogeneous HUs.
Prerequisites
The bar code specification is maintained in Customizing for EWM.
You do this in the Implementation Guide (IMG) for Extended Warehouse Management (EWM) by choosing Mobile Data Entry Maintain Bar Code
Specification.
In the inbound delivery document type, you have specified a determination procedure for automatic packing, and have set the indicator No Automatic
Packing . If you have specified a determination procedure and set this indicator, the system does not perform automatic packing when creating an inbound
delivery.
To do this, in the Implementation Guide (IMG) for Extended Warehouse Management (EWM) choose Goods Receipt Process Inbound Delivery
Manual Settings Define Document Type Determination for Inbound Delivery Process.
The inbound delivery is available in the EWM system.
Features
In the SAP Easy Access Menu for Extended Warehouse Management, choose Execution Log On to RF Environment Goods Receipt Processes
Receipt of HUs. This function comprises 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 Notification
Door
Dependent on this selection, the system looks for the corresponding deliveries. You then scan an HU and thereby confirm 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 or not.
If it already exists for example, if a detailed advances shipping notification exists and assigned to the current delivery, you scan the Serial Shipping
Container Code (SSCC).
PUBLIC
Page 12 of 29
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.
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 notification exists, you have to 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 you scan an HU that is not notified, the system generates the HU automatically. Here, it determines the default packaging material using the relevant
determination procedure. In the determination procedure, you have defined a packaging specification 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.
If you scan a product for which no inbound delivery item 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
Confirm 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 upon closing the transaction that a notified 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 EWM under Cross-Process Settings Exception Handling Define Exception
Codes .

Confirmation Correction Using Radio Frequency
Use
You can also use a radio frequency device (RF device) to correct warehouse tasks in the goods receipt process that have already been confirmed.
Prerequisites
You have defined a completion delay for inbound deliveries (see Confirmation Correction, under Prerequisites).
You are using a document type and item type with a status profile for which you have activated the status DWM ( see Confirmation Correction, under
Prerequisites).
Features
You can specify the following selection criteria for putaway warehouse tasks (putaway WTs):
Warehouse order (WO)
Putaway WT or a stock identification
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 confirmation correction by WO, and the warehouse order 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 fields Btch (batch) and AQty (quantity) ready for input.
5. You enter the changes and save them by choosing ENTER.

1.4.6 Picking

You are able to execute picking using an RF presentation device.
Prerequisites
PUBLIC
Page 13 of 29
Features
System-Guide Picking
The system presents the optimal WO for execution, pursuant to 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 WO from the queue, pursuant to the WO selection
mechanism.
Picking by WR
You enter a WR number, and the system finds the corresponding WO.
Picking by WO
You enter a WO number, and the system presents the WO for execution.
Picking by HU
You enter an HU number, and the system finds the corresponding WO.
1.4.6.1 RF Picking Flow
Purpose
This section shows the flow of the standard screens, in the context of the logical transactions and steps, when a user performs RF picking.

Process Flow

PUBLIC
Page 14 of 29
RF Picking - Process Flow
System-Guided Picking System-Guided Picking
by Queue
Picking By WR Picking By WO Picking By HU
1. After logging on to an RF presentation device, you choose 04 Goods Issue 01 RF Picking Main Menu .
2. You choose 01 System-
Guided Picking .
You choose 02 System-
Guided by Queue .
You choose 03 Pick by
WR .
You choose 04 Pick by
WO .
You choose 05 Pick by HU .
3.
You select a queue.
You select a WR. You select a WO. You select an HU.
4.
The system selects and locks a WO for selection, pursuant to the WO selection mechanism.
The pick HU introduction screen appears.
5. 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.
6. After introducing one or more pick HUs, you navigate to the source screen of the first 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
7. 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.
8.
After all products are picked, and have been put into the resources pick HUs, the place HU screen appears.
In case of no pick HU, the place product screen appears.
9. 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 destination HU.

1.4.7 Picking at a Pick Point Using Radio Frequency

You are able to pick at the 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 defined as a work center in
Extended Warehouse Management .
Prerequisites
You have made the following settings in Customizing for Extended Warehouse Management :
In the storage type which contains the stockt, you have set the Pick Point indicator to Active in stock removal control.
In Customizing for Extended Warehouse Management , choose Master Data Define Storage Type.
In the storage type which contains the pick point, you have set the Storage Type Role field as B (Pick Point) or C (ID and Pick Point).
In Customizing for Extended Warehouse Management , choose Master Data Define 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 field. You have also made an entry in the warehouse process type. You can also define the intermediate storage section and intermediate location.
You have set the Pick Point indicator
In Customizing for Extended Warehouse Management , choose Cross-Process Settings Warehouse Task Define Layout-Oriented Storage Control.
In the work center layout, you have define the transaction type Packing - General .
In Customizing for Extended Warehouse Management , choose Master Data Work Center Define 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 field to Check When Unpacking HUs and Products .
If you want to enter external HU numbers as well, you have selected the field RF: HU Ready for Input .
In Customizing for Extended Warehouse Management , choose Master Data Work Center Define Work Center.
Note
If the indicator is not selected, you cannot specify an HU number. The system determines the HU number from the internal number range.
Features
Logging On to the Work Center
PUBLIC
Page 15 of 29
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 first 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 defined 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.
3. If you specify an HU number, the system creates a pick-HU with the same number.
4. If you do not specify an 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, maimum 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 HU number of the HU that was transported from the warehouse to to 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. When you block a storage bin, you use an
exception code to define what is to happen to the relevant warehouse task when processing using radio frequency (RF).
When creating warehouse tasks, the system checks whether a storage bin is blocked. When blocking storage bins, the system does not check whether open
warehouse tasks exist for it. If a storage bin is blocked after you have created the warehouse task, this does not have any effect on the open warehouse task. The
system also does not check the lock indicators when confirming this warehouse task.
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 warehouse tasks in the EWM system, see Block Storage Bins for Open Warehouse Tasks.
Prerequisites
In Customizing, you have defined the exception codes that apply when you block storage bins with open warehouse tasks.
To do this, in the Implementation Guide (IMG) for Extended Warehouse Management (EWM) choose Cross-Process Settings Warehouse Task Define
Control for Blocking Storage Bins.
Activities
In the RF environment, in addition to the options described in the EWM system, you can issue messages.
You create a warehouse task with a particular warehouse process type, which in turn is dependent on the warehouse process type. When selecting a warehouse
order for a warehouse task 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 defined for the current case in the IMG 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 IMG activity select the fields 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 warehouse tasks 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
Confirm warehouse task (internal movement: TIM) RF Blocked source storage bin (B3) BIDF (cancel WT and create new WT)
Confirm warehouse task (internal movement: TIM) RF Blocked source storage bin (B3) WTCA (cancel WT)
Confirm warehouse task (internal movement: TIM) RF Blocked destination storage bin (B4) CHBD (change destination storage bin)
Confirm warehouse task (internal movement: TIM) RF Blocked destination storage bin (B4) WTCA (cancel WT)
Confirm warehouse task (stock removal: TPI) RF Blocked source storage bin (B3) BIDF (cancel WT and create new WT)
Confirm warehouse task (stock removal: TPI) RF Blocked source storage bin (B3) WTCA (cancel WT)
Confirm warehouse task (stock removal: TPI) RF Blocked destination storage bin (B4) CHBD (change destination storage bin)
Confirm warehouse task (putaway: TPT) RF Blocked destination storage bin (B4) CHBD (change destination storage bin)
PUBLIC
Page 16 of 29
Confirm warehouse task (putaway: TPT) RF Blocked destination storage bin (B4) CHBD (change destination storage bin)
Confirm warehouse task (putaway: TPT) RF Blocked destination storage bin (B4) WTCA (cancel WT)

1.4.9 Packing using Radio Frequency
Use
You are able to execute packing using a Radio Frequency (RF) presentation device.
Prerequisites
Features
Logging on to a work center
For most of the transactions within the main menu for packing, you need to log on to a certain work center. Especially if you work with the function Repacking
HUs automatically or the function Repacking HU items automatically, the system will consider all HUs located at the work center to propose destination HUs.
Creating a single handling unit (HU)
The creation of a single empty HU can be used as preparation for packing.
Repacking HUs automatically
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.
Repacking HU items automatically
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.
Creating a single HU manually
You can also create a new 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 HU can be used as preparation for repacking HU items or HUs.
Repacking HUs manually
You can also repack HUs without logging on to a work center. 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.
Repacking HU items manually
You can also repack HU items without logging on to a work center. 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.

1.4.10 Physical Inventory Using Radio Frequency

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.
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.
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).
PUBLIC
Page 17 of 29
Prerequisites
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 specific work center to receive proposals for different entry
fields.
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 Movements or Executing an Ad Hoc Movement.
Activities
Executing Ad Hoc Movements Using Product WT
1. You manually create a product WT.
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 specified 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
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 are more than one stock for 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 WT.
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 WT.
3. You transfer the products to the destination storage bin and confirm the product WT 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 defined in
Customizing.
Executing Ad Hoc Movements Using HU WT
1. You manually create a HU WT.
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 WT.
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 WT.
3. You transfer the HUs to the destination storage bin or destination HU and confirm the HU WT by scanning the destination storage bin or destination HU.

Yard Movement Using Radio Frequency
Use
You can also execute yard movements in a radio frequency (RF) environment.
PUBLIC
Page 18 of 29
Prerequisites
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. Confirm the WT on the desktop.
Create and Confirm Warehouse Task
1. Scan the transportation unit (TU).
The system creates a warehouse task (WT) for the handling unit that is assigned to the TU.
2. Confirm the WT by scanning the destination storage bin.

1.4.13 Querying Using Radio Frequency
Use
You can also 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 SAP Easy Access screen, you choose Extended Warehouse Management Execution /SCWM/RFUI
- Log On to 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 SAP Easy Access screen 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 )
WO query ( 03 WO Query )
By WO ( 01 WO Query by WO )
By warehouse task ( 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.
2. 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.
3. 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.
4. Specify a line number for an 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.
2. The system displays the corresponding products and their quantities.
3. If necessary, display the detailed storage bin data.
4. Enter a line number. The system displays the stock details.
Stock query by product
1. Scan the product.
2. The system displays the corresponding storage bins and their quantities.
3. If necessary, display the detailed product data or sort the storage bins by stocks in descending order.
4. Enter a line number. The system displays the storage bin details.
PUBLIC
Page 19 of 29
WO query by WO, WT, or queue
1. Depending on the menu option that was selected first, you scan the WO, the WT, or the queue.
2. 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 confirmed WTs, or you can display all WTs.
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.
3. The system displays the relevant WTs.
4. If necessary, display the detailed WT data. Additionally, you can restrict the WT display to open WTs or confirmed 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 first 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 RF environment. On the SAP Easy Access screen, you choose Extended Warehouse Management Execution
/SCWM/RFUI - Log On to 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 defined it within the resource group. To do so, on the SAP Easy Access screen, choose Extended
Warehouse Management Master Data Resource Management Maintain Queue Sequence for 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 environment (RF environment).
Prerequisites
You have logged on in the RF environment. On the SAP Easy Access screen, you choose Extended Warehouse Management Execution /SCWM/RFUI
- Log On to 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).
Features
You can enter a difference quantity for an 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 confirmed last, and an exception code.
2. 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.
3. 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.
4. Specify a line number for an 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.
5. Specify the quantity difference for an HU at product detail level and book it out.
PUBLIC
Page 20 of 29

1.4.16 Optimization Functions of the RF Execution

You can optimize the execution in your RF environment by using the following functions:
Interleaving Using Radio Frequency
Semi-System-Guided Processing
Resource Execution Constraints (REC) Using Radio Frequency
1.4.16.1 Interleaving Using Radio Frequency

This function allows you to optimize the utilization of your resources in an RF environment by reducing the travel times in the warehouse. The aim of this function is
to minimize unutilized 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 find 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 queue, based on the defined
queue sequence.
2. The next queue is processed according to the defined queue sequence.
Integration
This function is only available within system-guided processing.
Prerequisites
Define the queue type.
In Customizing for Extended Warehouse Management , choose Cross-Process Settings Resource Management Define Queue Type.
Define the queue sequence. By doing this, you define the processing sequencing of the warehouse tasks.
On the SAP Easy Access screen, choose Extended Warehouse Management Master Data Resource Management Maintain Queue Sequence
for Resource Group.
Assign the queue to a queue type.
In Customizing for Extended Warehouse Management , choose Cross-Process Settings Resource Management Define Queues.
You can exclude queues from the queue sequence.
On the SAP Easy Access screen, choose Extended Warehouse Management Master Data Resource Management Maintain Queue Sequence
for Resource Group.
You can exclude resource types.
In Customizing for Extended Warehouse Management , choose Cross-Process Settings Resource Management Define Resource Types.
1.4.16.2 Semi-System-Guided Processing Using Radio
Frequency

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 field is empty. The user can scan it.
After scanning, the system checks whether:
The scanned HU is available in the specified storage bin
An open warehouse task exists for this HU
The reported resource is allowed to process the HU
System-guided processing Semi-system-guided processing
The screen shows you various data, such as HU, product, quantity, batch, and so on. You only see the source storage bin and the input field for the HU.
Warehouse task is locked Warehouse task is not locked, as it is still not clear which HU is being selected
PUBLIC
Page 21 of 29
Integration
Activating this function affects the system behavior of the system-guided processing that is preconfigured in the standard system.
Prerequisites
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 Define 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.
1.4.16.3 Resource Execution Constraints (REC) Using Radio
Frequency

This function allows you to control the number of permitted work resources in defined areas of your warehouse. You define 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. Define the maximum number of
permitted work resources for these REC storage groups in such a way that the resources can perform your work without disruption.
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 define whether:
Only 1 resource type is allowed to be kept in the REC storage group at a time (parameter OR).
Multiple different resource types are allowed to be kept in the REC storage group at a time, for example fork lift and warehouse worker. For each resource
type, the maximum defined 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.
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 defined resource types and a speed for these types.
In Customizing for Extended Warehouse Management , choose Cross-Process Settings Resource Management Define Resource Types.
2. You have defined resources, and assigned these to resource types.
On the SAP Easy Access screen, choose Extended Warehouse Management Master Data Resource Management Maintain Resource.
3. Since the system calculates the working times using the travel distance calculation, you need to have defined a node for each activity. You need to have
assigned these nodes to aisles.
On the SAP Easy Access screen, choose Extended Warehouse Management Settings Travel Distance Calculation Settings for the Travel
Distance Calculation .
PUBLIC
Page 22 of 29
4. You have defined resource execution constraints (RECs).
In Customizing for Extended Warehouse Management , choose Cross-Process Settings Resource Management Control Data Define Resource
Execution Constraints (REC).
5. You have assigned an REC storage group to the storage bins.
On the SAP Easy Access screen, choose Extended Warehouse Management Master Data Storage Bin Create Storage Bin/Change Storage
Bin/Mass Change to Storage Bins .
6. The function works using the average confirmation 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 define the bin access type for the REC storage group, in the master data. You must also define the
extract time determination for storage bins.
In Customizing for Extended Warehouse Management , choose Cross-Process Settings Warehouse Task Define Extract Time Determination.
1.5 Enhancement Screen Wizard
Use
In the Enhancement Trigger dialog box, you can choose this option to add or remove fields 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 fields from the screen, the wizard generates an updated screen.
The wizard displays a field catalogue from which you can choose the required fields that you want to display on the screen. The field catalogue displays fields
from the corresponding screen structure.
You can also choose a field 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 specific group of users. If
you want to see the new screen, enter the personalization profile.
The new screen is displayed in Screen Painter , where you can adjust aspects of the screen layout, such as position and field size.
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 fields that can be
added to an RF screen.
We recommend that you first consider how many fields are required and whether they fit into the target screen.

Example
The figure below explains how to run the Enhancement Screen Wizard:

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 fields across several new
screens.

PUBLIC
Page 23 of 29
Features
As you go through the process of splitting the radio frequency (RF) screen, into multiple screens, the wizard does the following:
Displays a field catalogue comprising existing fields from the current screen.
You can assign a new screen to each of the fields. You should also specify the screen programs and numbers for each new screen.
Displays the screens based on your preferred sequence.
Enables you to configure 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 specified group
of users. If you want to see the new screen, enter the personalization profile.
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 fields that can be
added to an RF screen.
We recommend that you first think about how many fields are required and whether they fit into the target screen.

Example
The figure below explains the steps to run the 1.6 Split Screen Wizard:

1.7 Pick by Voice

The pick by voice (PbV) functionality in SAP Extended Warehouse Management (EWM) supports voice-based picking and internal moves in the warehouse,
independently of the RF Picking transaction. It is based on the radio frequency (RF) framework, the RF picking transaction and the ITS template generator Mobile
Devices with Speech Input . It supports barcode scanning and voice-enabling.
The pick by voice transaction uses SAPGUI dynpros whose fields have speech properties. From these dynpros, the system generates HTML templates using
the ITS HTML template generator Mobile Device with Speech Input . These HTML templates contain speech-specific tags which are interpreted by the web
browsers on the device.
The following dynpro field speech attributes are supported.
Attribute Description
Prompt Text Text to prompt input for a field, 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 fit to the grammar.
Grammar Simple grammar for identifying the speech input of a given value.
GrammerLnk Complex grammar, loaded as an external file, 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 Specifies the next field with speech input.
The system interprets speech input either as a field input value or as a command. All possible commands must be visible on the screen and represented by a
pushbutton. The RF framework supports up to 16 pushbuttons. You cannot assign commands to function keys.
To trigger a command, you must switch to command mode by saying the built-in keyword Command. Alternatively, the system automatically goes into command
mode if you make entries in all input fields.
Using the command Okay is equivalent to pressing Enter .
The transaction uses the field properties PromptText , HelpText , FilledText , Grammar , and GrammarLnk . A screen can contain up to ten prompt texts,
PUBLIC
Page 24 of 29
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 PbV transaction directly. This
transaction is not part of the SAP Easy Access screen. The Internet Communication Framework (ICF) service RFUI_PBV is linked to this start transaction.
You can use the Business Add-In (BAdI) Modify Screen Field Voice Properties to change the voice properties of a screen and its fields 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
1.7.1 RF Framework for Pick by Voice

The radio frequency (RF) framework for pick by voice uses the display profile *1 . This display profile 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
Pushbutton Text Length PUSHB_LEN 40
Number of Pushbuttons Available on the Screen PUSHB_QTY 16
Menu Item and Logical Transaction Text Length MENU_LEN 40
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 Program TMPL_MSG_PROGR /SCWM/SAPLRF_TMPL
Template (with Message Line) Screen Number TMPL_MSG_NUM 0002
Template Screen Title Program TMPL_TITL_PROGR
Template Screen Title Number TMPL_TITL_NUM
Text TEXT Pick-by-Voice
The field Data Entry in the presentation device has an additional fixed value 1 Voice recognition . The data entry controls the PbV-specific functionality,
such as setting the prompt text.
The main menu PBV contains the logical transaction PVSYSG.
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 profile **** has an additional personalization profile *1 . This personalization profile contains the main menu PBV .
Prerequisites
You have entered 1 in the Data Entry field and *1 in the Displ.Prof field in the presentation device. You do this on the SAP Easy Access screen under
Extended Warehouse Management Master Data Maintain Presentation Device . You should also leave the Shortcut field here blank.
In the RF user settings, you have entered *1 in the Prsn.Prof. field. You do this on the SAP Easy Access screen under Extended Warehouse
Management Master Data Resource Management Maintain Users .
More Information
Radio Frequency Framework
1.7.2 Standard RF Functionalities in Pick by Voice

The radio frequency (RF) framework supports standard RF functionalities, including the following:
Logon
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 fields with
the user's data. If the screen is not skipped, the system populates the fields with the values maintained in master data for the user. If the screen is skipped,
the system speaks a message such as 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 Define Reasons for Warehouse Movements . If warehouse orders are
still assigned to the user, the system informs of 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.
PUBLIC
Page 25 of 29
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 speaks Select menu via command to the user.
If the menu contains more entries than will fit on one page, the system speaks 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 field. 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
1.7.3 Working with RF for Pick by Voice

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 fields 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 Verification 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-HUs. The user can confirm 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.
2. Source storage bin for product WT (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, this step is repeated until all tasks are picked.
The user is guided to the source storage bin and must enter the verification value of the storage bin master. In the standard setup, the product is not
validated. For the stack, the validation is either the value or the verification 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 which 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 which has to be put away. If the
user has more pick-HUs to put away in different destinations, this step is repeated 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 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; the user
can place the HUs in one step.
The following screens are also voice-enabled:
Source storage bin for HU WT
Guides the user to the correct source storage bin to take the HU.
Destination storage bin for product WT
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 realises that the proposed destination storage bin is full or cannot be reached, and enters a new storage bin or lets the system propose a new
storage bin.
Semi-system guided picking
The system identifies 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 specific verification logic for the HU. To avoid the user having to speak 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 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 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 level, the validation field of the storage bin master is used. The system only tells
the user the difference between the storage bins of the previous WT and the current WT, 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 speaks the entire
storage bin to the user.
PUBLIC
Page 26 of 29
More Information
Exceptions
1.7.3.1 Exceptions

The list of valid exceptions depends on the type of warehouse task (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 Confirm Warehouse Task (Intern. Movemnt) and TPI Confirm 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)
Product warehouse task on source storage bin (Step P3)
NEXT Continue
SPLT WT Split
Product warehouse task on destination storage bin (Step P4)
CHBD Change Destin. Storage Bin (Location)
SPLT WT Split
The following internal exceptions allow you to directly trigger exceptions with pushbuttons 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 RF warehouse task confirmation:
RF01 Error during WT confirmation in RF
RF02 Error during WT creation in RF
For all the internal exceptions, you must define exceptions for execution step Data Verification in Background . You do this in Customizing for Extended
Warehouse Management under Cross-Process Settings Exception Handling Define Exception Codes .
The exception NEXT only works for the same step. This means that at the end of the WT list for the source step, it is not automatically changed to the destination
step. The system speaks the message 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 pushbutton or command Pick Denial is triggered. If the
quantity field is empty, the system assumes there is a full pick denial and triggers the internal exception BIDF . If the quantity field is not empty, the system
assumes there is a partial pick denial and triggers the internal exception BIDP .
The pushbutton Difference 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
1.7.3.2 Improving Performance

PUBLIC
Page 27 of 29
Switch Off Printing
Warehouse task (WT) printing and handling unit (HU) printing are called during WT creation and WT confirmation. The function modules call the Post Processing
Framework (PPF) which reads the relevant Customizing and calls the schedule condition for all active PPF actions. The schedule condition checks whether the
warehouse process type or the packaging material type has a determination procedure from the assigned condition technique. If there is one, the condition
technique is called, and based on the result the system determines whether or not to print.
If you know that you will never use printing as part of this process, you can control whether or not the PPF is called.
The queue has a field (QUEUE_PRINT) for setting up printing during WT creation and confirmation. The field has the following possible values:
' ' call PPF
1 do not call PPF
You can change the value of this field in Customizing for Extended Warehouse Management under Cross-Process Settings Resource Management
Define Queues .
The resource has a similar field (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 field on the SAP Easy Access screen under Extended Warehouse Management Master Data Resource Management
Maintain Resource .
Create Pick-HU Warehouse Tasks Asynchronously
The system creates the pick-HU WT from the resource to the destination bin when confirming the first pick WT into the HU. To improve the response time of the
WT confirmation step, this is carried out asynchronously in an RFC queue. The queue name consists of the prefix WMTR followed by the HU number.
The asynchronous warehouse task creation can fail if, for example, the destination bin for the pick-HU is blocked. For more information, see Error Handling.
1.7.3.3 Error Handling

If errors occur during warehouse task (WT) confirmation, the system sends the pick-HU to a dedicated clarification bin so that the error can be analyzed and
resolved. The picker can follow the guidance of the pick by voice system. You can specify a clarification bin for each activity area and activity on the SAP Easy
Access screen under Extended Warehouse Management Master Data Storage Bin Assign Start/End Storage Bin for Activity Area or by entering the
transaction code /SCWM/SEBA.
The following error scenarios are possible:
The confirmation of the pick WT from the source bin to the destination bin fails.
This can happen if, for example, the Customizing settings for the storage type allow the available quantity to be a negative value. Thus a WT can be
created with a quantity which exceeds the quantity actually available in the bin. However, the WT cannot be confirmed during picking if the available
quantity on the bin has not increased. The pick WT stays open but is no longer assigned to a picker for processing, and the pick HU is sent to the
clarification bin. If a pick-HU WT to the original destination already exists, it is canceled and a new one to the clarification bin is created.
The asynchronous creation of the pick-HU warehouse task fails.
This can happen if, for example, the destination bin of the pick-HU is blocked. In this case the RFC queue contains an entry for the HU which cannot be
processed. The system creates a WT with the clarification bin as its destination, and deletes the entry from the queue. WTs to the clarification bin are
always created synchronously, to ensure stable error handling.
Note
The clarification bin should not be located in a a storage type with the role staging area. If it is, the staging area of the outbound delivery item referenced
by the WT is set to the clarification bin. This is done because the delivery is updated with the current WT data during WT confirmation.
If the WT confirmation aborts with an error, the system moves the pick-HU to the clarification storage bin for further processing. The WT is marked internally as
faulty, and stays open but is not assigned to a picker for processing any more.
Warehouse Order Split
If a picker leaves the picking transaction while some WTs of the processed warehouse order (WO) are still open, he can send the remaining WTs back to the
queue so a different picker can process them. The WO is then split, so the open WTs are moved to a new WO. This also happens if you delete the assignment of
a WO to a resource in the warehouse management monitor.
WTs that are still open due to an error remain in the original WO, as they have already been processed. This means that the erroneous WTs remain assigned to
the picker that actually processed them.
Exception Codes
If an error occurs during WT confirmation, an internal exception code is raised. The following internal exception codes are available for pick by voice:
RF01 - Error during WT confirmation in RF
This exception code is raised if the confirmation of a pick WT from the source bin to the resource fails.
RF02 - Error during WT creation in RF
This exception code is raised if the confirmation of the pick-HU WT from the resource to the destination bin fails.
By assigning an exception code to the internal exception code, an alert can be triggered in order to inform the worker responsible for checking the HUs on the
clarification bin. The exception code must be valid for the business context TPI Confirm Warehouse Task (Stock Removal) with the execution step A0 Data
Verification in Background which is used for exceptions triggered by the system.
There is a warehouse management monitor node available to display the alerts. In the standard SAP monitor it is located under Alert Exception . From this
node you can also navigate to the faulty WO using the monitor method Display WO of WT . Here you can confirm WTs 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 option With History for your exception code.
PUBLIC
Page 28 of 29
Clearing Errors
When a pick-HU is rerouted to the clarification bin, you have to check the HU, confirm any pick WTs 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 clarification bin, you must first use the monitor node Alert Exception to identify the erroneous
warehouse order. You can check here whether some of the pick WTs are still open. If multiple pick-HUs were sent to the clarification bin, you first have to check
which one the product of the WT was picked into. As the remaining WTs could not be confirmed, they still point to the original destination and not to the pick-HU.
When you have matched the WTs that are still open with the correct HUs, confirm the WTs in the foreground and change their destination to the appropriate pick-
HU.
After you finish processing a HU in the clarification bin, you must create an ad-hoc WT to the HU's original destination. You can do this with the transaction Move
Handling Unit (/SCWM/ADHU) which you can find on the SAP Easy Access screen under Extended Warehouse Management Work Scheduling Create
Warehouse Task Without Reference .
More Information
Exceptions
Improving Performance
PUBLIC
Page 29 of 29

SAP Radio Frequence Framework

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Radio Frequence Framework

Uploaded by

Copyright:

Available Formats

Radio Frequency Framework

PDF download from SAP Help Portal:

You might also like