Warehouse Management System (WMS)

4/24/2022
Warehouse Management System (WMS)

Generated on: 2022-04-24 06:08:56 GMT+0000
SAP ERP Support Package Versions | 6.0 EHP7 SP17
PUBLIC
Original content: https://help.sap.com/docs/SAP_ERP_SPV/34fc810a607e4ae5a287b6e233b8566f?locale=en-

US&state=PRODUCTION&version=6.17.17
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/docs/disclaimer.
This is custom documentation. For more information, please visit the SAP Help Portal 1
4/24/2022
Mobile Data Entry (LE-MOB)
Purpose
Currently, the work process in the warehouse is characterized by speed, reliability, and precision in processing individual goods
movements. To make sure that work is performed efficiently and at a reasonable cost, the warehouse staff requires simple and
easy-to-view control of each individual process. The radio frequency (RF) solution provides fast and error-free data
communication through the use of mobile RF terminals. This, in turn, provides a high standard of quality.
The RF terminals receive data directly from the SAP System and transmit the results back to the system. You can scan the
information that needs to be recorded, such as handling unit (HU)numbers, using a bar code (for example, based on
UCC/EAN128 standards), and also scan the bar code to verify the storage bins.
The display of information on the RF terminal is possible with a graphical user interface. You can execute the individual functions
using pushbuttons on a touch screen. If you are using a character-based device, SAP provides a special, non-graphic user
interface.
Since the RF solution is an integral part of the standard SAP System, you can access the RF transactions either directly through
the SAP menu or from mobile data-entry devices. Generated information is immediately available to the RF user and
transmitted back to the SAP database instantly.
Integration
Mobile Data Entry is integrated with SAP’s Warehouse Management System (WMS) and Task and Resource Management
(TRM) .
Warehouse Management System (WMS)
The RF solution supports the movement of goods in both HU-managed and non HU-managed storage locations.
In HU-managed storage locations, the RF solution supports the movement of goods through the speci cation of the
respective handling units.
In non HU-managed storage locations, you can work with handling units as up to now in the delivery and in the shipment.
For more information, see Handling Unit Management .
Task and Resource Management (TRM)
TRM itself supports the customization of data presentation on RF devices. As part of this customization, you can include Mobile
Data Entry menus and functions. For more information, see Presentation Management in the SAP Library for Task and
Resource Management .
Features
Mobile Data Entry provides a number of features, including the following:
GUI and Character Device Support
Mobile Data Entry supports both GUI and character-based devices. For more information, see RF Device Support .
Bar Code Support
4/24/2022
Mobile Data Entry supports the use of bar codes for identi cation and veri cation purposes. For more information, see Bar
Code Support .
RF Support of Warehouse Management Processes
Mobile Data Entry supports a wide variety of warehouse processes, including:
Goods receipts and issues
Picking
Putaway
Interleaving
Inventory counting
Loading and unloading
The RF solution guides the user through each activity that is executed in the warehouse. Limited information is displayed to the
users, which they must then verify by scanning bar codes. For more information, see RF-Supported Warehouse Processes .
RF Activity Control
Mobile Data Entry supports the assignment of transfer orders to queues, according to physical areas of the warehouse and
activities. The TOs can then be processed by users assigned to those queues.
The warehouse manager can utilize the RF Monitor , which operates as a central coordination point to ensure that the
processing of transfer orders runs as efficiently as possible. For more information, see RF Queue Management .
Flexible RF Customizing
In Customizing for Mobile Data Entry , you can de ne the following:
The size and number of screens
Menus and menu sequences
Fields to be veri ed
Bar code types and Application Identi ers
Use of the Enter function
For more information, see the IMG for Logistics Execution MobileData Entry.
RF Device Support
Use
Mobile Data Entry supports both GUI and character-based devices.
RF devices utilize the standard SAPGui (GUI = Graphical User Interface) screen management environment to interact with
users. The screens are designed for normal device functions, such as the use of pushbuttons and reduced screen size.
Currently, two device types are supported:
1. GUI devices (with graphical user interface) that run on Windows 3.x/95/98
4/24/2022
2. Character devices (character-based) under terminal emulation mode
 Note
The same set of screens is used by the GUI and character-based environments.
GUI Devices
These devices are connected to the SAP System just like any other client-dependent PC. The screens can be touch screens,
using prede ned pushbuttons, or they can operate 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.
System fonts and size should correspond to the guidelines provided in order to achieve optimal utilization of the screen size.
Character-Based Devices
These devices are linked to the system through an SAP standard interface called the SAPConsole. The SAPConsole operates on
a Windows NT/Windows 2000 platform and interacts with the RF terminals connected to it. This concept is currently supported
by the leading providers of RF terminals.
The actual communication between the SAPConsole and the terminals can be achieved either through the use of a standard
Telnet server or through an optimized server that is provided by the RF terminal vendor. The speci c I/O engines are integrated
into the SAPConsole, which is based on the COM technology.
The following two industry standards for screen sizes are supported:
1. Devices for forklifts: 8 lines by 40 characters each
2. Portable handheld devices: 16 lines by 20 characters each
In addition, with user exits , you can de ne user-speci c display sizes that allow every device type to be supported.
With all device types, navigation takes place through function codes that have to be de ned on the keyboard.
RF Device Basic Functions
Use
Due to the character mode of the RF devices, pushbuttons must be used for all available functions. You should set up the RF
device so that it corresponds to the standard function keys.
The standard layout of the RF screens is designed in such a way that the pushbuttons for the key functions are located in the
upper half of the screen, while additional pushbuttons are set in the lower half of the screen.
 Note
You can customize the pushbutton texts in Customizing for Logistics Execution MobileData Entry De ne Menu
Management.
Features
Pushbutton Function
4/24/2022
Pushbutton Function
Back Returns you to previous screen
Clr Clears from the screen the current input eld or all input elds
Det Displays detailed information for a speci c item
Enter Checks veri cation elds
 Note
You can replace up to ve pushbuttons in a sequence with one
click of Enter . For more information, see the IMG for Logistics
Execution MobileData Entry Default Enter Function
(Navigation With Bar Code Scanner).
LOff Enables you to log off from the RF device
More Displays additional available pushbuttons/functions
Nxt Navigates you to the next screen
OK Con rms a message and leaves the screen
PgUp ( ) / PgDn ( ) Displays the previous or next item
Save Con rms the step
Yes/No Answers a message
Pushbutton Function Process Where Used
AllHU Enables you to either pick an entire HU Pick and Pack – Nested Handling Units
(take-over), or, if the HU is already marked
for take-over, change the pick quantity of
material in the HU
APM Enables you to select auxiliary packaging Packing

material
BnEm Marks a storage bin as being empty. Inventory Counting
ByMt Enables you to pack/unpack material Packing and Unpacking

into/from HUs
Chk Calculates difference quantity when Goods Receipt

reporting differences
Putaway
Picking (except for Bulk Picking)
Interleaving
Movement by SU
Posting Changes
4/24/2022
Conf Con rms a difference Goods Receipt
Putaway
Picking
Interleaving
Movement by SU
Posting Changes
Diff Enables you to report quantity differences Goods Receipt
Putaway
Picking
Interleaving
Movement by SU
Posting Changes
DlSU Deletes a SU from the Selected Storage Inventory Counting

Units list.
DelHU Deletes an HU from the Selected Handling Pick and Pack – Nested Handling Units
Units list.
EndCnf Ends con rmation after the picking, from Picking from Bulk
bulk storage, of a quantity that is less than
Interleaving
TO quantity
Movement by SU
G.TO Creates a TO for a delivery. Goods Receipt
Goods Issue
GRDt Sorts by goods receipt date Stock Overview Inquiry
HU V Displays information on any lower-level HUs HU Inquiry
HU.D Displays additional information on a HU HU Inquiry
Packing and Unpacking
Items Displays information on the items of a Goods Receipt

delivery.
Goods Issue
LdUn Enables you to load/unload a delivery Goods Receipt
Goods Issue
MatV Displays information on a material HU Inquiry
Mt.D Displays information on a material Packing and Unpacking
NBin Changes the destination bin for a single- Putaway

step con rmation TO during con rmation
Interleaving
Movement by SU
Nest Displays information on the lower-level HUs Pick and Pack – Nested Handling Units
of a nested HU
4/24/2022
NSU Adds further SUs to the selected SU list Clustered Putaway
NwIt Enables you to add a new quant to a storage Inventory Counting

unit/bin.
Pack/Unpck Enables you to packs/unpack delivery Goods Receipt

items.
Goods Issue
Post Posts goods to Inventory Management Goods Receipt

(IM).
Goods Issue
PrHU Prints a handling unit label HU Inquiry
PrSh Prints a shipping unit label Goods Receipt
Goods Issue
HU Inquiry
Prt. Prints a label Pick and Pack
Loading and Unloading
SBn Sorts by storage bin Stock Overview Inquiry
Sel Marks delivery items as having been Goods Receipt

checked
Shipmt Displays information on the shipment to Goods Receipt

which a delivery is assigned
Goods Issue
SLED Sorts by shelf life expiration date Stock Overview Inquiry
Split Enables you to split an outbound delivery Goods Issue
TOex Enables you to con rm a TO for a delivery. Goods Receipt
Goods Issue
Undo Unloads a recently loaded HU or loads a Loading and Unloading

recently unloaded HU
WM V Displays information on the storage unit, the HU Inquiry

warehouse number, the storage type, and
the storage bin
ZeroSt Sets to zero the quantity of a particular Inventory Counting

material in a storage unit/bin.
Bar Code Support
Use
Mobile Data Entry supports the use of bar codes for identi cation and veri cation purposes.
1. Identi cation
You scan bar codes , printed on transfer orders and other container documents, to identify:
4/24/2022
Storage bin
Material
Quantity
Delivery
Staging area
Shipment
Pick wave
Handling unit
Storage Unit
1. Veri cation
You scan bar codes to verify information of the following elds:
Storage unit
Material
Quantity
Storage bin
Other elds determined in a user exit
Prerequisites
You have done the following:
1. In Customizing for Mobile Data Entry Veri cation Control De ne Pro les , de ned a veri cation pro le and the
respective elds that are to be veri ed.
2. In Customizing for Mobile Data Entry Veri cation Control Assign Veri cation Pro les to Goods Movements ,
determined for which warehouse, storage types and movement type your veri cation pro le is valid.
3. In Customizing for Mobile Data Entry Bar Code Assign Bar Code Types to Warehouse Numbers , de ned which bar
code is supported in your warehouse to identify goods.
4. In Customizing for Mobile Data Entry Bar Code Maintain Bar Code Speci cation , maintained the structure of the bar
code types.
5. In Customizing for Mobile Data Entry Bar Code Assign Bar Code Types to Warehouse Numbers , de ned by which bar
code standard the elds are to be veri ed.
6. In Customizing for Mobile Data Entry Bar Code Maintain Bar Code Speci cation , de ned the structure of the bar
code types
RF Queue Management
Purpose
The de nition and management of queues, as well as the assignment of activities and users to queues, ensures that transfer
order processing is run as efficiently as possible.
4/24/2022
Process Flow
 Note
For more information on de ning queues, assigning areas and activities to queues and assigning processors to queues, see
the IMG for Mobile Data Entry RF Queue Management.
For more information on monitoring queues and coordinating TO processing, see RF Monitor .
RF Monitor
Use
The RF monitor is a tool for central, cross- queue monitoring and coordination of transfer order (TO) processing.
Each RF user is assigned to a queue in Customizing for Mobile Data Entry . This assignment can be viewed and changed using
the RF monitor.
The user's view at the RF terminal is limited to the transfer orders of its current queue. The RF monitor operates as a central
coordination point, ensuring that TO processing is run as efficiently as possible.
Prerequisites
You have done the following in Customizing for Logistics Execution Mobile Data Entry RF Queue Management:
De ned queues
Assigned areas and activities to queues
Assigned processors to queues
Features
4/24/2022
Using the RF monitor, an authorized RF user can do the following:
Monitor queues, including the number of assigned TOs, number of users and ratio of workload to users
Assign TOs and users to other queues
Change the processing priorities of TOs
RF Monitor User Interface

The RF monitor has a user-friendly interface which utilizes Drag&Drop functionality. The interface comprises of the following
areas:
Navigation area
ALV (SAP List Viewer) area
Navigation Area
The navigation area, located on the left side of the monitor, is a navigation area consisting of the various queues, assigned TOs
and users (agents). The navigation area also displays the following queue attributes:
1. Total number of TOs
2. Total number of agents
3. Proportion
The proportion signi es the workload for agents/users and is calculated by dividing the number of TOs by the number of
agents. The traffic lights represent the workload situation:
Green – the proportion is less than or equal to the lower threshold
Yellow (warning) –the proportion is greater than the lower threshold
Red (critical) – the proportion is greater than the upper threshold
 Note
You de ne the lower and upper thresholds in Customizing for Logistics Execution Mobile Data Entry RF Queue
Management De ne Queues.
Using the navigation area, you can also assign TOs and agents to queues, as well as forward TOs to other queues.
ALV
The ALV, located on the right side of the monitor, contains elds of TO and user records for a particular queue. You can also
change the processing priorities of TOs from the ALV.
This area is synchronized with the navigation area.
See Also:
Using Basic RF Monitor Functions
Using Basic RF Monitor Functions

4/24/2022
To access the individual functions shown in the table, from the SAP Easy Access menu, choose Logistics Logistics
Execution Internal Whse Processes Monitor Mobile Data Entry.
The RF monitor opens, displaying the following:
In the navigation area, all queues and their attributes
In the ALV, all TOs and users
Function Procedure Result
Changing the warehouse being monitored The RF monitor’s display is updated, with
1. From the top menu, choose
the monitor now displaying queues for
Edit Other warehouse number .
the chosen warehouse.
The RF Monitor dialog box
appears.
2. Enter the new warehouse number.
3. Choose Enter .
Resizing the navigation area and ALV Drag the horizontal and vertical split The areas are resized accordingly.
bars.
Displaying in the navigation area TOs, The folder expands, revealing the
1. From the navigation area, choose
agents and queues assigned to a queue TOs/agents.
Expand next to the queueʻs
folder.
The folder node expands,

revealing the TO, queue and
agent sub-folders (if any are
assigned to the queue).
2. To display the TO/agent objects,

choose Expand next to the
TO/agent folder.
Displaying in the ALV the records of From the navigation area, double-click a The TOs, as well as any logged on users,
TOs/users of a queue queue folder. assigned to the queue are displayed in
the ALV.
Assigning TOs/users to a different queue The TO/agent is reassigned to the

1. From the navigation area, select
destination queue.
the particular TO or agent that
you want to re-assign.
2. Drag it down to the destination

queue folder.
 Note
An RF user can also re-assign
itself to a different queue by
choosing Internal Warehouse
Processes Queue Change
from the RF menu, entering
the name of the destination
queue and choosing Save.
4/24/2022
Forwarding TOs to another queue The source queue now appears below the
1. From the navigation area, select a
destination queue.
queue (source queue)
Users can process TOs from the source
2. Drag it down to the destination
queue, even though they are assigned to
queue folder.
the destination queue, despite any
access limitations de ned for the source
queue.
In a system-guided transaction, the TOs

of the source queue are automatically
forwarded to the RF user assigned to the
destination queue, after it has processed
all TOs in its queue.
Changing the processing priority of a TO The TO priority either increases or

1. From the ALV, select a line
decreases, depending on whether the
corresponding to a TO.
priority of the destination TO is greater
2. The line is highlighted. than or less than the priority of this TO.
3. Drag the line either up or down

and drop it on the line of a TO
with a different priority.
Refreshing the display First Option The display of the monitor is updated.
Perform an operation, such as

reassignment of TO/user or changing the
priority of a TO.
Second Option
From the RF monitor tool bar, choose

Refresh.
Third Option
From the top menu, choose

Edit Refresh.
Reversing an operation First Option The last performed operation is

reversed.
From the RF monitor tool bar, choose
Discard.
Second Option
From the top menu, choose Edit Undo .
RF- Supported Warehouse Processes

The Mobile Data Entry RF solution supports the following warehouse processes:
Goods receipt
Goods issue
Putaway
Picking/replenishment
4/24/2022
Interleaving
Packing and unpacking
Inventory counting
Loading and unloading
Serial number capture
Inquiries
Movement by storage unit
Posting changes
 Note
In order to perform the functions associated with each of these processes, you must rst log on using your RF device.
To log on, choose Logistics Logistics Execution Internal Whse Processes Mobile Data Entry Mobile Data Entry
from the SAP Easy Access menu.
Goods Receipt
Use
Mobile Data Entry supports the goods receipt process. Using their RF devices, warehouse workers can perform the following
goods receipt-related functions:
Check all delivery items and report differences
View and change shipment information
Print shipping unit labels
Unload deliveries
Pack/unpack delivery items
Generate and con rm TOs for delivery items
Post goods receipts to Inventory Management
Prerequisites
The goods receipt is based on an inbound delivery.
Features
You can perform goods receipts for inbound deliveries identi ed by:
Delivery number
Handling unit (HU) number
Staging area
Shipment number
4/24/2022
Other criteria
Performing a Goods Receipt
Use
Using an RF device, you can perform a goods receipt for an inbound delivery identi ed by one of the following:
Delivery number
Handling unit number (if HU already exists and is assigned to an inbound delivery)
Staging area
Shipment number
Other criteria
 Recommendation
We recommend that you use the staging area selection method only when you cannot identify deliveries by any of the other
criteria, since this method is time consuming.
Procedure
4/24/2022
GR for Delivery Identi ed by:
Delivery Number HU Number Staging Area Shipment Number Other Criteria
1 From the RF menu, From the RF menu, From the RF menu, From the RF menu, From the RF menu,
choose Inbound choose Inbound choose Inbound choose Inbound choose Inbound
Process Goods Process Goods Process Goods Process Goods Process Goods
Receipt GR by Receipt GR by Receipt GR by Receipt GR by Receipt GR by
Delivery . Handling Unit . Staging Area . Shipment . Others. .
The Select Delivery The Select Storage The Select Delivery The Select Delivery The Select Delivery
screen appears. Unit/Handling by Staging Area by Shipmentscreen by Others screen
Unitscreen appears. screen appears. appears. appears.
2 Enter the delivery Enter the handling Enter the staging Enter the shipment Enter one or more of
number using the unit number using area. number using the the following
scanner or the scanner or scanner or criteria:
keyboard. keyboard. keyboard.
Material
Vendor
Delivery
date
External
delivery
reference
Service
agent
3 Choose Nxt. The Delivery Header Information screen appears, displaying the following information for the
delivery:
Load/unload status
Vendor account number
Vendor name
Shipping point and shipping date
Total weight of goods delivered
Number of packages
HU indicator indicating whether or not a HU exists for the delivery
TO indicator indicating whether or not a TO exists for the delivery
4 You can scroll between deliveries by choosing PgUp ( ) / PgDn ( ) (applies to deliveries identi ed by staging area,
shipment number or other criteria only)
5 Choose Items. The Delivery Item Information screen appears, displaying the following information:
Delivery information, including total number of items in delivery and number of items con rmed
Material information, including material name, special stock number, quantity and batch number
6 Scroll between the delivery items by choosing PgUp ( ) / PgDn ( ).
4/24/2022
7 If the received quantity of a material is not equal to the TO quantity, report the difference by doing the following:
1. Choose Diff. The Differences screen appears.
2. Enter the actual quantity in the relevant eld and choose Chk. The difference quantity is automatically
calculated.
3. Choose Conf to con rm the reported difference. You return to the Delivery Item Information screen. The
item is now marked as having been checked and is added to the total of con rmed items as displayed in
the Conf. eld.
 Note
If you did not choose Chk in the Differences screen, you can now choose Sel to mark the item as having been
checked and update the Conf. eld.
8 To view or change information on the corresponding shipment:
1. Choose Shipmt. The Shipment Information screen appears, displaying the shipment number, external ID,
container ID, shipment type and shipment route.
2. To manually change the unloading start date and time or unloading end date and time, enter the data in the
relevant elds and choose Save.
3. When you commence the unload process selected by shipment, the start date and time are automatically
updated. The end date and time are automatically updated when unloading the last HU.
4. To print a shipping unit label, choose PrSh.
9 To unload the delivery:
1. Choose LdUn. The Load/Unload by Delivery screen appears.
2. Follow steps 2 onwards in Performing Loading/Unloading(Load/Unload by Delivery).
10 To pack or unpack delivery items:
1. Choose More and then Pack or Unpck. The Pack/Unpack screen appears, displaying the status of
Packing or Unpacking.
2. Follow steps 2 onwards in Packing or Unpacking.
11 If a TO does not exist for some or all of the items in the delivery, choose G.TO. to generate a TO for the items
without a TO.
 Note
If the delivery contains batch-managed material, the batch number must be entered in the delivery in order to
generate a transfer order.
12 To con rm the TOs for the delivery:
1. Choose TOex. The Source Information screen appears.
2. Follow steps 3 onwards in Performing a Putaway.
4/24/2022
13 To post the goods in Inventory Management:
1. Choose Post. A message appears.
2. ChooseYes to post the goods.
 Note
Generally speaking, the TO must be con rmed before executing the posting.
You can determine that the delivery is posted before TO creation and con rmation in Customizing for Logistics
General Handling Unit Management Basics Delivery De ne Sequence of Transfer Order – Goods
Receipt.
You can also determine that the delivery is automatically posted when all of the delivery items are processed in
Customizing for Logistics Execution Warehouse Management Interfaces Shipping De ne Shipping
Control De ne Shipping Control at the Movement Type Level. Enter 2 in the Copy WM quantity eld.
You can also set the system for partial posting of deliveries (data for a speci c delivery item, whose TOs are
completed, is posted) in Customizing for Logistics Execution Warehouse Management Interfaces
Shipping De ne Shipping Control De ne Shipping Control at the Movement Type Level. Enter 4 in the
Copy WM quantity eld.
Goods Issue
Use
Mobile Data Entry supports the goods issue process. Using their RF devices, warehouse workers can perform the following
goods issue-related functions:
View and change shipment information
Pack/unpack delivery items
Load deliveries
Split deliveries
Generate and con rm TOs for delivery items
Post goods issues to Inventory Management
Prerequisites
The goods issue is based on an outbound delivery.
Features
You can perform goods issues for outbound deliveries identi ed by:
Delivery number
Handling unit (HU) number
Staging area
4/24/2022
Shipment number
Group number
Other criteria
Performing a Goods Issue
Use
Using an RF device, you can perform a goods issue for an outbound delivery identi ed by one of the following:
Delivery number
Handling unit number (if HU already exists and is assigned to an outbound delivery)
Staging area
Shipment number
Group number
Other criteria
 Recommendation
We recommend that you use the staging area selection method only when you cannot identify deliveries by any of the other
criteria, since this method is time consuming.
Procedure
GI for Delivery Identi ed by:
Delivery HU Number Staging Area Shipment Group Number Other Criteria

Number Number
1 From the RF From the RF From the RF From the RF From the RF From the RF
menu, choose menu, choose menu, choose menu, choose menu, choose menu, choose
Outbound Outbound Outbound Outbound Outbound Outbound
Process Goods Process Goods Process Goods Process Goods Process Goods Process Goods
Issue GI by Issue GI by Issue GI by Issue GI by Issue GI by Issue GI by
Delivery . Handling Unit . Staging Area . Shipment . Group . Others.
The Select The Select The Select The Select The Select The Select
Delivery screen Storage Delivery by Delivery by Delivery by Delivery by
appears. Unit/Handling Staging Area Shipment Group screen Others screen
Unit screen screen appears. screen appears. appears. appears.
appears.
2 Enter the Enter the Enter the staging Enter the Enter the group Enter one or
delivery number handling unit area. shipment number. more of the
using the number using the number using following criteria:
scanner or scanner or the scanner or
Material
keyboard. keyboard. keyboard.
Ship-to-
party
4/24/2022
Delivery
date
External
delivery
reference
Door
Service
agent
3 Choose Nxt . The Delivery Header Information screen appears, displaying the following information for the delivery:
Load/unload status
Ship-to account number
Ship-to party name
Shipping point and shipping date
Total weight of goods delivered
Number of packages
HU indicator indicating whether or not an HU exists for the delivery
TO indicator indicating whether or not a TO exists for the delivery
4 You can scroll between deliveries by choosing PgUp ( ) / PgDn ( ) (applies to deliveries identi ed by staging area,
shipment number, group or other criteria only)
5 To view the items in the delivery, choose Items. The Delivery Item Information screen appears, displaying the
following information:
Delivery information, including total number of items in delivery and number of items con rmed
Material information, including material name, special stock number, quantity and batch number
6 To view or change information on the corresponding shipment:
1. Choose Shipmt . The Shipment Information screen appears, displaying the shipment number, external ID,
container ID, shipment type and shipment route.
2. To manually change the loading start date and time or loading end date and time, enter the data in the relevant
elds and choose Save .
3. When you commence the load process selected by shipment, the start date and time are automatically
updated. The end date and time are automatically updated when loading the last HU.
4. To print a shipping unit label, choose PrSh .
7 To pack or unpack delivery items:
1. Choose More and then Pack or Unpck . The Pack/Unpack screen appears, displaying the status of Packing or
Unpacking .
2. Follow steps 2 onwards in Packing or Unpacking .
8 To load the delivery:
1. Choose LdUn . The Load/Unload by Delivery screen appears.
2. Follow steps 2 onwards in Performing Loading/Unloading (Load/Unload by Delivery).
4/24/2022
9 To split the delivery so as to load the items on different means of transportation:
1. Choose More and then Split. The Split Delivery by Quantity screen or Split Delivery by Handling Unit screen
appears, depending on whether or not a HU exists for the delivery.
2. Enter the quantity or HU to be transferred to the new delivery and choose Save . The new delivery is created.
10 If a TO does not exist for some or all of the items in the delivery, choose G.TO. to generate a TO for the items without a
TO.
 Note
If the delivery contains batch-managed material, the batch number must be entered in the delivery in order to
generate a transfer order.
11 To con rm the TOs for the delivery:
1. Choose TOex . The source screen appears.
2. Follow step 5 onwards in Picking from Bulk or in Picking from a Non-Bulk Storage Type , depending on the
storage type of the source bin.
12 To post the goods in Inventory Management :
1. Choose Post. A message appears.
2. Choose Yes to post the goods.
 Note
Generally speaking, the TO must be con rmed before executing the posting.
You can determine that the delivery is automatically posted when all of the delivery items are processed in
Customizing for Logistics Execution Warehouse Management Interfaces Shipping De ne Shipping
Control De ne Shipping Control at the Movement Type Level. Enter 2 in the Copy WM quantity eld.
You can also set the system for partial posting of deliveries (data for a speci c delivery item, whose TOs are
completed, is posted) in Customizing for Logistics Execution Warehouse
Management Interfaces Shipping De ne Shipping Control De ne Shipping Control at the Movement Type
Level. Enter 4 in the Copy WM quantity eld.
Putaway
Use
Mobile Data Entry supports the putaway process. Putaway execution is based on a transfer order (TO) for putaway created in
the Warehouse Management System (WMS) or as part of the RF goods receipt function.
Prerequisites
There are available TOs for putaway.
Features
You can perform the following types of putaways:
Selected by storage unit/handling unit
4/24/2022
Clustered
Selected by transfer order
Selected by delivery
System-guided
Performing a Putaway
Use
Using an RF device, you can perform the following types of putaway:
1. P utaway based on SU/HU number
You can use this option if you do not know the transfer order for an SU/HU. Identify the SUs/HUs and then store them in
an SU-managed or HU-managed part of the warehouse.
 Recommendation
If you perform putaways for mixed pallets, we recommend that you trigger the display of the destination storage bin
immediately after scanning the SU/HU number. To do this, set the Skip source dta. indicator in Customizing for
Logistics Execution Mobile Data Entry Veri cation Control Assign Veri cation Pro les to Goods Movements .
4/24/2022
 Note
This works for one-step con rmation TOs only.
For two-step con rmation TOs, the source screen always appears, with no veri cation elds being open. Choosing
Save for one of the items will save all the items on the source screen.
2. Putaway based on transfer order
3. Clustered putaway
Refer to Performing a Clustered Putaway .
4. Putaway based on delivery number
You can enter the delivery number individually if you have transfer orders (TOs) that refer to a speci c delivery, and then
execute putaway immediately. The system selects and then blocks individual TOs for delivery.
5. System-guided putaway
The system proposes the next putaway TO in the queue to which you are assigned.
For more information on queue assignments, see RF Queue Management .
Procedure
Putaway by SU/HU Putaway by Transfer Order Putaway by Delivery System-Guided P
1 From the RF menu, choose one of From the RF menu, choose one of From the RF menu, choose one of From the RF menu
the following: the following: the following: the following:
Inbound Inbound Inbound Inbound

Process Putaway Putaway Process Putaway Putaway Process Putaway Putaway Process P
by Storage Unit by Transfer Order by Delivery Guided Pu
Stock Stock Stock Stock

Transfer Putaway Putaway Transfer Putaway Putaway Transfer Putaway Putaway Transfer
by Storage Unit by Transfer Order by Delivery Guided Pu
The Select Storage The Select Transfer Order The Select Delivery screen
Unit/Handling Unit screen screen appears. appears.
appears.
2 Enter the SU/HU number using the Enter the TO number and choose Enter the delivery number using the
scanner or keyboard and choose Nxt. scanner or keyboard and choose
Nxt. Nxt.
3 The source screen appears, displaying:
Source information, including source bin and source SU/HU
Material information, including material number, name, quantity and UoM
 Note
If you are entering from the Delivery Header Information screen, you go straight to this screen.
4 To view more information on the TO item, choose Det .
5 Verify the data and choose Save to con rm a material at source.
6 Choose PgUp ( ) / PgDn ( ) to scroll between materials, if there is more than one material.
4/24/2022
Putaway by SU/HU Putaway by Transfer Order Putaway by Delivery System-Guided P
7 Choose Nxt to proceed to the destination screen . The destination information is displayed.
 Note
For a putaway by TO or delivery, or a system-guided putaway, you can con rm only part of the TO by choosing Nxt without saving all of
8 To change the destination bin:
1. a. Choose NBin . The Change Destination Bin screen, appears.
2. b. Verify the bin number.
3. c. Scan the new bin number and choose Conf. The Dest. bin eld is updated.
9 Verify the data and choose Save to con rm the materials at destination.
Performing a Clustered Putaway
Use
Using an RF device, you can put away several SUs/HUs simultaneously.
Prerequisites
You are using a device with sufficient capacity.
In the case of two-step con rmation, the selected SUs/HUs belong to the same TO.
If you perform putaways for mixed pallets, we recommend that you trigger the display of the destination storage bin
immediately after scanning the SU/HU number. To do this, set the Skip source dta. indicator in Customizing for Logistics
Execution → Mobile Data Entry → Veri cation Control Assign Veri cation Pro les to Goods Movements
This works for one-step con rmation TOs only.
For two-step con rmation TOs, the source screen always appears, with no veri cation elds being open. Choosing Save for one
of the items will save all the items on the source screen.
Procedure
From the RF menu, choose one of the following:
Inbound Process → Putaway → Clustered Putaway
Stock Transfer → Putaway → Clustered Putaway
4/24/2022
The Select Storage Units - Clustered screen appears.
Enter a SU/HU number using the scanner or keyboard.
To add more SUs/HUs:
a. Choose NSU . The SU/HU number appear below Selected storage units.
b. Repeat step 2.
After you have nished selecting SUs/HUs, choose Nxt . The source screen appears, displaying:
Source information, including source bin
Material information, including SU/HU, material number, name, quantity and UoM
To view more information on the TO item, choose Det .
Verify the data and choose Save to con rm at source.
Choose PgUp () / PgDn () to scroll between SUs/HUs.
After con rming all SUs/HUs, choose Nxt to proceed to the destination screen. The destination information is displayed.
To change the destination bin:
a. Choose NBin . The Change Destination Bin screen, appears.
b. Verify the bin number.
c. Scan the new bin number and choose Conf. The Dest. bin eld is updated.
Verify the data and choose Save to con rm the materials at destination.
Picking/Replenishment
Use
Mobile Data Entry supports the picking/replenishment process. The picking execution is based on transfer orders (TOs) for
picking created in the Warehouse Management System (WMS) or as part of the RF goods issue function.
Prerequisites
There are available TOs for picking.
 Note
If you are working in a storage unit/handling unit-managed environment, you can de ne that pick HUs are to be created and
assigned automatically upon TO creation. For more information, see the Implementation Guide (IMG) for Logistics
General Handling Unit Management Basics Warehouse Management De ne Control for Automatic Creation of Pick HUs .
You can also propose a source HU as the destination HU if the entire material quantity is picked by choosing Customizing for
Logistics General Handling Unit Management Basics Warehouse Management De ne Storage Type. In activities De ne
Storage Type and De ne Movement Types , enter 1 in the HU picking control eld. In this case, the system does not support
the reporting of differences.
4/24/2022
Features
You can do the following:
Pick from bulk
Pick from a non-bulk storage type
Pick and pack
Pick and pack nested handling units
Picking from Bulk
Use
Using an RF device, you can pick materials from a bulk storage type. You can select the pick transfer order (TO) by:
Identifying the TO number
Identifying the delivery number
Selecting the system-guided option, whereby the system guides you according to sorting and your queue assignment
4/24/2022
 Note
The system recognizes any discrepancy between the TO pick quantity and the quantity of material in the SU/HU that you
pick, automatically opening up a differences screen.
Prerequisites
In Customizing for Logistics Execution Warehouse Management Storage Units Strategies De ne Bulk Storage Area De ne
Storage Type Control , you have entered Y in the Round off eld to avoid partial pallet quantities.
Procedure
Pick by TO Pick by Delivery System-Guided

Pick/Replenishment
1 From the RF menu, choose one From the RF menu, choose one From the RF menu, choose one
of the following: of the following: of the following:
Outbound Process Outbound Process Outbound Process

Picking/Replenishment Picking/Replenishment Picking/Replenishment
Picking by Transfer Picking by Delivery System-Guided
Order Picking/Replen.
Stock Transfer
Stock Transfer Picking/Replenishment Stock Transfer
Picking/Replenishment Picking by Delivery Picking/Replenishment
Picking by Transfer System-Guided
The Select Delivery screen
appears.
The Select Transfer Order
screen appears.
2 Enter the TO number. Enter the delivery number using

the scanner or keyboard.
3 Choose Nxt .
Source information, including source bin and source SU/HU
Material information, including material number and name, quantity and UoM
5 Enter the SU/HU number in the Verify SU eld using the scanner or keyboard.
7 If the TO quantity is greater than the quantity of the scanned SU/HU, you can either force the system
to generate a new TO for the remaining items not picked, or you can end con rmation after the pick.
To end con rmation after the pick, choose Endcnf . The EndCnf indicator is set.
8 Choose Enter .
9 If the TO quantity differs from the quantity of the scanned SU/HU, the Report Difference for Pick
from Bulk Storage screen automatically appears. Enter the pick quantity and choose Conf .
10 The destination screen appears.
11 Choose Save to con rm the materials at destination.
If the picked quantity was less than the TO quantity and the EndCnf indicator was not set (in step 7
above), the source screen of the next TO item for the remaining quantity appears.
4/24/2022
Picking from a Non-Bulk Storage Type
Use
Using an RF device, you can pick materials from any non-bulk storage type. You can select the pick transfer order (TO) by:
Identifying the TO number
Identifying the delivery number
Selecting the system-guided option, whereby the system guides you according to sorting and your queue assignment
Procedure
Pick by TO Pick by Delivery System-Guided

Pick/Replenishment
1 From the RF menu, choose one From the RF menu, choose one From the RF menu, choose one
of the following: of the following: of the following:
Outbound Process Outbound Process Outbound Process

Picking/Replenishment Picking/Replenishment Picking/Replenishment
Picking by Transfer Picking by Delivery System-Guided
Stock Transfer
Stock Transfer Picking/Replenishment Stock Transfer
Picking/Replenishment Picking by Delivery Picking/Replenishment
Picking by Transfer System-Guided
Order The Select Delivery screen Picking/Replen.
appears.
The Select Transfer Order
screen appears.
2 Enter the TO number. Enter the delivery number using

the scanner or keyboard.
3 Choose Nxt .
Source information, including source bin and source SU/HU (if the bin is in an SU/HU-managed
environment)
Material information, including material number and name, quantity and UoM
5 Choose PgUp ( ) / PgDn ( ) to scroll between SUs/materials, if there is more than one SU or material.
7 If you are picking a quantity that differs from that in the TO, report the difference by doing the following:
1. Choose Diff . The Report Differences in Destination Quantities screen appears.
2. Enter the actual quantity in the relevant eld and choose Chk . The difference quantity is
automatically calculated.
3. Choose Conf to con rm the reported difference. You return to the source screen.
8 Verify the data and choose Save to con rm a SU or material at source.
9 Once all items are con rmed at source, choose Nxt . The destination screen appears.
4/24/2022
10 Choose Save to con rm the SUs/materials at destination.
Pick and Pack
Use
Using an RF device, you can pick and pack material in one step. This is useful in a handling unit-managed environment, where
partially picking from one or more handling units (HUs) necessitates the speci cation of the HU into which these materials are
packed (destination HU).
The destination HU can be assigned to a transfer order (TO) in one of the following three ways:
1. The HU number is assigned at TO creation. After choosing the pick and pack option using an RF device, you enter the
number of the existing HU.
2. After choosing the pick and pack option using an RF device,you take a label and scan it. At this point, the HU number is
assigned to the TO.
3. Using a small printer connected to an RF device, you choose the pick and pack option. You print a label and affix it to the
destination HU. You then scan the label and the HU number is assigned to the TO.
You can either select a pick and pack transaction based on system-guided picking (for TOs with reference to a delivery), or by
identifying a delivery number.
Prerequisites
1. You have maintained all the packaging-relevant parameters in Customizing for Logistics General Handling Unit
Management .
 Note
You can de ne a default packaging material in Customizing for Logistics General Handling Unit
Management Basics Warehouse Management De ne Control for Automatic Creation of Pick HUs .
2. If you want to use the pick and pack function in a storage location that is not handling unit-managed, set the Pick&Pack
indicator in Customizing for Logistics Execution Warehouse Management Interfaces Shipping De ne Shipping
Control Shipping Control per Warehouse number. After a TO is con rmed, the pick HU is assigned to the delivery.
3. Pick TOs are created with reference to deliveries.
Procedure
Pick and Pack Pick and Pack by Delivery
1 From the RF menu, choose one of the following: From the RF menu, choose one of the following:
Outbound Outbound
Process Picking/Replenishment Pick Process Picking/Replenishment Pick
and Pack and Pack by Delivery
Stock Stock
Transfer Picking/Replenishment Pick Transfer Picking/Replenishment Pick
and Pack and Pack by Delivery
The Pick and Pack screen appears. The Pick and Pack by Delivery screen appears.
4/24/2022
Pick and Pack Pick and Pack by Delivery
2 Enter the delivery number using the scanner or

keyboard.
3 You have the following options for de ning or selecting handling units:
1. a. Enter a new HU number from the external HU number range.
2. b. Enter or scan an existing HU number.
3. c. If you skip the Handling unit eld, the system assigns a number. You can see the
number by choosing Prt. to print the HU label.
Choose Enter . If you de ned a default packaging material, it is entered automatically. You
can override it and enter a different packaging material.
4 Choose Nxt . The source screen appears for the Choose Nxt . The source screen appears for the
rst pick TO in the queue.. TO of the delivery.
5 Choose PgUp ( ) / PgDn ( ) to scroll between SUs/materials, if there is more than one SU or
material.
7 If you are picking a quantity that differs from that in the TO, report the difference by doing the
following:
1. Choose Diff . The Report Differences in Destination Quantities screen appears.
2. Enter the actual quantity in the relevant eld and choose Chk . The difference quantity is
automatically calculated.
3. Choose Conf to con rm the reported difference. You return to the source screen.
8 Verify the data and choose Save to con rm an SU or material at source.
9 Once all items are con rmed at source, choose Nxt . The destination screen appears.
10 Choose Save to con rm the SUs/materials at destination.
 Note
If you want to pack TO items of a different TO into the same handling unit, enter the number of the handling unit that you
selected before. Proceed as described above.
If you cannot pack all the TO items into one handling unit, create a new handling unit and assign it to the same TO.
Pick and Pack - Nested Handling Units
Use
The nested handling unit transaction (LM47) enables you to execute the regular picking transactions (including pick and pack),
for nested handling units (HUs), from bulk or non-bulk storage.
Currently, this transaction is supported for two-levels of HUs – a highest-level HU and one level of lower-level HUs.
Prerequisites
4/24/2022
The transaction is accessed by choosing Outbound Process Picking / Replenishment Pick and Pack – Nested HUs from the
RF menu.
Features
The transaction is similar to the other pick and pack transactions, with the following differences:
1. On the initial screen, you must enter the TO number, delivery number, or both.
You also have the option of entering the pick HU (for pick and pack) and a packaging material.
2. On the source screen, you have the option of entering/scanning the number of the highest-level HU (in the SrcHU eld) ,
or of any of the lower-level HUs (in the LwrHU eld).
3. The Nested Handling Units - Lower-Level HUs screen appears in the following ways:
If you enter or scan the number of the highest-level HU, or any of the lower-level HUs, and then choose F9 Nest .
Automatically, after you scan the HU number and choose Enter , if the quantity of material in the HU is higher
than the TO item material quantity
Automatically if you enter or scan the number of the highest-level HU and choose F6 Diff
4. Once you are in the Nested Handling Units - Lower-Level HUs screen, you can do the following:
View previously scanned lower-level HUs
Enter or scan the number of another lower-level HU that you want to add to the list of selected HUs
Select a speci c lower-level HU from the list by scanning it again
Select the next HU from the list, by choosing Enter . Each time you choose Enter , the next line in the list is
selected.
Delete an HU, by selecting it and choosing DelHU
Pick an entire HU (take-over), by selecting it and choosing F7 AllHU. If an HU is already marked for take-over,
choosing F7 AllHU enables you to pick a speci ed quantity of material from the HU, and to enter differences.
5. After selecting HUs or material quantities to be picked, the open quantity is updated in the Op eld.
Interleaving
Use
Mobile Data Entry provides interleaving functionality, alleviating dead-heading in RF-managed warehouses.
Integration
Interleaving utilizes the putaway and picking/replenishment functions.
Prerequisites
1. Transfer orders (TOs) for picking/replenishment are available in the warehouse.
2. The TOs belong to the same queue. For more information on queues, see RF Queue Management .
4/24/2022
Features
The system enables two types of interleaving:
Interleaving by storage unit/handling unit
System-guided interleaving
Activities
1. A forklift operator receives a TO for putaway via its RF device.
2. The operator performs and con rms the putaway.
3. The operator receives a TO for picking/replenishment.
4. After con rming the TO, the operator is able to repeat the process, the cyclical nature of work assignments providing it
with a continuous work ow.
 Note
You can use the user exit function EXIT_SAPLLMOB_061to de ne selection criteria for identifying the next TO to be
processed for picking/replenishment. For example, you can use it to assign TOs for picking/replenishment with a
source storage bin close to the destination storage bin of the previous TO for putaway.
For more information, see Sorting Using the User Exit .
4/24/2022
Executing Interleaving
Use
Using an RF device, you can:
Identify by SU/HU number a TO for putaway; or
Prompt the system to propose a TO for putaway,
the con rmation of which prompts a TO for picking/replenishment from the same queue as the TO for putaway.
Procedure
Interleaving by Storage Unit System-Guided Interleaving
1 From the RF menu, choose one of the From the RF menu, choose one of the
following menu paths: following menu paths:
Inbound Process Interleaving Inbound Process Interleaving

Stock Transfer Interleaving Stock Transfer Interleaving

The Select Storage Unit/Handling Unit The source screen appears.

screen appears.
2 Follow step 2 onwards in Performing a Follow step 4 onwards in Performing a

Putaway . Putaway .
After you have con rmed the destination After you have con rmed the destination
information of the TO for putaway, the information of the TO for putaway, the
system proposes a TO for picking. system proposes a TO for picking.
3 If the source of the TO for picking is of a bulk storage type, follow step 5 onwards in
Picking from Bulk .
Otherwise, follow step 5 onwards in Picking from a Non-Bulk Storage Type .
You return to the source screen from where you can process another TO for putaway.
Packing and Unpacking

Use
Mobile Data Entry supports the packing and unpacking of materials into/from HUs. The HUs may be assigned or unassigned:
Unassigned handling units (free HUs)
It is possible to create HUs without reference to a document. You assign the material items and the packaging material
to this HU. The packed material is posted to a storage location. The HUs created here are HUs with inventory
management information. If the storage location is warehouse-managed, stock information will also be created.
You execute packing and unpacking of unassigned HUs via the Pack and Unpack menu options.
Handling units assigned to a delivery
Packing is part of delivery and shipment processing. During delivery processing, you can select the delivery items that
you would like to pack and assign them to handling units. If the incoming goods are stored in a handling unit-managed
4/24/2022
storage location, it is mandatory to pack them.
You execute packing and unpacking of assigned HUs via the Goods Receipt and Goods Issue transactions.
 Note
You can create default packaging material for a warehouse in Customizing for Handling Unit
Management Basics Warehouse Management De ne Control for Automatic Creation of Pick HUs.
Packing
Use
Using an RF device, you can use this option to pack material items into HUs.
Procedure
From the RF menu, choose Internal Warehouse Processes → Pack
The Pack/Unpack screen appears, displaying the statusPacking
Using this option, you can only pack an HU that is not assigned to a delivery. To pack an HU assigned to a delivery, see
Performing a Goods Issue.
Do one of the following:
a. If there is no default packaging material, enter packaging material in the appropriate eld and choose Enter .
b. If you are packing into an existing HU, the plant, storage location and storage bin are taken from the HU data. If you are
creating a new HU, you must manually enter this information.
You can also de ne your own default user parameters by choosing System → User pro le → Own data → Parameters.
To print the HU label, choose Prt . For more information, see Printing Using the User Exit .
To pack materials into the HU:
a. Choose ByMt . The Select Material for HU Activities screen appears.
b. Enter the material, quantity and UoM to be packed. You can also enter batch, special stock number, stock indicator and
category.
c. Choose Enter . The material, quantity and UoM appear under the Material list .
d. To view details on a material, choose Mt.D .
4/24/2022
e. To select auxiliary packaging material:
i. Choose APM . The Select Packaging Material screen appears.
ii. Enter the packaging material name and choose Enter .
iii. Choose Back . The auxiliary packaging material is now displayed in the Material list .
f. Choose Save .
Unpacking
Use
Using an RF device, you can use this option to unpack material items from HUs.
 Note
Unpacking handling units assigned to outbound deliveries is only supported for non-HU-managed storage locations.
Procedure
1. From the RF menu, choose Internal Warehouse Processes Unpack .
The Pack/Unpack screen appears, displaying the status Unpacking.
 Note
Using this option, you can only unpack an HU that is not assigned to a delivery. To unpack an HU assigned to a delivery,
see Performing a Goods Receipt.
2. Enter the number of the handling unit to be unpacked and choose Enter.
HU information including the default packaging material and storage location is automatically displayed.
3. To print the HU label, choose Prt. For more information, see Printing Using the User Exit.
4. To unpack materials from the HU:
a. Choose ByMt. The Select Material for HU Activities screen appears.
b. Enter the material, quantity and UoM to be unpacked. You can also enter batch, special stock number, stock
indicator and category.
c. Choose Enter. The material, quantity and UoM appear under the Material list.
d. To view details on the material, choose Mt.D.
e. Choose Save. The message Handling unit was unpacked appears.
Inventory Counting
Use
You can use RF devices for inventory counting, enabling a greater degree of accuracy and efficiency. This is particularly useful,
given the importance of inventory counting in terms of data maintenance and country-speci c tax laws.
4/24/2022
 Note
For more information on Inventory Counting, see Inventory in the SAP Library for Warehouse Management System .
New Dynamic Cycle Counting (DCC) functionality provides a number of features that facilitate cycle counts in the warehouse,
including:
Physical inventory counting against inactive inventory documents (i.e. while open transfer orders exist for a bin)
Inventory counting at quant level
Creation of inventory documents by RF users
Automatic clearing of active and inactive documents
For more information, see Dynamic Cycle Counting .
Dynamic Cycle Counting (LE-WM-DCC)
Purpose
Mobile Data Entry supports inventory counting via RF devices, enabling a greater degree of exibility and efficiency. This is
accomplished through Dynamic Cycle Counting (DCC).
4/24/2022
DCC enhances the previous inventory counting functionality by enabling you to count physical inventory at storage bin and
quant level during the performance of normal warehouse operations, and allowing the creation of inventory documents when
open transfer orders (uncon rmed picks and putaways) exist for a bin. This ensures continued warehouse operations and
facilitates cycle counts during peak activity periods.
 Note
For more information on Inventory Counting, see Inventory in the SAP Library for Warehouse Management System .
Implementation Considerations
DCC is of most use to 7x24 operations, but is also useful to any warehouse for which there is a need to improve the usage of
available resources.
 Recommendation
We recommend that you use DCC only in those storage types where you have set two-step con rmation (Con rmation for
both stock removals and stock placements, set in Customizing for Logistics Execution Warehouse Management Master
Data De ne Storage Type) .
Integration
DCC involves minimal changes to the existing inventory counting transactions LM50 (system-guided storage unit count) and
LM51 (user-selected storage unit count). It uses similar RF screens with the following changes:
Addition of the material eld below the Storage Bin eld in the initial selection screen
The More pushbutton replaces the DISU pushbutton
Addition of the DelDoc pushbutton
Addition of various message screens
Addition of new inventory count status D (dynamic cycle count)
Even though transactions LM50 and LM51 still exist in the system, you need only use the new DCC transactions (LM58, LM59
and LM60).
 Caution
Pre-version 4.7 transactions LM52 (user-selected storage bin count) and LM53 (system-guided storage bin count) still exist
in the system, since they cannot be deleted. However, you must not use them.
Features
DCC provides the following features:
Inventory Counting Against Active and Inactive Inventory Documents
DCC enables inventory counting against both active and inactive inventory documents, allowing you to count the physical
inventory in a bin whether or not open transfer orders exist for the bin. For more information, see Dynamic Cycle Counting
Process .
Inventory Counting at Both Bin and Quant Level
4/24/2022
DCC supports inventory counting for a bin, as well as for a speci c material in the bin.
Applicable to SU-Managed, HU-Managed and Non SU/HU-Managed Environments
You can count inventory for storage unit (SU)-managed , handling unit (HU)-managed and non SU/HU-managed environments.
In an SU or HU-managed environment, you scan/count each SU/HU in a storage bin. If desired, you can also count the
material quantity within an SU/HU.
In an HU-managed environment, you can scan/count nested (multi-level) HUs in a storage bin but cannot count the
lower-level HUs. In other words, you can only count the content of a single-level HU.
In a non-SU/HU managed environment, you count the material quantities in a storage bin.
The screens displayed on the RF device vary according to whether or not the storage bin is in an SU/HU-managed environment.
Different Modes of Bin/Quant Selection
There are three main options for performing an inventory count using an RF device:
1. System-guided
The system proposes all of the bins/materials of an inventory document that was assigned to the particular user. This
assignment takes place during the creation of the document.
2. User-selected
The user selects the storage bin or material in a bin for the inventory count. Under this option, you can select and scan
storage bins or materials within a warehouse area that are assigned from an organizational point of view.
 Example
Worker A processes aisles 1 and 2, and worker B processes aisles 3 and 4
3. User-initiated
In a case where an inventory document does not already exist in the system, the system creates “on the y” an inactive
or active document for the selected storage bin or material in the bin. The user can then start the inventory count.
Automatic Clearing of Inactive Inventory Documents
DCC supports the automatic clearing of an inventory count in Warehouse Management (WM) against active documents, or
inactive documents if the count results in no differences.
Dynamic Cycle Counting Process

Process Flow
4/24/2022
Performing a User-Selected Dynamic Inventory Count: By

Quant
Use
You can perform a dynamic inventory count on a speci c material in a bin, for which there is an active or inactive inventory
document.
Prerequisites
1. There is an active or inactive inventory document for a speci c material in a bin.
2. For counting against an inactive document, the storage bin belongs to a storage type for which a record exists in
Customizing for Logistics Execution Warehouse Management Activities Physical Inventory Dynamic Cycle
Counting General Settings De ne Storage Type Settings.
3. You have logged on to the RF device.
4/24/2022
Procedure
SU/HU-Managed Environment Non SU/HU-Managed Environment
Choose Internal Warehouse Processes Inventory Dynamic Cycle Count DCC User-
Guided Count. The DCC: Initial screen appears, displaying the last-entered storage type
number.
Enter or scan the storage bin number or its veri cation value.
In the Material eld, enter the name of the material, in the bin, to be counted.
Choose Nxt . Choose Nxt .
The Verify SU eld appears. The DCC: Quant screen for counting the
speci c storage bin content appears.
If you want to delete the inventory document, do the following:
1. a. Choose More .
2. b. Choose DelDoc . A query message appears.
3. c. Choose Yes . A con rmation message appears.
4. d. Choose OK . You return to the initial screen.
If the bin is empty of storage units If the bin is empty of the relevant material
containing the relevant material , do the , the message
following: Confirm that the bin is empty
appears.
1. a. Choose BnEm . The status is
updated to Counted to zero and 1. a. Choose Ok and then BnEm. A
theSave button appears. check appears next to the storage
bin number.
2. b. Choose Save to con rm the
inventory count. 2. b. Choose Save to con rm the
inventory count.
If the bin is not empty of storage units If the bin is not empty, do the following:
containing the relevant material, do the
1. a. Enter the material quantity and
following:
unit of measure. Choose Save to
1. a. Scan or enter the numbers of con rm that you counted the
each relevant SU/HU in the bin. The material.
SU/HU numbers appear below
2. b. If the storage bin does not
Selected storage units , and the
contain any quantity of the
Save button appears on the screen.
displayed material, choose ZeroSt .
If you scan an SU/HU containing a The material quantity is
different material, the error automatically updated to zero, and
message a check appears. Choose Save to
You verified the wrong con rm that you counted the
storage unit material.
appears.
3. c. If you nd a speci c batch of the
2. b. To delete an SU/HU from the relevant material in the SU/HU,
Selected storage units list : which is not displayed in the DCC:
Quant screen, choose NwIt and
a. i. Place the cursor over the repeat step a above.
SU/HU number.
If you enter a different material, the
b. ii. Choose More .
error message
4/24/2022
The material x does not
match inventory document
c. iii. Place the cursor over the material
SU/HU number again. appears.
d. iv. Choose DelSU . 4. d. After you have completed

counting the materials in the
3. c. If you nd a new SU/HU in the
storage bin, choose Back . You
bin, which contains the relevant
return to the DCC: Initial screen .
material, do the following:
The inventory count is con rmed.
a. i. Choose NwIt .
b. ii. Enter the details of the

SU/HU and choose Enter .
c. iii. Choose Save .
d. iv. Choose Back . You return

to the DCC: Initial screen.
4. d. To count the material in an

SU/HU, do the following:
a. i. Enter/scan the SU/HU

again, or place the cursor
alongside the SU/HU
number and choose Det .
TheDCC: Quant screen for
counting the speci c
SU/HU content appears.
b. ii. For the material found in

the SU/HU, enter the
quantity and unit of
measure. Choose Save to
con rm that you counted
the material.
c. iii. If the SU/HU does not

displayed material, choose
ZeroSt . The material
quantity is automatically
updated to zero, and a
check appears. Choose
Save to con rm that you
counted the material.
d. iv. If you nd a speci c

batch of the relevant
material in the SU/HU,
which is not displayed in the
DCC: Quant screen, choose
NwIt and repeat step ii
above.
If you enter a different

material, the error message
The material x does
not match inventory
document material
appears.
e. v. After you have completed

4/24/2022
SU/HU, choose Back . You

return to the DCC: Initial
screen .
5. e. Choose Save .
The inventory count is con rmed for

the selected SUs/HUs.
The following SU/HU statuses are

possible:
Already counted : The

inventory count for the
SU/HU has been
completed, with the
con rmed quantity
corresponding to the
system quantity (Either you
scanned the SU/HU number
and then con rmed with
Save , or you counted the
materials inside the SU/HU
and entered a quantity
system quantity).
Partially count : Not all of

the materials in the SU/HU
have been counted and
con rmed.
Qty changed : The inventory

count for the SU/HU has
been completed, with the
con rmed quantity not
con rmed a material with a
quantity greater than or less
than the system quantity, or
you added a new item).
Performing a User-Selected Dynamic Inventory Count: By Bin
Use
You can perform a dynamic inventory count on a storage bin for which there is an active or inactive inventory document.
Prerequisites
There is an active or inactive inventory document for the storage bin.
For counting against an inactive document, the storage bin belongs to a storage type for which a record exists in Customizing
for Logistics Execution → Warehouse Management → Activities → Physical Inventory → Dynamic Cycle Counting → General
Settings → De ne Storage Type Settings .
4/24/2022
You have logged on to the RF device.
Procedure
Choose Internal Warehouse Processes → Inventory → Dynamic Cycle Count → DCC

User-Guided Count . The DCC Count: Initial screen appears, displaying the last-entered
storage type number.
The Verify SU eld appears. The DCC Count: Quant screen for counting
the speci c storage bin content appears.
a. Choose More .
b. Choose DelDoc . A query message appears.
c. Choose Yes . A con rmation message appears.
d. Choose OK . You return to the initial screen
If the bin is empty, do the following: If the bin is empty, the messageCon rm
that the bin is emptyappears.
a. Choose BnEm . The status is updated to
Counted to zero and the Save button a. Choose Ok and then BnEm. A check
appears. appears next to the storage bin number.
b. Choose Save to con rm the inventory b. Choose Save to con rm the inventory
count. count.
If the bin is not empty, do the following: If the bin is not empty, do the following:
a. Scan or enter the numbers of each a. Enter the material quantity and unit of
SU/HU in the bin. The SU/HU numbers measure. Choose Save to con rm that you
appear below Selected storage units , and counted the material.
the Save button appears on the screen.
b. If the storage bin contains more than one
b. To delete an SU/HU from the Selected material, you scroll between the materials
storage units list : using the PgDn () / PgUp (pushbuttons.
i. Place the cursor over the SU/HU number. c. If the storage bin does not contain any
quantity of the displayed material, choose
ii. Choose More .
ZeroSt . The material quantity is
automatically updated to zero, and a check
iii. Place the cursor over the SU/HU number
appears. Choose Save to con rm that you
again.
iv. Choose DelSU .
d. If you nd a material in the storage bin,
c. If you nd a new SU/HU in the bin, do the which is not displayed in the DCC Count:
following: Quant screen, choose NwIt and repeat step
a. above.
i. Choose NwIt.
e. After you have completed counting the
ii. Enter the details of the SU/HU and
materials in the storage bin, choose Back .
choose Enter
You return to the DCC Count: Initial screen
iii. Choose Save
iv. Choose Back . You return to the DCC
Count: Initial screen
4/24/2022
d. To count the materials in an SU/HU, do

the following:
i. Enter/scan the SU/HU again, or place the

cursor alongside the SU/HU number and
choose Det . The DCC Count: Quant screen
for counting the speci c SU/HU content
appears.
ii. For any material that is found in the

SU/HU, enter the quantity and unit of
measure. Choose Save to con rm that you
iii. If the SU/HU contains more than one

material, you scroll between the materials
using the PgDn () / PgUp (pushbuttons.
iv. If the SU/HU does not contain any

v. If you nd a material in the SU/HU, which

is not displayed in the DCC Count: Quant
screen, choose NwIt and repeat step ii
above.
vi. After you have completed counting the

materials in the SU/HU, choose Back . You
return to the DCC Count: Initial screen
e. Choose Save .
The inventory count is con rmed for the

selected SUs/HUs.
The following SU/HU statuses are possible:
Already counted : The inventory count for

the SU/HU has been completed, with the
con rmed quantity corresponding to the
system quantity (Either you scanned the
SU/HU number and then con rmed with
Save , or you counted the materials inside
the SU/HU and entered a quantity
corresponding to the system quantity).
Partially count : Not all of the materials in

the SU/HU have been counted and
con rmed.
Qty changed : The inventory count for the

SU/HU has been completed, with the
con rmed quantity not corresponding to the
system quantity (Either you con rmed a
material with a quantity greater than or less
than the system quantity, or you added a
new item).
4/24/2022
We recommend that you count the materials

only in those SUs/HUs that you suspect are
not full, such as those with torn wrapping.
Performing a User-Initiated Dynamic Inventory Count: By

Quant
Use
You can create “on the y” an inventory document for counting by a speci c material in a bin, and then immediately perform the
count.
Prerequisites
1. For counting against an inactive document, the storage bin belongs to a storage type for which a record exists in
Procedure
Choose Internal Warehouse Processes Inventory Dynamic Cycle Count DCC User-
Initiated Count . The DCC: Initial screen appears, displaying the last-entered storage type
number.
In the Material eld, enter the name of the material, in the bin, to be counted.
If there are open transfer orders for the bin, an inactive inventory document is created in
the background.
If there are no open transfer orders for the bin, an active inventory document is created in
the background.
 Note
If you enter/scan the storage bin number only and then choose Nxt , a message screen
appears, enabling you to choose whether to create an inventory document for the bin or
for a speci c material in it.
If you choose Yes , an inventory document is created for the bin.
If you choose No , you return to the initial screen, where you can enter the material and
choose Nxt to create an inventory document for the material.
4/24/2022
1. a. Choose More .
If the bin is empty of storage units If the bin is empty of the relevant material ,
containing the relevant material , do the the message
appears.
bin number.
inventory count.
following:
appears.
a. i. Place the cursor over the
repeat step a. above.
SU/HU number.
error message
c. iii. Place the cursor over the
SU/HU number again.
material
d. iv. Choose DelSU . appears.
3. c. If you nd a new SU/HU in the 4. d. After you have completed

bin, which contains the relevant counting the materials in the
material, do the following: storage bin, choose Back . You
a. i. Choose NwIt .
4/24/2022



alongside the SU/HU

quantity, and unit of
the material.


above.

The material x does
not match inventory
document material
appears.

screen .
5. e. Choose Save .


possible:

SU/HU has been
4/24/2022
completed, with the

con rmed quantity
system quantity).

con rmed.

Performing a User-Initiated Dynamic Inventory Count: By Bin
Use
You can create „on the y“ an inventory document for counting by bin, and then immediately perform the count.
Prerequisites
Settings → De ne Storage Type Settings.
Procedure

User-Initiated Count . The DCC: Initial screen appears, displaying the last-entered storage
type number.
4/24/2022
If there are open transfer orders for the bin, an inactive inventory document is created in
the background.
If there are no open transfer orders for the bin, an active inventory document is created in
the background.
If you enter/scan the storage bin numberonlyand then choose Nxt , a message screen
appears, enabling you to choose whether to create an inventory document for the bin or for
a speci c material in it.
If you choose Yes , an inventory document is created for the bin.
If you choose No , you return to the initial screen, where you can enter the material and
choose Nxt to create an inventory document for the speci c material.
a. Choose More .
d. Choose OK . You return to the initial screen.
count. count.
ii. Choose More .
iii. Place the cursor over the SU/HU number automatically updated to zero, and a check
again. appears. Choose Save to con rm that you
iv. Choose DelSU .
c. If you nd a new SU/HU in the bin, do the which is not displayed in the DCC: Quant
following: screen, choose NwIt and repeat step a.
above.
i. Choose NwIt
choose Enter
4/24/2022
You return to the DCC: Initial screen
iii. Choose Save The inventory count is con rmed.
iv. Choose Back . You return to the DCC:

Initial screen.

the following:

choose Det . The DCC: Quant screen for
counting the speci c SU/HU content
appears.




is not displayed in the DCC: Quant screen,
choose NwIt and repeat step ii above.

return to the DCC: Initial screen
e. Choose Save .

selected SUs/HUs.


con rmed.

4/24/2022

new item).

Performing a System-Guided Dynamic Inventory Count: By

Quant
Use
You can perform a dynamic inventory count by a speci c material on a bin and material proposed by the system.
Prerequisites
1. There is an active or inactive inventory document for a speci c material in a bin.
2. For counting against an inactive document , the storage bin belongs to a storage type for which a record exists in
Procedure
Choose Internal Warehouse Processes Inventory Dynamic Cycle Count DCC System-
Guided Count . The DCC: Initial screen appears, displaying the last-entered storage type
number.
Verify the storage bin number via the Verify the storage bin number via the
scanner or keyboard. scanner or keyboard.
1. a. Choose More .
4/24/2022
If the bin is empty of storage units If the bin is empty of the relevant material
containing the relevant material , do the , the message
appears.
bin number.
inventory count.
following:
appears.
a. i. Place the cursor over the repeat step a above.
SU/HU number.
error message
c. iii. Place the cursor over the
SU/HU number again.
material
d. iv. Choose DelSU . appears.
3. c. If you nd a new SU/HU in the 4. d. After you have completed

bin, which contains the relevant counting the materials in the
material, do the following: storage bin, choose Back . You
a. i. Choose NwIt .



alongside the SU/HU
4/24/2022


quantity and unit of
the material.


above.

The material x does
not match inventory
document material
appears.

screen .
5. e. Choose Save .


possible:

SU/HU has been
completed, with the
con rmed quantity
system quantity).
4/24/2022

con rmed.

Performing a System-Guided Dynamic Inventory Count: By Bin
Use
You can perform a dynamic inventory count on a storage bin proposed by the system.
Prerequisites
There is an active or inactive inventory document for a storage bin, assigned to your username.
Settings → De ne Storage Type Settings.
Procedure

System-Guided Count . The DCC: Initial screen appears, displaying the number of the
proposed storage bin
Verify the storage bin number via the Verify the storage bin number via the
a. Choose More .
d. Choose OK . You return to the initial screen
4/24/2022
count. count.
ii. Choose More .
iii. Place the cursor over the SU/HU number automatically updated to zero, and a check
again. appears. Choose Save to con rm that you
iv. Choose DelSU .
c. If you nd a new SU/HU in the bin, do the which is not displayed in the DCC: Quant
following: screen, choose NwIt and repeat step a.
above.
i. Choose NwIt.
choose Enter
You return to the DCC: Initial screen
iii. Choose Save
iv. Choose Back . You return to the DCC:
Initial screen.

the following:

choose Det . The DCC: Quant screen for
counting the speci c SU/HU content
appears.



4/24/2022

is not displayed in the DCC: Quant screen,
choose NwIt and repeat step ii above.

return to the DCC: Initial screen
e. Choose Save .

selected SUs/HUs.


con rmed.

new item).

Performing a User-Selected Inventory Count

Use
You can perform an inventory count on a storage bin that you select.
Prerequisites
1. There is an activated inventory document for the storage bin.
Procedure
Performing an Inventory Count in an:
4/24/2022
1 Choose Internal Warehouse Processes Inventory Bin Count – User selection . The
Inventory Count: Storage Unit screen appears, displaying the last-entered storage type
number.
2 Enter or scan the storage bin number and, if Enter or scan the storage bin number and, if
required, verify it. required, verify it.
The Verify SU eld appears. The Inventory Count: Quant screen for
counting the speci c storage bin content
appears.
3 If the bin is empty, do the following: If the bin is empty, the message Con rm
that the bin is empty appears.
1. Choose BnEm . The status is
updated to Counted to zero and 1. Choose Ok and then BnEm. A check
the Save button appears . appears next to the storage bin
number.
2. Choose Save to con rm the
inventory count. 2. Choose Save to con rm the
inventory count.
4 If the bin is not empty, do the following: If the bin is not empty, do the following:
1. Scan or enter the numbers of each 1. Enter the material quantity, unit of
SU/HU in the bin. The SU/HU measure and choose Enter . Choose
numbers appear below Selected Save to con rm that you counted
storage units , and the Save button the material.
appears on the screen.
2. If the storage bin contains more
2. To delete an SU/HU from the than one material, you scroll
Selected storage units list , choose between the materials using the
the SU/HU and then choose DISU . PgDn ( ) / PgUp ( pushbuttons.
3. To count the materials in an SU/HU, 3. If the storage bin does not contain
do the following: any quantity of the displayed
material, choose ZeroSt . The
4. material quantity is automatically
updated to zero, and a check
a. Enter/scan the SU/HU
appears. Choose Save to con rm
that you counted the material.
over the SU/HU number and
choose Det . The Inventory
4. If you nd a material in the storage
Count: Quant Screen for
bin, which is not displayed in the
Inventory Count: Quant screen,
choose NwIt and repeat step a.
b. For any material that is above.
found in the SU/HU, enter
5. After you have completed counting
the quantity, unit of measure
the materials in the storage bin,
and choose Enter . Choose
choose Back . You return to the
Inventory Count: Storage Unit
screen.
c. If the SU/HU contains more
6. Choose Save .
than one material, you scroll
between the materials using The inventory count is con rmed.
the PgDn ( ) / PgUp (
pushbuttons.
d. If the SU/HU does not

4/24/2022
e. If you nd a material in the

SU/HU, which is not
displayed in the Inventory
Count: Quant screen,
choose NwIt and repeat
step ii above.
f. After you have completed

return to the Inventory
Count: Storage Unit screen.
5. Choose Save .

selected SUs/HUs.
Already counted : The inventory

count for the SU/HU has been
completed, with the con rmed
quantity corresponding to the
scanned the SU/HU number and
then con rmed with Save , or you
counted the materials inside the
SU/HU and entered a quantity
corresponding to the system
quantity).
Partially count : Not all of the

materials in the SU/HU have been
counted and con rmed.
Qty changed : The inventory count

for the SU/HU has been completed,
with the con rmed quantity not
quantity (Either you con rmed a
material with a quantity greater than
or less than the system quantity, or
 Recommendation
We recommend that you count the
materials only in those SUs/HUs that
you suspect are not full, such as those
with torn wrapping.
Performing a System-Guided Inventory Count

Use
4/24/2022
You can perform an inventory count on a storage bin proposed by the system.
Prerequisites
1. There is an activated inventory document for the storage bin, assigned to your username.
Procedure
Performing an Inventory Count in an:
1 Choose Internal Warehouse Processes Inventory Bin Count – System Guided . The
Inventory Count: Storage Unit screen appears, displaying the number of the proposed
storage bin.
2 Verify the storage bin number via the Verify the storage bin number via the
The Verify SU eld appears. The Inventory Count: Quant screen for
counting the speci c storage bin content
appears.
3 If the bin is empty, do the following: If the bin is empty, the message Con rm
that the bin is empty appears.
1. Choose BnEm . The status is
updated to Counted to zero and 1. Choose Ok and then BnEm. A check
the Save button appears . appears next to the storage bin
number.
2. Choose Save to con rm the
inventory count. 2. Choose Save to con rm the
inventory count.
4 If the bin is not empty, do the following: If the bin is not empty, do the following:
1. Scan or enter the numbers of each 1. Enter the material quantity, unit of
SU/HU in the bin. The SU/HU measure and choose Enter . Choose
numbers appear below Selected Save to con rm that you counted
storage units , and the Save button the material.
appears on the screen.
2. If the storage bin contains more
2. To delete an SU/HU from the than one material, you scroll
Selected storage units list , choose between the materials using the
the SU/HU and then choose DISU . PgDn ( ) / PgUp ( pushbuttons.
3. To count the materials in an SU/HU, 3. If the storage bin does not contain
do the following: any quantity of the displayed
material, choose ZeroSt . The
4.
material quantity is automatically
a. Enter/scan the SU/HU updated to zero, and a check
again, or place the cursor appears. Choose Save to con rm
over the SU/HU number and that you counted the material.
choose Det . The Inventory
4. If you nd a material in the storage
Count: Quant Screen for
bin, which is not displayed in the
Inventory Count: Quant screen,
choose NwIt and repeat step a.
b. For any material that is above.
found in the SU/HU, enter
4/24/2022
the quantity, unit of measure 5. After you have completed counting
and choose Enter . Choose the materials in the storage bin,
Save to con rm that you choose Back . You return to the
counted the material. Inventory Count: Storage Unit
screen.
c. If the SU/HU contains more
than one material, you scroll 6. Choose Save .
between the materials using
the PgDn ( ) / PgUp (
pushbuttons.
d. If the SU/HU does not

e. If you nd a material in the

SU/HU, which is not
displayed in the Inventory
Count: Quant screen,
choose NwIt and repeat
step ii above.
f. After you have completed

return to the Inventory
Count: Storage Unit screen.
5. Choose Save .

selected SUs/HUs.
Already counted : The inventory

count for the SU/HU has been
completed, with the con rmed
quantity corresponding to the
scanned the SU/HU number and
then con rmed with Save , or you
counted the materials inside the
SU/HU and entered a quantity
quantity).
Partially count : Not all of the

materials in the SU/HU have been
counted and con rmed.
Qty changed : The inventory count

for the SU/HU has been completed,
with the con rmed quantity not
quantity (Either you con rmed a
material with a quantity greater than
or less than the system quantity, or
4/24/2022
 Recommendation
We recommend that you count the
materials only in those SUs/HUs that
you suspect are not full, such as those
with torn wrapping.
Loading and Unloading
Use
Mobile Data Entry supports loading and unloading. Using RF devices, you can do the following:
Load handling units on to modes of transport, such as trucks and trains
Unload handling units from incoming means of transport
View the load statuses of shipments, deliveries and handling units
Undo a recent load/unload
Features
The following options are available:
Loading/Unloading by Shipment
Handling units are loaded/unloaded according to a known shipment number.
Loading/Unloading by Delivery
Handling units are loaded/unloaded according to a known delivery number.
When goods are loaded by shipment or delivery, warehouse workers can determine the load sequence. This is important if, for
example, goods with different destinations are loaded on to the same truck.
System-Guided Loading
The system proposes a load sequence of handling units assigned to a known shipment number.
 Note
The load and unload functionality works on the delivery level. Only HUs belonging to a delivery can be loaded. In the
loading/unloading by shipment option, the system allows you to load/unload HUs belonging to a delivery assigned to the
shipment. You can not load/unload HUs that are not directly assigned to a shipment.
4/24/2022
Performing Loading/Unloading
Use
Using an RF device, you can:
Load handling units (HUs) on, or unload HUs from, a means of transport if you know the number of the shipment to
which the HUs are assigned.
Load HUs on, or unload HUs from, a means of transport if you know the number of the delivery to which the HUs are
assigned.
Perform system-guided loading. You enter a shipment number and the system proposes the load sequence of the HUs
assigned to it. In the case of nested HUs, you can enter the higher-level HU and the respective lower-level HUs are
loaded automatically.
Procedure
Load/Unload by Shipment Load/Unload by Delivery System-Guided Loading
1 From the RF menu, choose one From the RF menu, choose one From the RF menu, choose
of the following: of the following: Outbound Process Load
System-Guided Load .
For unloading: Inbound For unloading: Inbound
Process Unload Process Unload The System-Guided Load
Unload by Shipment Unload by Delivery screen appears.
For loading: Outbound For loading: Outbound

Process Load Load Process Load Load
by Shipment by Delivery
The Load/Unload by Shipment The Load/Unload by Delivery

screen appears. screen appears.
4/24/2022
2 Enter the shipment number Enter the delivery number. Enter the shipment number
using the scanner or keyboard. using the scanner or keyboard.
If you entered the Load/Unload

by Delivery screen from the
Delivery Header Information
screen, the number of the
relevant delivery appears
automatically in the Delivery
eld.
3 Enter or scan the handling unit Enter or scan the handling unit Choose Enter . The system
assigned to this shipment. assigned to this delivery. proposes the following:
The rst delivery

assigned to the
shipment
The rst HU assigned to

the delivery
4 Choose Enter. The following information is now displayed: Scan the HU number and
choose Enter .
Shipment information, such as delivery number, staging
area and door
Handling unit information, such as the number of

loaded/unloaded HUs, total number of HUs, weight of each
HU and total weight
5 You can view the load statuses of the shipment (only for load/unload by shipment and system-guided
loading), deliveries and HUs.
To view the load status of the shipment, choose the Ship. eld and then choose Det . The Load
Inquiry by Shipment screen appears. For more information, see Load Inquiry by Shipment .
To view the load status of a delivery, choose the Dlv. eld and then choose Det . The Load
Inquiry by Delivery screen appears. For more information, see Load Inquiry by Delivery .
To view the load status of a handling unit, choose the Handling unit eld and then choose Det .
The Load Inquiry by Handling Unit screen appears. For more information, see Load Inquiry by
Handling Unit .
6 To print a shipping unit label, choose Prt .
 Note
You can only print a label if you have created your own user exit. For more information, see Printing
Using the User Exit .
7 Choose Save to load/unload the handling unit. The system updates Choose Save to load the HU.
the number of HUs loaded/unloaded, their weights, and the
If there are more HUs
statuses of the shipment and delivery.
for the shipment, the
next HU is proposed.
Repeat steps 4-7.
If there are no more HUs

for the shipment, the
system noti es you that
the shipment is fully
loaded.
4/24/2022
8 If you want to unload the HU that you just loaded, or load the HU that you just unloaded, choose Undo .
The information is updated accordingly.
 Note
In system-guided loading, the Undo function works only where the shipment has not yet been fully
loaded.
Serial Number Capture
Use
Mobile Data Entry supports the capturing of serial numbers related to the items of an inbound or outbound delivery.
Prerequisites
1. Created one or more serial number pro les in Customizing for Plant Maintenance and Customer Service Master Data
in Plant Maintenance and Customer Service Technical Objects Serial Number Management De ne Serial Number
Pro les.
2. Maintained the following serializing procedures for the relevant serial number pro les in Customizing for Plant
Maintenance and Customer Service Master Data in Plant Maintenance and Customer Service Technical
Objects Serial Number Management De ne Serial Number Pro les:
SDLS (Maintain delivery)
SDRE (Maintain returns delivery)
When maintaining the serializing procedures, you have not entered 01 in the SerUsage eld.
3. Entered the following in the master data records for materials for which you want to capture the serial numbers:
a. a. Entered the prede ned serial number pro le in the SerialNoPro le eld
b. b. Entered a serialization level in the SerializLevel eld
Features
Mobile Data Entry provides the following features for capturing serial numbers:
Enabling of serial number capture for both equipment(unique numbers) and non-equipment
Automatic assignment of captured serial numbers to relevant equipment
Provision of running totals indicating progress made
 Note
For more information on serial numbers, see the SAP Library for Logistics Logistics – General (LO) Logistics Master
Data (LO-MD) Serial Number Management (LO-MD-SN).
Capturing Serial Numbers
4/24/2022
Prerequisites
In the case of an outbound delivery, the delivery must be fully picked.
If you are using Warehouse Management System , you have con rmed all transfer orders for the delivery items.
If you are not using Warehouse Management System , the delivery quantity has been picked.
Procedure
1. From the RF menu, choose Capture Serial Numbers .
The Serial Number Capture screen appears.
2. Enter the delivery number using a scanner or keyboard.
3. Choose Nxt .
The Serial Number Capture screen appears, displaying the following:
The SN eld at the top of the screen
The delivery items as separate rows.
An indicator eld to the left of each delivery item.
The details of the delivery item for which this indicator is set can be viewed. For more information, see step 5
below.
Running totals of the quantity of serial numbers captured, expressed as a fraction of the total quantity of
material, for each delivery item.
4. If the delivery items are equipment with unique equipment numbers, scan or enter the serial number of each material.
The system automatically allocates the serial numbers to the correct delivery items.
The running totals are updated after each serial number capture.
5. If a delivery item does not have unique equipment numbers, do the following:
a. a. Set the indicator corresponding to the delivery item. If you need to move the indicator to another delivery item,
scroll up or down by choosing the PgUp ( ) / PgDn ( ) pushbuttons.
b. b. Choose Det . The Serial Number: Details screen for the particular delivery item appears.
c. c. Scan or enter the serial number of each material.
After each serial number is scanned, it appears below the SN eld, along with a running total of the quantity of
serial numbers captured, expressed as a fraction of the total quantity of material.
d. d. If you want to delete a captured serial number:
i. i. Set the indicator corresponding to the captured serial number.
ii. ii. Choose Del . A query message appears.
iii. iii. Choose Yes to con rm the message.
6. Choose Save to save the serial numbers to the database.
 Note
If you want to delete serial numbers saved to the database, you can delete them via the Change Inbound/Outbound
Delivery desktop transactions.
4/24/2022
Inquiries
Use
Using an RF device, you can call up information on material stock, handling units and the load statuses of shipments, deliveries
and handling units.
Features
The following inquiries are available:
Stock Overview Inquiry
Handling Unit Inquiry
Load Inquiry by Shipment
Load Inquiry by Delivery
Load Inquiry by Handling Unit
Stock Overview Inquiry
Use
Using this inquiry, you can display information on material stocks sorted by storage bin, goods receipt date or shelf life
expiration date.
Procedure
1. From the RF Menu, choose Inquiries Stock Overview .
The Inquiry – Select Material screen appears.
1. Enter one or more of the following search criteria:
Material
Plant
Storage type
1. Choose one of the following sort criteria:
SBn – sort by storage bin
GRDt – sort by goods receipt date
SLED – sort by shelf life expiration date
The Inquiry – Display Material Stock screen appears.
1. Scroll through the screens by choosing PgUp ( ) / PgDn ( ).
4/24/2022
1. Choose Back to return to the Inquiry – Select Material screen.
Handling Unit Inquiry
Use
Using this inquiry, you can do the following:
Display detailed information on a handling unit (HU) assigned to a delivery or shipment, including information on any
lower-level HUs, materials within the HU, storage unit, warehouse number, storage type and storage bin
Print handling unit and shipping unit labels
Procedure
1. From the RF menu, choose Inquiries Handling Unit Detail .
The Inquiry – Select Handling Unit screen appears.
1. Enter the handling unit number.
1. Choose Nxt .
The type of packaging material for the handling unit appears.
1. Do any of the following:
1. Display information on the storage unit, warehouse number, storage type and storage bin by choosing WM V .
2. Display information on any lower-level HUs by choosing HU V .
3.
a. To display additional information, choose HU D .
b. To display the warehouse management view, choose WM V .
4. Display information on the materials in the HU by choosing MatV .
5.
a. To display additional information, choose Det .
b. To display the warehouse management view, choose WM V .
6. Print a shipping unit label by choosing PrSh .
7. Print a handling unit label by choosing PrHU .
 Note
You can only print labels if you have created your own user exit. For more information, see Printing Using the User Exit .
Load Inquiry by Shipment
Use
4/24/2022
Using this inquiry, you can display the load status of a particular shipment and its respective deliveries.
Procedure
1. From the RF menu, choose one of the following menu paths:
1. Inquiries Load Inquiry by Shipment .
2. Outbound Process Load Load Inquiry by Shipment .
The Load Inquiry by Shipment screen appears.
1. Enter the shipment number.
1. Choose Enter . The following information appears on the screen:
Load status of the shipment
_ – Not relevant
A – No goods loaded
B – Partially loaded
C – Fully loaded
Processing stage of the shipment:
Planned
Planning completed
Check-in
Loading start
Loading end
Shipment completion
Shipment start
Shipment end
The deliveries in the shipment and their statuses:
_ – Not loaded
L – Loaded
Load Inquiry by Delivery
Use
Using this inquiry, you can display the load status of a particular delivery and its respective handling units.
Procedure
4/24/2022
1. Inquiries Load Inquiry by Delivery .
2. Outbound Process Load Load Inquiry by Delivery .
The Load Inquiry by Delivery screen appears.
1. Enter the delivery number.
Load status of the delivery
_ – Not relevant
A – No goods loaded
B – Partially loaded
C – Fully loaded
Number of higher-level HUs loaded
Total number of higher-level HUs for the delivery
The HUs in the delivery
The category of each HU:
X – Higher-level
_ – Lower-level
The status of each HU:
_ – Not loaded
L – Loaded
Load Inquiry by Handling Unit
Use
With this inquiry, you can call up the load status of a particular handling unit (HU), as well as information on the shipping point,
weight, volume and other HUs on same hierarchical level.
Procedure
1. Inquiries Load Inquiry by Handling Unit
2. Outbound Process Load Load Inquiry by Handling Unit
The Load Inquiry by Handling Unit screen appears.
1. Enter the handling unit number.

4/24/2022
Shipping point
Status of the HU
_ – Not relevant
A – No goods packed
B – Partially packed
C – Fully packed
Total weight and volume of the HU
HUs belonging to same hierarchy and their categories:
X – Higher-level
_ – Lower-level
The statuses of these HUs:
Performing a Movement by Storage Unit
Use
You can use this radio frequency option if you do not know the transfer order (TO) number of a storage unit (SU)/handling unit
(HU). Because there is no movement type check, you can identify transfer orders for putaway or picking.
Procedure
1. From the RF menu, choose Stock Transfer Movement by SU .
The Select Storage Unit/Handling Unit screen appears.
2. Enter the SU/HU number using the scanner or keyboard.
3. Choose Nxt . The source screen relating to the underlying TO appears.
4. If the TO is for a simple movement within the warehouse or a putaway, see Performing a Putaway for the remaining
steps.
If the TO is for a pick, see Picking from a Non-Bulk Storage Type for the remaining steps:
 Note
If you set the Skip source dta . indicator in Customizing for Logistics Execution Mobile Data Entry Veri cation
Control Assign Veri cation Pro les to Goods Movements , the source screen is skipped after the SU/HU is scanned
in the case of the following transactions:
LMO2 – Putaway by storage unit
LM13 – Clustered putaway
Posting Changes
4/24/2022
Use
Using an RF device, you can con rm posting changes .
Procedure
Choose Internal Warehouse Processes → Posting Change
The source screen appears.
To view further details on the posting change notice, chose Det .
To con rm the posting change at source, choose Save .
Choose Nxt . The destination screen appears.
To report a difference:
a. Choose Diff . The Report Difference in Destination Quantities screen appears.
b. Enter the actual quantity in the relevant eld and choose Chk . The difference quantity is automatically calculated.
c. Choose Conf to con rm the reported difference. You return to the destination screen.
Choose Save to con rm the posting change at destination.
The next posting change notice appears.
If there are no more posting change notices in the system, the messageThe system could not nd a transfer order for
executionappears.
Other Functions
This section contains information about the following functions :
Recovery
User Exits
Recovery
Use
Where the RF connection between your RF device and the SAP system has been interrupted, the recovery function enables you
to resume the last activity without losing data. Operations you have saved are immediately updated in the system database. If
there is a link failure, the system automatically proposes processing at the point where you last saved data.
In the case of two-step con rmation transfer orders (TOs), logging on via the Logon screen and choosing Save takes you to the
destination screen for the TO items that were partially con rmed.
Prerequisites
You have de ned two-step con rmation for TOs in Customizing for Logistics Execution Warehouse Management Activities
Con rmation.
4/24/2022
Features
If there is a link failure after the rst step of a TO (the pick step), the data saved last is retrieved again by the system.
After you log on using the same username, the system automatically displays the destination data screen.
A different user can continue processing a TO that could not be nished due to link failure by choosing a transaction
identi ed by the TO number, such as Putaway by Transfer Order . A warning message informs the user that the TO is
being processed by another user.
If only certain items were saved during the pick step, you can con rm the second step (the transfer step) for the
respective items and continue processing the other items.
You can also use transactions LM03 ( Putaway by TO ) and LM05 ( Picking by TO ) to enter the source screen of the
speci c TO, add additional TO items to the list and only then move to the destination screen.
User Exits
Use
User exits offer you the option of enhancing existing functions according to your personal requirements.
See Also:
User Exit Screens
Veri cation with User Exit
Sorting Using the User Exit
Printing Using the User Exit
Deactivating Function Codes with the User Exit
Adding Function Keys to Screens
User Exit Screens
Use
The RF solution supports the two screen formats (8x40/16x20) that are offered by most manufacturers of RF devices. The user
exit function enables you to display other elds, according to your particular requirements, and also to implement other screen
formats.
Features
Fields
You can add elds that are available through standard transactions to the existing screens. Currently, these elds can only be
used for display purposes.
Also, you can eliminate elds, which are part of the RF solution, from the display.
Changing the Screen Format
The RF transactions use logical screen numbers. User exit screens are built upon existing screens, but have a separate ID
(physical screen number). This physical screen number is assigned to a logical screen and then implemented for users who are
4/24/2022
assigned to the same user exit class.
User exit screens are maintained in a separate user screen library.
The templates have been de ned as part of the RF screen management environment in order to help the user with the
development and logic of the speci c screens. These screens are called "dummy" screens.
Changing the Screen Layout on Runtime
To change the screen layout on runtime, use the following screen layout modules:
MODULE DISABLE_PB
MODULE SPECIAL_FIELD_OUTPUT
MODULE SET_CURSOR
Screen Selection in RF
The screens in the radio frequency transactions are divided into the following two main groups:
Source information screens
Destination information screens
In each group, the screens are chosen dynamically, according to transfer order properties, such as activity and storage unit
management.
De ning a Screen
Use
You can either create a new screen or copy an existing one.
Procedure
Creating a New Screen
Enter the program SAPLXLRF or SAPLXLHU in the screen painter.
 Note
To nd out which program you have to enter, enter the program SAPLLMOB and the dummy screen number 1xxx in the
screen painter. The Flow Logic of the dummy screen contains a call for the customer-subscreen in which the respective
program (SAPLXLRF or SAPLXLHU) is included.
Copying a Screen
1. Enter the program SAPLLMOB and a screen number.
2. Choose Element List and delete the last eld, the "OK_CODE".
3. Choose Subscreen in the tab page Attributes in Screen type .
4. Save your data entries under the relevant development class in the customer's namespace.
4/24/2022
Assigning a Screen
Procedure
1. In Customizing for Logistics Mobile Data Entry De ne Screen Management, create a new table record to assign the
new user screen to a logical screen for this user exit version. Ensure that you enter a number other than 0 in the Variant
eld.
 Recommendation
We recommend that the user exit screens start with a number from 3-9 inclusive since:
8x40 screens are numbered 0xxx
Dummy screens are numbered 1xxx
16x20 screens are numbered 2xxx
2. In Customizing for Logistics Mobile Data Entry RF Queue Management Assign Processor to Queues, assign users to
the variant.
3. Use the CMOD transaction to create a project for the screen.
 Recommendation
We recommend that you start the project name with one of the letters X, Y, or Z, followed by four digits that
represent the screen number used.
4. Insert a descriptive text after you have created the project.
5. Choose Continue.A dialog box appears.
6. Choose Local Object and save your entries.
7. Choose Enhancement. A new screen appears. Enter the enhancement name MWMRFxxx and save your entries. Make
sure that you include for xxx the last three digits of the logical screen number.
8. Activate the project using the transaction CMOD.
9. In the screen painter, enter the program SAPLLMOB and the dummy screen number 1xxx. From the Flow Logic tab of the
dummy screen, call up the module DATA_TO_EXIT0xxx, open the customer function, and go to Include. Do the same
for the module DATA_FROM_EXIT0xxx.
10. Enter the data that is entered into the screen through the function (note the import parameters). You need to execute
the same step for the structure of the data that returns from the screen through the function (note the export
parameters).
11. You can add up to four veri cation elds by lling in the table O_VERIFICATION_ERRORS (internal table). You can
de ne up to four elds on the screen that you can check any way you wish. If an error occurs during the check, you should
update this internal table with the appropriate eld name. The function reports a known error message
Error in field verification (which the user updated in the internal table).
Veri cation with User Exit
Use
Mobile Data Entry supports the following four types of veri cation:
4/24/2022
Storage bin
Storage unit number
Material
Quantity
To be able to verify other elds, the system also provides a general veri cation entry. You can use this veri cation to meet
individual requirements, such as veri cation of batches.
Procedure
1. Create a new screen.
2. In the screen painter, enter the program SAPLLMOB and one of the dummy screen numbers 1xxx.
3. Enter the module DATA_FROM_EXIT0xxx on the Flow Logic tab of the dummy screen, open the customer function, and
access the Include.
4. Fill in the internal table O_VERIFICATION_ERRORS with up to four veri cation elds. You can de ne up to four elds on
the screen that you can program according to your speci c requirements.
 Note
If an error is found in the veri cation checks, the system requires the user to update this internal table with the eld
names. The error message Error in field verification (which the user updated in the internal table)
appears.
Sorting Using the User Exit
Use
Mobile Data Entry supports two different sorting possibilities for system-guided transfer order processing:
Sorting without de ning a user exit
Sorting by different sort criteria with the help of a user exit
Both options can be used in the following transactions, but we strongly recommend that you implement the user exit only in the
interleaving transactions. In the other system-guided transactions, the sorting de ned in the user exit is not re ected properly
in the RF monitor .
System-guided putaway: LM04 (Report: RLMOB005)
System-guided picking: LM07 (RLMOB008)
System-guided pick and pack: LM45 (RLMOB045)
Posting change: LM11 (RLMOB010)
System-guided interleaving: LM57 (RLMOB005, RLMOB008)
4/24/2022
Interleaving by storage unit: LM56 (RLMOB001, RLMOB008)
Procedure
Sorting Without a User Exit
In the system-guided RF transactions, if you do not de ne a user exit, the system selects your transfer orders by priority and
then by creation date and time (the same method of sorting as that of the RF monitor)
Sorting with the Help of a User Exit
Use user exit function EXIT_SAPLLMOB_061.
If you use this function for interleaving, the following parameters will be imported:
Last storage bin
Queue
Activity
To use the user exit, use the enhancement name MWMRFSSG.
As an additional selection criterion, you want the system to select a transfer order for picking with a source storage bin close to
the destination storage bin of the preceding transfer order for putaway.
If you do not de ne your own user exit in this function, the system selects the transfer order for picking only according to the
queue assignment and the standard sorting mentioned above.
If you use this function for any other system-guided transaction, only the parameter for the activity will be imported.
The function returns the transfer order number.
If you use the user exit to change the sorting, the sorting will not correspond to the sorting in the RF monitor.
Printing Using the User Exit
Use
Mobile Data Entry supports the printing of different label types, such as shipping and handling unit labels. You can use the print
pushbuttons in the respective transaction by creating your own user exit function module, which is called from the
LE_MOB_PRINTfunction module.
4/24/2022
Procedure
1. Choose the function LE_MOB_PRINT.
2. Change the status eld to indicate that you created your own user exit in order to print labels. If the user exit is not
activated, you receive an error message upon using the print pushbuttons.
Result
Two parameters, the ok_codeand the parameter of the object to be printed, will be passed to the user exit function. The
ok_codede nes which pushbutton has been selected and the second parameter contains the object ID.
Deactivating Function Codes with the User Exit
Use
Using the user exit EXIT_SAPLLMOB_222, you can deactivate function codes in the delivery header screen.
Procedure
Activate the user exit using the enhancement name MWMRFCOD and clear the output parameter O_ENABLED.
Result
The corresponding button still appears on the delivery header screen, but is deactivated.
Adding Function Keys to Screens
Use
You can add function keys to the user exit screens of the existing screens.
On the screens, you can use one more function key. In the respective user exit screen, you can display the pushbutton and
assign to it the function code USRF in the GUI status, which corresponds to the function key Shift+F1.
Procedure
De ne the functionality of the function key in the user exit function EXIT_SAPLLMOB_077.
Cross-Docking (LE-WM-DCK)
Purpose
In today’s warehouse environment, customers aim to handle materials more efficiently and minimize unnecessary material
double-handling to reduce cycle times, inventory and handling costs. Maximizing cross-docking utilization is one way of achieving
this goal.
SAP’s Cross-Docking extends existing warehouse functionality to the realm of cross-docking.
Integration
4/24/2022
Logistics Execution (LE)
Cross-Docking is integrated with Logistics Execution through an interface (package LEINT). In future releases, Cross-Docking
will be fully integrated into Logistics Execution , eliminating the need for this interface.
Shipping(LE-SHP)
Cross-Docking is integrated with the LES component for Shipping . When cross-docking transfer orders are created and
con rmed, the relevant deliveries are updated.
Warehouse Management (LE-WM)
Cross-Docking is fully integrated into Warehouse Management (WM) .
Yard Management (LE-YM)
Cross-Docking is integrated with Yard Management (YM) .Before creating a cross-docking decision, YM checks if a location can
be scheduled. If so, when the decision is saved, YM creates the corresponding scheduling activity.
Features
Cross-Docking provides the following features:
Planned and Opportunistic Cross-Docking
Cross-Docking enables you to create cross-docking decisions prior to the arrival of incoming stock and release of the outgoing
delivery or transfer requirement, as well as after goods have physically arrived at the warehouse. These decisions can be
created in contravention of strict FIFO, according to a tolerance duration determined in customization. For more information,
see Planned Cross-Docking and Opportunistic Cross-Docking .
One-Step and Two-Step Cross-Docking
Cross-Docking enables goods to be either be directly moved between the goods receipt and goods issue areas, or rst moved
from goods receipt to a cross-docking storage type, before being moved to the goods issue area. For more information, see
Cross-Docking Execution .
Cross-Docking Decision Optimization
Cross-Docking determines the optimal cross-docking decisions and proposes these decisions. You can either create these
decisions in the background or view the decisions and decide whether or not to accept them. For more information, see Cross-
Docking Decision Optimization .
Monitoringand Response Tools
Cross-Docking enables you to monitor cross-docking in the warehouse, including cross-docking decisions and their statuses. You
can also use the monitor to invoke methods such as cross-dock planning. For more information, see Cross-Docking Monitor .
Cross-Dock Planning Tool
From the monitor, you can also invoke the cross-dock planning tool, a tool that enables you to analyze inbound and outbound
documents and manually create your own cross-docking decisions. The tool also ensures that doors can be scheduled for the
documents of any created decisions. For more information, see Cross-Dock Planning Tool .
Alert and Troubleshooting Tools
4/24/2022
Cross-Docking provides information on actual and arising problematic situations in the warehouse, which are related to cross-
docking, and enables you to handle exceptions. For more information, see Cross-Docking Alert Monitor .
Constraints
1. Opportunistic cross-docking may not always work in a non-RF environment.
2. The cross-docking of mixed pallets is not supported.
3. Cross-docking only applies to available stock, and not stock in quality control, returns stock or blocked stock.
Cross-Docking Decision
De nition
A cross-docking decision is a decision that either establishes a cross-docking link between a planning document and candidate
document item, or designates a document or item for cross-docking , without establishing a link.
Use
Linking Planning and Candidate Document Items
Decisions linking planning and candidate document items can be created as part of the planned cross-docking or opportunistic
cross-docking processes. They can be created in the following ways:
Manually created by the warehouse manager
You can plan cross-docking and establish links between documents via the Plan cross-docking monitor method . For
more information, see Creating a Cross-Docking Plan .
You can also run the cross-dock planning in the background, accepting cross-docking decisions recommended by the
system. For more information, see Cross-Docking Decision Optimization .
Automatically created by the system
During the creation of a transfer order (TO) for an inbound or outbound planning document that has not been linked with
a candidate document, the system establishes the link by searching for appropriate open TOs connected to candidate
documents. For more information, see Opportunistic Cross-Docking .
Designating Documents or Items for Cross-Docking
You can designate both inbound and outbound documents or items for cross-docking via the Designate for cross-docking
monitor method.
In the case of an inbound document/item, the designation results in the creation of a putaway TO, at goods receipt for the
inbound document/item, with the cross-docking storage type as its destination.
In the case of an outbound document/item, if goods receipt is performed for an inbound document/item containing the
required outbound material, the putaway TO is created to the cross-docking storage type or goods issue area. The designation
does not, however, prevent the creation of any picking TO from storage to meet the outbound material requirements.
For more information, see Designating a Document or Item for Cross-Docking .
 Note
4/24/2022
You can cancel cross-docking decisions via the Cancel monitor method. For more information, see Cross-Docking Monitor
Methods .
Structure
A cross-docking decision comprises of the following:
Decision number
Decision type
Inbound and/or outbound document(s) and item(s)
Document type
Decision status
Decision quantity
Inbound processed quantity
Inbound con rmed quantity
Outbound processed quantity
Decision unit of measure
Decision origin
Material data, including material number, plant, storage location and stock category
Outbound document warehouse movement type
Example
A warehouse is customized so that two-step cross-docking is forced.
The warehouse manager links item 10 of inbound delivery 180002452 with item 20 of outbound delivery 80001308 (4 loads).
Each load represents a pallet containing 10 pieces.
The decision elds include the following values:
Doc. Item Doc. Item Status Dec. Qty Inb. Proc. Inb. Cnf. Out. Proc. UoM
Qty Qty Qty
180002452 10 80001308 20 Open 40 PCE
After delivery 180002452 arrives and goods receipt is performed, a TO to take 40 pieces from the goods receipt area and put
them away in the cross-docking storage type is created. The decision elds are now as follows:
Qty Qty Qty
180002452 10 80001308 20 Inbound 40 40 PCE

complete
4/24/2022
At this point, release of delivery 80001308 will not trigger the creation of a picking TO since there is no inbound con rmed
quantity.
After the putaway TO is con rmed, the decision is updated as follows:
Qty Qty Qty
180002452 10 80001308 20 Inbound 40 40 40 PCE

complete
After delivery 80001308 is released, a TO to pick 40 pieces from the cross-docking storage type and take them to the goods
issue area is created. The decision now looks as follows:
Qty Qty Qty
180002452 10 80001308 20 Completed 40 40 40 40 PCE
Planning Document
De nition
A planning document is a document for which cross-docking opportunities are analyzed.
Use
You can create a cross-docking decision by establishing a link between a planning document item and a candidate document
item.
For more information, see Creating a Cross-Docking Plan .
Integration
Planning documents can be inbound/outbound deliveries or transfer requirements.
Example
In the planned cross-docking process, if the planning direction is Inbound to Outbound , the inbound documents are the planning
documents containing items from which outbound document items are to be ful lled.
Candidate Document
De nition
A candidate document is a document with an item that has potential to be linked to an item in a planning document , so as to
create a cross-docking decision .
Use
4/24/2022
You can create a cross-docking decision by establishing a link between a planning document item and a candidate document
item.
For more information, see Creating a Cross-Docking Plan .
Integration
Candidate documents can be inbound/outbound deliveries or transfer requirements.
Example
In the planned cross-docking process, if the planning direction is Inbound to Outbound , the outbound documents, which contain
items to be ful lled from the inbound documents, are the candidate documents.
Release Time
De nition
The release time for an outbound document is the time by which you to plan to create a transfer order for the document,
enabling the document to be released for execution.
Use
You can enter a release time for a group when creating the group and assigning to it outbound deliveries via the monitor. For
more information, see Assigning Outbound Deliveries to a Group .
If you do not enter a release time for a group, the system uses the default release time as de ned in Customizing for
LogisticsExecution Warehouse Management Cross-Docking General Settings Maintain Warehouse Level Settings.
In this Customizing activity, you de ne the release time in terms of an amount of time before the outbound document date and
time reference.
The release time has the following uses:
1. It is used by Yard Management as the beginning time of the time frame for which the system searches for available
locations to schedule for the outbound document at the time the cross-docking decision is created.
For more information, see System Scheduling in the SAP Library for Yard Management (LE-YM) .
2. Violation of the release time triggers a yellow alert in the alert monitor.
For more information, see Alerts Provision .
Latest Release Time
De nition
The latest release time for an outbound document is the latest time by which you must create a transfer order for the
document, enabling the document to be released for execution.
The latest release time is also the latest point in time until which transfer order (TO) creation will be delayed.
4/24/2022
Use
You can enter a latest release time for a group when creating the group and assigning to it outbound deliveries via the monitor.
For more information, see Assigning Outbound Deliveries to a Group .
If you do not enter a latest release time for a group, the system uses the default latest release time as de ned in Customizing
for LogisticsExecution Warehouse Management Cross-Docking General Settings Maintain Warehouse Level Settings.
In this Customizing activity, you de ne the latest release time in terms of an amount of time before the outbound document
date and time reference.
The latest release time has the following uses:
1. In the case of planned cross-docking , if the outbound document is released prior to the con rmation of a TO for the
inbound document, the system delays creation of picking TOs (from storage to the goods issue area) for the outbound
document until the latest release time.
2. Violation of the latest release time triggers a red alert in the alert monitor.
For more information, see Alerts Provision .
Planned Cross-Docking
Purpose
Cross-Docking enables you to generate cross-docking decisions priorto the actual arrival of incoming stock and release of
outgoing documents (i.e. prior to transfer order creation).
The process differs, depending on:
Whether the cross-docking decisions involve linking document items or designating a document or item for cross-docking
Whether the inbound TO is con rmed before or after the release of the outbound document (in the case of decisions linking
items)
Whether the document or item is an inbound or outbound document or item (in the case of cross-docking designation)
Prerequisites
Inbound and outbound deliveries/transfer requirements (TRs) are created in the system.
The documents have some quantity of stock available for picking or putaway.
a. Maintained warehouse level settings in Customizing for Logistics Execution → Cross-Docking → Maintain Warehouse Level
Settings. In particular, you have entered the cross-docking storage type, and de ned a time reference, planning time window
and default latest release time.
b. De ned warehouse movement types as being relevant for cross-docking inCustomizing for Logistics Execution → Cross-
Docking → De ne Cross-Docking Relevancy for Movement Types
c. Ensured that the Consider Pre-Alloc. Stock indicator is not set in Customizing for Logistics Execution → Warehouse
Management → Activities → Transfers → De ne Movement Types
4/24/2022
d. Ensured thatthe cross-docking storage type is excluded from the stringent FIFO picking strategy in Customizing for Logistics
Execution → Warehouse Management → Strategies → Picking Strategies → De ne Strategy for “Stringent FIFO”
e. Entered1(for inbound documents) or2(for outbound documents) in the TO Creation eld (Screen Control) for your warehouse
inCustomizing for Logistics Execution → Warehouse Management → Activities → Transfers → De ne Movement Types.
We also recommend that you ensure thatthe cross-docking storage type is excluded from every storage type search sequence
in Customizing for Logistics Execution → Warehouse Management → Strategies → Activate Storage Type Search , to avoid a
situation in which stock for cross-docking is picked for other deliveries.
Process Flow
Decisions Linking Planning and Candidate Document Items
Inbound Outbound
You do any of the following:
Create a cross-docking plan consisting of one or more cross-docking decisions involving

linked inbound and outbound document items. For more information, see Creating a Cross-
Docking Plan .
Create the system-recommended decisions in the background. For more information, see
Cross-Docking Decision Optimization .
The stock arrives at the goods receipt area You try to create a TO for the outbound
(storage type 902) and you post goods document (i.e. release the outbound
receipt, or use the partial posting document).
functionality.
You create a putaway TO for each of the The system fetches the previously created
document items. decisions according to the document items.
During TO creation, the system does the

following:
a. Fetches the previously created decision

according to the document item
b. Determines the destination as:
The cross-docking storage type in a case

where two-step cross-docking is forced
The goods issue area (storage type 916) in

all other cases
4/24/2022
Inbound Outbound
You try to create a TO for the outbound The system delays creation of picking TOs
document (i.e. release the outbound (from storage to the goods issue area) for
document). the outbound document as long as the
latest release time has not yet arrived.
If the goods to be cross-docked are at the
cross-docking storage type, the system If the relevant inbound document items
automatically creates the TO from the arrive before the latest release time, you
cross-docking storage type. perform goods receipt and create a
putaway TO for each item. During TO
creation, the system determines the
destination as:
The cross-docking storage type in the case

where two-step cross-docking is forced.
Once the goods have been con rmed at the
cross-docking storage type, the system will
not delay the creation of a picking TO, and
you can create a picking TO for the
outbound document. When you create the
picking TO, the system automatically
creates it from the cross-docking storage
type.
The goods issue area in all other cases
Decisions Designating Documents or Items for Cross-Docking
Inbound Document/Item Designated for Outbound Document/Item Designated for

Cross-Docking Cross-Docking
You designate a document or item for cross-docking via the cross-docking monitor.
For more information, see Designating a Document or Item for Cross-Docking .
When the inbound document items arrive at When inbound document items containing
the warehouse, you perform goods receipt the same materials as the relevant
and create a putaway TO for each of the outbound items arrive, you perform goods
items. receipt and create a putaway TO for each
item. During TO creation, the system
determines the destination as:
During TO creation, the system does the
following: The cross-docking storage type in the case
where two-step cross-docking is forced.
a. Fetches the previously created decisions
Once the goods have been con rmed at the
b. Determines the destination as the cross- cross-docking storage type, you can create
docking storage type a picking TO for the outbound document.
When you create the picking TO, the system
automatically creates it from the cross-
A warehouse worker moves the relevant docking storage type.
goods to the cross-docking storage type
The goods issue area in all other cases
and con rms execution.
You can manually create a picking TO from

The system does not prevent the creation
the cross-docking storage type to the goods
of a picking TO from storage to meet the
issue area.
outbound material requirements.
Cross-Docking Decision Optimization

4/24/2022
Use
As part of the cross-dock planning process, the system optimizes cross-docking decisions linking inbound and outbound
document items.
Features
The system optimizes cross-docking decisions so that:
The maximum number of loadsare cross-docked
The minimum number of links are established between deliveries/TRs, shipments or groups
 Note
You can create your own optimization algorithm using method PLANNING_DOCUMENTS_MATCH of Add-In
LXDCK_CROSS_DOCK . For more information, see Business Add-Ins .
This optimization is performed according to one of the following optimization levels
Delivery/TR
Shipment
Group
The selected optimization level can in uence the system-recommended cross-docking decisions.
The following shipments and deliveries are within the cross dock planning time window:
Inbound Outbound
Delivery 180003243 Shipment 1245 Delivery 80005432
BIKE x 10 Loads BIKE x 9 Loads
Delivery 180003244 Delivery 80005433
Delivery 180003245 Delivery 80005434
Shipment 1249 Delivery 80005500
BIKE x 10 Loads
Delivery 80005501
BIKE x 5 Loads
If the optimization level is set at Shipment , the system will create a cross-docking decision linking inbound deliveries
180003243, 180003244 and 180003245 (18 bike loads) with outbound shipment 1245 (16 bike loads), and not with outbound
shipment 1249, which has only 15 bike loads.
If the optimization level is set at Delivery/TR , the system will create cross-docking decisions linking the deliveries as follows:
4/24/2022
Inbound delivery 180003243 with outbound delivery 80005500 ( shipment 1249 )
Inbound delivery 180003244 with outbound delivery 80005501( shipment 1249 )
Inbound delivery 180003245 with outbound delivery 80005444 ( shipment 1245 )
 Note
You select the optimization level in the cross-docking monitor selection screen. For more information, see Opening
the Cross-Docking Monitor .
You can either prompt the system to create the decisions in the background, or you can view the system proposal and either
accept the decisions in their entirety, or adjust them manually according to your requirements.
Activities
Creating the System-Recommended Decisions in Background
1. From the Cross-Docking: Selection screen of the cross-docking monitor, you choose .
2. The system creates cross-docking decisions linking inbound and outbound document items, according to the
optimization algorithm.
3. You can view these decisions in the cross-docking monitor ( Decision object class).
Opportunistic Cross-Docking
Purpose
In the opportunistic cross-docking process, the system generates a cross-docking decision during the process of TO creation (
after the arrival of the incoming stock or release of the outgoing document).
 Note
Opportunistic cross-docking involves one-step cross-docking execution only.
Prerequisites
1. Enabled opportunistic cross-docking in Customizing for Logistics Execution Warehouse Management Cross-
Docking General Settings Maintain Warehouse Level Settings
2. De ned warehouse movement types as being relevant for cross-docking in Customizing for Logistics
Execution Warehouse Management Cross-Docking General Settings De ne Cross-Docking Relevancy for Movement
Types
3. Ensured that the Consider Pre-Alloc. Stock indicatoris not set in Customizing for Logistics Execution Warehouse
Management Activities Transfers De ne Movement Types
4. Entered 1(for inbound documents) or 2(for outbound documents) in the TO Creation eld (Screen Control) for your
warehouse inCustomizing for LogisticsExecution Warehouse Management Activities Transfers De ne Movement
Types
4/24/2022
5. Enabled one of the following, in the case of opportunistic cross-docking for inbound documents (HU-managed
environment):
¡Partial posting goods receipt at movement type level in Customizing for Logistics Execution Warehouse
Management Interfaces Shipping De ne Shipping Control De ne Shipping Control at the Movement Type
Level (enter 4in eld)
¡Posting goods receipt before TO creation in Customizing for Logistics - General Handling Unit
Management Basics Delivery De ne Sequence of Transfer Order – Goods Receipt
6. Enabled posting goods receipt before TO creation in Customizing for Logistics - General Handling Unit
Management Basics Delivery De ne Sequence of Transfer Order – Goods Receipt , in the case ofopportunistic cross-
docking for outbound documents
7. Entered Bin the Method eld (Blocking logic) for your warehouse in Customizingfor Logistics Execution Warehouse
Management Master Data De ne Control Parameters for Warehouse Number
8. Ensured that automatic con rmation is not set (HU-managed environment only) by doing at least one of the following in
Customizing for LogisticsExecution Warehouse Management Activities Con rmation Storage Type:
Setting the Con rmation putaway indicator for the goods issue storage type (e.g. 916)
Setting the Con rm stck removal indicator for the goods receipt storage type (e.g. 902)
Process Flow
Inbound Document Outbound Document
An inbound document is created. An outbound document is released.
The stock arrives at the goods receipt area

(storage type 902) and goods receipt is
performed if posting is allowed before TO
creation.
You create a putaway TO for each of the document items.
During TO creation, the system checks whether a cross-docking decision already exists for
each document item.
If a decision already exists, see step 3 onwards in Planned Cross-Docking .
4/24/2022
Inbound Document Outbound Document
If a decision does not already exist, the If a decision does not already exist, the
system analyzes whether there are any system analyzes whether there are any
available cross-docking opportunities. available cross-docking opportunities:
1. a. The system searches for any 1. a. The system searches for any
open picking TO items from storage open putaway TO items from the
to the goods issue area (storage goods receipt area (storage type
type 916), according to the following 902) to storage, according to the
criteria: following criteria:
a. i. TO item status is not a. i. TO item status is not

con rmed and TO item is con rmed and TO item is
not locked by any resource. not locked by any resource.
b. ii. TO item contains the b. ii. TO item contains the

same material, quantity, same material and a lower
plant and storage location or same quantity as the
(usually in terms of full picking TO item to be
loads) as the putaway TO created.
item to be created.
c. iii. The stock category of the
c. iii. The stock category of the TO item is
TO item is Available Stock .
Available Stock .
d. iv. The handling unit (HU) of
2. b. The system evaluates further the TO item is posted (in
criteria, such as FIFO and batch HU-managed environment
requirements. only)
2. b. The system evaluates further

criteria, such as FIFO and batch
requirements.
If the system nds a suitable picking TO If the system nds a suitable putaway TO
item, it does the following: item, the system does the following:
1. a. Cancels the picking TO item 1. a. Cancels the putaway TO item
2. b. Creates a putaway TO item to the 2. b. Creates a picking TO item to the

goods issue area goods issue area, with the source of
the cancelled putaway TO item
3. c. Updates the outbound document,
(goods receipt area) as its source
for which the picking TO item was
cancelled, with the new cross- 3. c. Updates the inbound document,
docking putaway TO item for which the putaway TO item was
cancelled, with the new cross-
docking picking TO item
The newly-created putaway/picking TO item is now connected to both the inbound and
outbound documents.
Effect of Document Changes on Cross-Docking Decisions

Type of Change Document Type Effect What You Should Know
Deletion Delivery The statuses of all of the A document can be deleted as

document’s cross-docking long as processing on it has not
TR decisions are set to yet commenced.
Cancelled .
4/24/2022
Type of Change Document Type Effect What You Should Know

Change in quantity Delivery When quantity is reduced, the A document’s quantities can be
quantities of the document’s changed even after processing
cross-docking decisions are on it has commenced.
reduced so that the total open
quantity of decisions (decision
TR
qty minus processed qty) does
not exceed the quantity left to
pick/putaway.
Change in material, plant or Delivery The statuses of all of the Changes are not allowed after
storage location document’s cross-docking delivery processing has
decisions are set to commenced.
Cancelled .
TR Changes are not allowed at all.
Change in stock category Delivery If stock category is changed to

anything but
Available Stock , the
statuses of all of the
TR
document’s decisions are set to
Cancelled .
Change in source or destination TR If you enter a value in the

storage type destination storage type and bin
of a picking TR, or the source
storage type and bin of a
putaway TR, the statuses of all
of the document’s decisions are
set to Cancelled .
Cross-Docking Execution
Purpose
Warehouse workers execute transfer orders (TOs) based on cross-docking decisions in exactly the same way as they would
execute standard TOs, either via desktop computers or RF devices.
Cross-docking execution can be performed in one or two steps. For more information, see:
One-Step Cross-Docking
Two-Step Cross-Docking
Process Flow
1. Cross-docking decisions are created before ( planned cross-docking ) or during ( opportunistic cross-docking ) TO
creation.
2. Warehouse workers execute the TOs.
Use
Cross-Docking enables one-step cross-docking, whereby goods to be cross-docked are moved directly from the goods receipt
area to the goods issue area.
4/24/2022
Prerequisites
Ensured that automatic con rmation is not set (HU-managed environment only) by doing at least one of the following in
Customizing for Logistics Execution → Warehouse Management → Activities → Con rmation → Storage Type:
Setting the Con rmation putaway indicator for the goods issue storage type (e.g. 916)
Setting the Con rm stck removal indicator for the goods receipt storage type (e.g. 902)
Enabled one of the following (in the case of an HU-managed environment):
Partial posting goods receipt at movement type level in Customizing for Logistics Execution → Warehouse Management →
Interfaces → Shipping → De ne Shipping Control → De ne Shipping Control at the Movement Type Level (enter4in eld)
Posting goods receipt before TO creation in Customizing for Logistics → General → Handling Unit Management → Basics →
Delivery → De ne Sequence of Transfer Order – Goods Receipt
If you do not perform prerequisite 2, cross-docking execution will be implemented in two steps.
Activities
The system creates a transfer order (TO) from the goods receipt area (storage type 902) to the goods issue area (storage type
916) in the following cases:
a. In the opportunistic cross-docking process
b. In the planned cross-docking process where:
i. You have not forced two-step cross-docking in Customizing for Logistics Execution → Warehouse Management → Cross-
Docking → General Settings → Maintain Warehouse Level Settings
ii. The inbound load’s quantity is not greater than the open decision quantity; and
iii. The decision links inbound and outbound document items or designates an outbound document or item for cross-docking
When the TO is con rmed, the inbound and outbound documents are updated with the actual pick and putaway quantities.
The cross-docking decision does not track differences.
In case the TO reference is handling unit (HU) managed, the HU is assigned to the outbound document during con rmation of
the cross-docking TO.
4/24/2022
Use
Cross-Docking enables two-step cross-docking, whereby goods to be cross-docked are rst moved from the goods receipt (GR)
area to a cross-docking storage type. The goods are subsequently moved to the goods issue (GI) area upon release of the
outbound document.
Activities
You do any of the following:
a. Create a cross-docking decision linking inbound and outbound document items, after having forcedtwo-step cross-docking in
Customizing for Logistics Execution → Warehouse Management → Cross-Docking → Maintain Warehouse Level Settings
b. Create a cross-docking decision linking inbound and outbound document items, without having forced two-step cross-docking,
in a case where the inbound load’s quantity is greater than the open decision quantity
c. Designate an outbound document for cross-docking, after having forced two-step cross-docking
d. Designate an inbound document for cross-docking
4/24/2022
The system creates the following transfer orders (TOs):
A putaway TO from the GR storage type to the cross-docking storage type
A picking TO from the cross-docking storage type to the goods issue storage type (except in the case of 1d. above)
For more information on the exact process of transfer order creation in the case of two-step cross-docking, see Planned Cross-
Docking .
When the putaway TO is con rmed, the decision's inbound con rmed quantity is updated. This quantity indicates to the
outbound document that stock waits in the cross-docking area.
When the picking TO is con rmed, no additional document is updated and the con rmation is like that of a standard picking TO
Cross-Docking Monitor
Purpose
4/24/2022
The cross-docking monitor is a tool for keeping warehouse managers constantly up-to-date as to the current situation
regarding cross-dockingand to enable them to plan cross-docking and initiate appropriate responses in light of this situation.
Features
Provision of Information on LES and YM Objects
The cross-docking monitor displays current information on LES and Cross-Docking objects, including inbound and outbound
deliveries and transfer requirements (TRs), document items, shipments, groups and cross-docking decisions.
Provision of Methods
The cross-docking monitor provides methods with which you can initiate managerial actions appropriate to the situation in the
warehouse. For more information, see Cross-Docking Monitor Methods.
Opening the Cross-Docking Monitor
Use
Before you open the cross-docking monitor, you can determine the following:
The actual warehouse to monitor/plan cross-docking
The next screen to be displayed (monitor vs. cross-dock planning tool)
The cross-dock planning mode (background vs. manual)
The planning direction (in the case where you navigate directly to cross-dock planning tool)
The optimization level for cross-docking decision optimization
The objects and sub-object classes to be displayed when the monitor opens.
Prerequisites
You have sufficient authorization to open the monitor for the selected warehouse.
Procedure
From the SAP Easy Access menu, choose Logistics → Logistics Execution → Cross-Docking → Cross-Docking Monitor.
The Cross-Docking: Selection screen appears.
In the Warehouse eld, enter the number of the warehouse for which you want to monitor and plan cross-docking.
You can set a default warehouse for which the monitor will open by doing the following:
From the menu, choosing System → User Pro le → Own Data.
4/24/2022
Entering the following parameter and value:
Parameter ID: LXDCK_LGNUM
Parameter value: warehouse number
If you have set a default warehouse, or have only de ned one warehouse, the warehouse number automatically appears in the
Warehouse eld.
From the Optimization Level drop-down list, select an optimization level based on which the system does the following:
Creates planned cross-docking decisions in the background (see step 4 below)
Proposes links between documents (see step 5b. below)
For more information, see Cross-Docking Decision Optimization .
If you want the system to perform cross-dock planning in the background, choose .
The system creates planned cross-docking decisions according to the optimization algorithm.
If you want to skip the monitor and navigate straight to the cross-dock planning tool :
a. Determine the planning direction:
i. If you want to set inbound documents as the planning documents and outbound documents as the candidate documents ,
select Inbound to Outbound .
ii. If you want to set outbound documents as the planning documents and inbound documents as the candidate documents,
select Outbound to Inbound .
b. Choose .
The cross-dock planning tool opens, with the inbound and outbound documents and system recommended links between
documents being displayed. For more information, see Creating a Cross-Docking Plan .
If you want to open the monitor:
a. You can restrict the objects to be monitored by choosing one or more tab cards relating to object classes and entering
selection criteria.
The selected objects will be displayed in the monitor when it opens.
If you want to add further selection criteria, choose .
If you want to display a previously saved variant of the selection criteria, choose .
If you want to clear any entered values from all of the search criteria elds, enter .
b. If you also want sub-object classes for a particular object to be displayed when the monitor opens, select Expand object in the
object class’ tab card.
4/24/2022
c. Execute.
The monitor opens, displaying thehierarchy treeandALV
The following is displayed in the hierarchy tree:
All objects that meet the selection criteria, if entered.
The sub-object classes of these objects, if you elected to expand the objects pursuant to step 6b. above.
Objects that meet the selection criteria are also displayed in the ALV.
If you entered selection criteria for more than one object class, the objects of the object class that appears furthest down the
hierarchy tree are displayed.
If you elected to expand the objects pursuant to step 6b. above, the objects of the sub-object class that appears furthest down
the hierarchy tree are displayed.
If you did not enter any selection criteria, the warehouse object only is displayed in both the hierarchy tree and the ALV.
Cross-Docking Monitor User Interface

The cross-docking monitor has a user-friendly interface which utilizes Drag&Dropfunctionality. The interface comprises of the
following two areas:
Hierarchy tree
ALV (SAP List Viewer)
Hierarchy Tree
The object hierarchy tree, located on the left side of the monitor, is a navigation area consisting of the various object classes,
associated objects and their attributes. Using the tree, you can display the object classes and objects, as well as perform
methods on them.
ALV
The ALV, located on the right side of the monitor, contains all elds of the object records and can display records of all retrieved
objects simultaneously. This area is synchronized with the object hierarchy tree. You can also perform methods from the ALV
tool bar.
 Note
For more information on the ALV, see the SAP Library for SAP NetWeaver Components SAP Web Application Server Basis
Services/Communication Interfaces (BC-SRV) SAP List Viewer (BC-SRV-ALV) .
See Also:
Using Basic Monitor Functions
Cross-Docking Monitor Methods
Using Basic Cross-Docking Monitor Functions

4/24/2022
Function Result
Set monitor view parameters Your settings are saved and implemented.
Displaying objects in the hierarchy tree and ALV The node containing the target class expands, revealing its objects
and child object classes.
All objects and details for the target object class are displayed in
the ALV.
 Example
If you want to display the decisions of inbound delivery
180002963 , drag the inbound delivery 180002963 object on
to the Decision sub-object class.
Selecting objects in hierarchy tree The selected objects are highlighted.
Scrolling through objects You scroll up and down a page at a time, or to the extreme top or
bottom, depending on which icon you choose.
Invoking monitor methods Refer to Cross-Docking Monitor Methods .
Displaying object summary details The Details dialog box appears, displaying summary object
details.
Opening the cross-docking alert monitor The cross-docking alert monitor appears, displaying alerts for the
warehouse chosen for the cross-docking monitor.
Refreshing the display for an object class The display of the object class in the monitor is updated.
Refreshing the display for whole site The display of all object classes in the monitor is updated.
Refreshing the display for an object The display of the selected object in the monitor is updated.
Cross-Docking Monitor Methods
Use
The cross-docking monitor methods allow you to perform actions on a selected object or object class. Each method belongs to
one of two groups:
1. Display methods
Display information for the selected object
2. Maintenance methods
Enable you to perform actions that in uence object eld values
Prerequisites
You have de ned methods and object classes in Customizing for LogisticsExecution Warehouse Management Cross-
Docking Monitoring De ne Object Class Methods.
Features
You can invoke the methods either via the monitor hierarchy tree or the ALV tool bar.
4/24/2022
Invoking Methods Via the Hierarchy Tree
1. Display the relevant objects. For information on how this is done, see Using Basic Monitor Functions .
2. From the hierarchy tree, right-click one or more objects or an object class. A pop-up menu appears.
3. Choose an option from the pop-up menu.
Invoking Methods Via the ALV
1. Display the relevant objects.
2. From the ALV, select the row or rows corresponding to the objects on which you want to apply the method.
3. For some methods, you choose the relevant icon from the ALV tool bar.
4. For other methods, you choose or from the ALV tool bar and then an option from the pop-up menu.
Activities
Method Name ALV Icon Allowed Objects Description What You Should Know
Display details All Displays the Details This method is available

dialog box from the ALV tool bar
only.
Refresh objects All Updates the display of

selected objects
Select tree objects All Selects in the hierarchy This method is available
tree objects that have from the ALV tool bar
been selected in the ALV only.
Hide selected objects All Hides one or more

selected objects in both
the hierarchy tree and
ALV
Hide unselected objects All Hides one or more

unselected objects in
both the hierarchy tree
and ALV
Set as selection criteria All except Decision Sets one or more object This method can be
nodes as the selection used instead of
criteria for expanding Drag&Drop.
sub-object classes
Clear selection criteria All except Decision Discontinues the use of

object nodes as
selection criteria
Assign to group Outbound Delivery Enable you to create a Refer to Assigning

group and assign to it Outbound Deliveries to a
deliveries Group.
4/24/2022
Cancel Decision Cancels the selected Before canceling a

cross-docking decisions decision, the system
and scheduling gives you the option of
also canceling its related
scheduling.
Designate for cross- Inbound Delivery Designates selected Refer to Designating a

docking documents or items for Document or Document
Outbound Delivery
cross-docking Item for Cross-Docking
Inbound TR
Outbound TR
Inbound
Outbound
Inbound Delivery Item
Outbound Delivery Item
Inbound TR Item
Outbound TR Item
Inbound Item
Outbound Item
Modify Group Enables you to modify

the release date/time
and latest release
date/time of a group
Plan cross-docking Inbound Delivery Opens the cross-dock Refer to Opening the
planning tool, with the Cross-Dock Planning
Outbound Delivery
selected documents Tool
Inbound TR serving as the planning
documents
Outbound TR
Inbound
Outbound
Schedule Decision Schedules one or more The Scheduling results

selected decisions dialog box appears,
indicating whether or not
scheduling succeeded
for each of the selected
decisions.
Cross-Dock Planning Tool
De nition
The cross-dock planning tool is a tool that enables you to analyze the cross-docking opportunities for a selected population of
planning documents , and create cross-docking decisions .
Use
4/24/2022
You can access the cross-dock planning tool from the cross-docking monitor in one of two ways:
Directly from the monitor selection screen. For more information, see Opening the Cross-Docking Monitor .
Invoking the Plan Cross-Docking monitor method. For more information, see Opening the Cross-Dock Planning Tool .
Using the cross-dock planning tool, you can view the cross-docking decisions recommended by the system and either add them
to the plan or create your own decisions. The tool also provides a number of functions that provide assistance in creating cross-
docking decisions, including:
Changing the view resolution (document, item and shipment resolutions)
Showing the links between documents
Scheduling locations for cross-docking decisions
Structure
The cross-dock planning tool user interface comprises of the following areas:
Inbound and Outbound Document Areas
TheInbounddocument area is located on the top left side of the screen, with theOutbounddocument area being located on the
top right side. The inbound and outbound documents are identi ed as planning or candidate documents, depending on the
planning direction.
Both areas consist of the following parts:
ALV summarizing the main, relevant details of the documents and their loads
ALV tool bars, containing buttons for the main methods that can be used, including:
Displaying links between documents
Showing link-related information
Document items that do not contain at least one load (according to the palletization data of the material) are not displayed.
Selected Plan Area
TheSelected Planarea is located on the bottom of the screen, underneath the Inbound/Outbound document areas.
This area consists of the following parts:
ALV summarizing any cross-docking decisions that are added to the plan
ALV toolbar, containing buttons for plan-related methods such as:
Saving a decision to the plan
Deleting a decision from the plan
4/24/2022
Checking if scheduling is possible for a decision
The ALV methods for each of the aforementioned areas include regular ALV functions, such as sorting, ltering and changing
the layout.
Main Toolbar
The main toolbar is located at the top of the screen, above the Inbound and Outbound document areas. It contains buttons for
general methods such as:
Adding a decision to the plan
Recalculating the system recommendation
Changing the view resolution
Opening the Cross-Dock Planning Tool
Use
You can open the cross-dock planning tool via the cross-docking monitor.
 Note
You can also open the tool directly from the monitor selection screen,. For more information, see Opening the Cross-Docking
Monitor .
Procedure
ALV Hierarchy Tree
Display inbound or outbound document objects.
From the ALV, select one or more rows From the hierarchy tree, select one or more
corresponding to the documents that you objects corresponding to the documents
want to use as planning documents . that you want to use as planning
documents.
From the ALV tool bar, choose . From the hierarchy tree, right-click the icon
to the left of the object and then choose
Plan cross-docking from the pop-up menu.
If you have selected more than one object,

right-click the icon to the left of any of the
objects.
Result
The cross-dock planning tool opens.
See Also :
4/24/2022
Cross-Dock Planning Tool Functions
Creating a Cross-Docking Plan
Cross-Dock Planning Tool Functions
Use
Most of the cross-dock planning tool functions are accessed by choosing a pushbutton. In some cases, you must rstly select
one or more lines corresponding to reference documents before choosing the pushbutton.
Features
Pushbutton Icon Location Description
Main tool bar Adds the selected documents to the cross-

docking plan
Main tool bar Re-calculates cross-docking decisions

recommended by the system according to
the pool of selected documents
Main tool bar Changes the view to shipment resolution
Main tool bar Changes the view to document resolution
Main tool bar Changes the view to item resolution
Inbound/Outbound document area Displays the exact system-recommended

links between documents or document
items
Inbound/Outbound document area Displays the following additional

information:
Number of system-recommended links
The number of documents/items that the

system recommends be linked with the
document/item, after analyzing the whole
pool of selected planning documents
Number of system-recommended links for

a speci c candidate document
The number of documents/items that the

system recommends be linked with a
particular /item, after analyzing the
candidate document and the whole pool of
selected
Inbound/Outbound document area Hides the additional link information
Inbound/Outbound (Candidates) document Displays other candidate documents with

area items that can be linked to the planning
document items (in addition to the system-
recommended candidate documents)
4/24/2022
Pushbutton Icon Location Description
Inbound/Outbound (Candidates) document Reverts to displaying only those candidate

area documents with items that the system
recommends be linked to the planning
document items
Inbound/Outbound document area Opens a dialog box displaying the main

details for the selected
Selected plan area
documents/decisions
Inbound/Outbound document area Displays additional pushbuttons
Inbound/Outbound document area Hides the additional pushbuttons
Selected plan area Saves a cross-docking decision to the plan
Selected plan area Checks if location scheduling is possible

for the selected decisions
Selected plan area Deletes a cross-docking decision from the

plan
Selected plan area (item view only) Enables you to change the decision number
of full loads of a selected item
See Also:
Use
You can use the cross-dock planning tool to manually create a cross-docking plan consisting of one or more cross-docking
decisions . These cross-docking decisions may or may not be based on the system recommendation.
Procedure
Open the cross-dock planning tool .
The planning tool opens.
The following is displayed:
The selected documents for which the Plan cross-docking monitor method was invoked (displayed in the Inbound/Outbound
document area for planning documents)
The candidate documents that contain items, which the system recommends be linked with planning document items
(displayed in the Inbound/Outbound document area for candidates)
If the planning tool was opened directly from the monitor selection screen, the planning and candidate documents that contain
items, which the system recommends be linked, are displayed in the Inbound and Outbound document areas, according to the
previously determined planning direction.
The following information is displayed for each document:
4/24/2022
a. Total number of loads to plan (for which cross-docking opportunities can be analyzed)
b. Number of full that are the subject of opportunities recommended by the system after analyzing the whole pool of selected
c. Cross-docking percentage (a/b *100%)
d. Document time reference
e. Vendor (inbound documents only)
f. Priority (outbound only)
g. Shipment (outbound only)
h. Sold-to-party (outbound only)
You can add or subtract columns via the ALV tool bar functions to customize the information that you want to be displayed in
the planning tool ALVs.
You can either accept the system-recommended decisions or view more details (with the possibility of creating your own cross-
docking decisions).
a. To add the system-recommended decisions to the plan, go to step 8.
b. To view more information, go to step 3.
Choose the following from the main tool bar if you want to change the view resolution:
a. For shipment view, choose .
b. For item view, choose .
c. Back to document view, choose .
If you want to display the number of system-recommended links between documents or document items, choose
.
If you want to display the exact system-recommended links between documents or items:
a. From the relevant document ALV, select the line corresponding to the document or item.
b. From the ALV tool bar, choose .
The following additional information is displayed for the selected document, and its corresponding linked document:
i. Number of full loads that the system recommends be linked (based on whole pool of documents)
ii. Number of documents/items that the system recommends (based on whole pool of documents) be linked with the
document/item (only if link information is displayed per step 4 above)
The information in i and ii appears in elds shaded in orange.
4/24/2022
iii. Number of full loads that the system recommends be linked (based on particular candidate document and whole pool of
planning documents)
iv. Number of documents/items that the system recommends (based on particular candidate document and whole pool of
planning documents) be linked with the document/item (only if link information is displayed per step 4 above)
The information in iii and iv appears in elds shaded in yellow.
If you want to view other candidate documents with items that can be linked to the planning document items, choose
.
This pushbutton is only displayed if more candidates exist than those in the system recommendation.
If you want to view the system recommendation based on selected planning and/or candidate documents/items:
a. From the document ALVs, select the lines corresponding to the documents or items.
b. From the main tool bar, choose .
The new system recommendation, based on the selected documents/items, is displayed
If you want to see how the system recommends you ful ll loads of outbound delivery 80001222 with loads of inbound deliveries
180004323 and 180002342, you select the lines corresponding to all of these deliveries and then choose .
To add a decision to the cross-docking plan:
a. From the inbound document ALV, select the line corresponding to the inbound document/item.
b. Repeat step a. for the outbound document/item.
c. From the main tool bar, choose .
The selected documents/items disappear from the Inbound and Outbound document ALVs and reappear in the Selected plan
ALV.
You can add all of the system-recommended decisions by simply choosing , without the need to select each
corresponding line in the ALV.
If you want to change the number of loads of a particular material in a cross-docking decision:
a. Ensure that you are in the item view resolution.
b. From the Selected plan ALV, select the line corresponding to the decision for which you want to change the load quantity of a
material.
4/24/2022
c. Choose .
The Enter full loads of decision dialog box appears.
d. Enter new number of material loads for the decision. The new number must be less than the original number.
e. Choose Enter .
The plan is updated accordingly.
After the plan is complete:
a. From the Selected plan ALV, select lines corresponding to the decisions that you want to save.
b. Choose .
The Scheduling Possible eld is checked for those decisions for which locations can be scheduled in Yard Management .
Choose to save the decisions to the cross-docking plan.
If scheduling is not possible for all of the decisions, the reason is displayed in the Reason Not Scheduled eld, and the query
messageScheduling not possible for all selected records. Save decisions for these anyway?appears.
If you choose Yes , all of the decisions are saved, and locations are scheduled where possible. You can subsequently attempt to
schedule locations for the other decisions (for which locations have not currently be scheduled), via the Schedule method. For
more information, see Cross-Docking Monitor Methods .
If you choose No , only the decisions for which scheduling is possible are saved, and the locations are scheduled.
For more information on location scheduling in Yard Management , see System Scheduling in the SAP Library for Yard
Management.
Designating a Document or Document Item for Cross-Docking
Use
You can designate documents or items for cross-docking via the cross-docking monitor.
Procedure
ALV Hierarchy Tree
4/24/2022
ALV Hierarchy Tree
Display the objects of one or more of the following object and sub-object classes:
Inbound
Inbound Item
Inbound Delivery
Inbound Delivery Item
Inbound TR
Inbound TR Item
Outbound
Outbound Item
Outbound Delivery
Outbound Delivery Item
Outbound TR
Outbound TR Item
corresponding to the documents/items that objects corresponding to the
you want to designate for cross-docking. documents/items that you want to
designate for cross-docking.
From the ALV toolbar, choose and Right-click the icon to the left of the object
then Designate for cross-docking from the representing the document/item that you
pop-up menu. want to designate for cross-docking and
then choose Designate for cross-docking
from the pop-up menu.

objects.
Result
The documents or items are designated for cross-docking. Decisions of type
A (Designation of inbound doc/item for cross-docking) or
B (Designation of outbound doc/item for cross-docking) are created for the documents or items.
In the case of an inbound document/item, TOs created for the inbound items designated for cross-docking are created to
the cross-docking storage type.
In the case of an outbound document/item, putaway TOs created for arrived inbound items with the same materials as
the outbound items are created to ful l the outbound items, as long as planned decisions do not exist for these inbound
items.
 Note
For more information on decisions involving documents or items designated for cross-docking, see Planned Cross-
Docking .
Assigning Outbound Deliveries to a Group

4/24/2022
Use
You can create groups and assign to them deliveries via the cross-docking monitor. The objective of this functionality is to save
you from having to maintain groups from the delivery monitor.
 Note
This method allows you to only create a group and then assign outbound deliveries to it. You can not assign the outbound
deliveries to a previously created group.
Procedure
ALV Hierarchy Tree
Display the Outbound Delivery objects.
corresponding to the outbound deliveries objects corresponding to the outbound
that you wish to assign to a group. deliveries that you wish to assign to a
group.
From the ALV tool bar, choose and Right-click the icon to the left of the object
then Assign to group from the pop-up representing the outbound delivery that you
menu. wish to assign to a group and then choose
Assign to group from the pop-up menu.
The Create Group dialog box appears.
objects.
The Create Group dialog box appears.
From the Group type eld, choose a type of group. The group can be either a picking
group or a wave pick .
In the Group descript . eld, enter a textual description for the group.
If you want to create transfer orders for multiple deliveries, select TO for Mult. Del .
 Note
This is only relevant if you have selected more than one outbound delivery to assign to
the group.
In the Release Date and Latest Rel.Date elds, you can enter dates and times for the
release time and latest release time .
If you do not enter any dates and times in these elds, the release time and latest release
time is determined from Customizing for Logistics Execution Warehouse
Management Cross-Docking General Settings Maintain Warehouse Level Settings .
Choose Enter .
The deliveries are assigned to the group.
 Note
You can modify the release time and latest release times via the Modify method. For more information, see Cross-Docking
Monitor Methods .
4/24/2022
Cross-Docking Alert Monitor
Purpose
The purpose of the cross-docking alert monitor is to highlight to warehouse managers actual and potential problematic
situations regarding cross-dockingand to provide exception handling tools.
Integration
The cross-docking alert monitor can be accessed from the cross-docking monitor.
Features
Alerts Provision
The cross-docking alert monitor provides you with alerts when certain conditions are met. For more information, see Alerts
Provision.
Exception Handling and Troubleshooting
The cross-docking alert monitor provides the tools with which you can handle the exceptions highlighted by the alerts. For more
information, see Alert Monitor Troubleshooting Tools.
Opening the Cross-Docking Alert Monitor
Use
You can open the cross-docking alert monitor either from the SAP Easy Access menu or from the cross-docking monitor .
Prerequisites
You have sufficient authorization to open the alert monitor for the selected warehouse.
Procedure
Opening the Alert Monitor from the SAP Easy Access Menu
1. From the SAP Easy Access menu, choose Logistics Logistics Execution Cross-Docking Alert Monitor.
The Select an Object dialog box appears.
2. Enter the warehouse for which you want to monitor alerts.
3. Choose Enter .
The alert monitor opens, displaying alerts for the selected warehouse.
Opening the Alert Monitor from the Cross-Docking Monitor
From the monitor tool bar, choose .
The alert monitor opens, displaying alerts for the warehouse selected for the cross-docking monitor.
4/24/2022
Cross-Docking Alert Monitor User Interface

The alert monitor’s user interface comprises of the following two areas:
Hierarchy tree
ALV
Hierarchy Tree
The hierarchy tree, located on the left side of the cross-docking alert monitor, is a navigation area consisting of the various
object classes (alert categories). Using the tree, you can display and con gure the alerts.
ALV
The ALV, located on the right side of the cross-docking alert monitor, contains all elds of the object records, including the
alerts’ statuses. You can also perform methods from the ALV tool bar.
See Also:
Using Basic Alert Monitor Functions
Alert Monitor Troubleshooting Tools
Using Basic Alert Monitor Functions

Displaying alerts From the hierarchy tree, double-click the Details for alerts in the category, including
icon next to an object class node. levels of alert and statuses, are displayed
in the ALV.
Display details for individual alert The Details dialog box appears.
1. From the ALV, selecting a row
corresponding to the alert for which
you want to display details.
2. Choose from the ALV tool bar.
Invoking alert monitor troubleshooting tools Refer to Alert Monitor Troubleshooting Tools .
Refreshing display for whole warehouse From the alert monitor tool bar, choose . The display of all object classes in the alert
monitor is updated.
Setting auto-refresh period The alert monitor display is periodically

1. Enter the number of minutes that
updated according to your settings.
must elapse before the alert
monitor display is automatically
updated.
2. If you want to display a clock at

the top of the hierarchy tree with
the time that has elapsed since the
last auto-refresh, select Display
AutoRefresh Clock .
3. Choose Enter .
4/24/2022
See Also:
Con guring Alerts
Con guring Alerts
Use
You can de ne the circumstances that trigger the different levels of user-de ned alerts, as well as determine which alert
categories are not to be displayed in the alert monitor and which alert category is initially displayed.
Procedure
Con guring Multiple Alert Categories
1. Fr o m thealert monitor tool bar, choose .
The Alerts Maintenance dialog box appears, displaying all object classes/alert categories.
2. For an alert category (for which con guration is enabled) and warehouse, enter a value for one or more of the following:
Upper threshold value
Upper warning threshold value
Lower threshold value
Lower warning threshold value
3. Choose a unit of measure for the UOM eld.
 Note
Steps 1-3 are not applicable to the standard alerts provided with the system.
4. If you want to exclude an alert category from the alert monitor, select Exclude.
5. To set an object class as the initially displayed object class, select Init. Exp .
6. Save your settings.
Con guring an Individual Alert Category
1. Display the object class/alert category.
2. From the hierarchy tree, right-click the icon to the left of the object class and choose Con gure from the pop-up menu.
The Alerts Maintenance dialog box appears, displaying the selected alert category
3. Perform steps 2-6 in Con guring Multiple Alert Categories.
Result
The system saves your alert settings.
 Note
4/24/2022
For an object class/alert category, if you de ne alerts for a speci c presentation pro le and these alerts also exist for
presentation pro le ****, the alerts for the speci c presentation pro le take precedence.
Alerts Provision
Use
The cross-docking alert monitor provides customizable alerts upon the ful llment of certain conditions.
Prerequisites
In the case of non-standard alerts, you have done the following:
De ned the alerts in Customizing for Logistics Execution Warehouse Management Cross-Docking Monitoring De ne
Object Classes.
· De ned object class identi ers and hierarchy in Customizing forLogistics Execution Warehouse
Management Cross-Docking Monitoring De ne Unique Object Class Identi ers, Permitted Movements and Hierarchy.
Mapped values to the de ned alerts in Customizing for Logistics Execution Warehouse Management Cross-
Docking Monitoring Map Alert Values.
Con gured the alerts. For more information, see Con guring Alerts .
Features
Alerts are provided for the following categories:
Object Class/Alert Category Contains
Deliveries - Rel. Time in Past Cross-docking relevant outbound deliveries whose release times
and latest release times have passed.
The alert statuses are as follows:
Red when the latest release time has passed
Yellow when the release time has passed
TRs - Rel. Time in Past Cross-docking relevant TRs whose release times and latest release
times have passed.
The alert statuses are as follows:
Red when the latest release time has passed
Yellow when the release time has passed
4/24/2022
Object Class/Alert Category Contains
Cancelled TOs w/o Substitute TOs that have been cancelled, pursuant to the opportunistic cross-
docking process, but for which no substitute TOs have been
created.
 Note
This situation occurs when you are utilizing foreground picking
transfer order (TO) creation. During TO creation, when the
system displays the source of the TO to be created (e.g. goods
receipt storage type 902), the original putaway TO has already
been cancelled. If you exit the transaction without saving the TO,
no replacement TO is created.
Activities
1. When the value of a particular object, for which an alert has been con gured:
a. a. Exceeds the upper warning threshold value or falls below the lower warning threshold value, the yellow traffic
light appears in the Exception eld for the object
b. b. Exceeds the upper threshold value or falls below the lower threshold value, the red traffic light appears in the
Exception eld for the object
c. c. If the alert is not con gured to have upper or lower threshold values, the red traffic light automatically appears
in the Exception eld when the alert appears.
2. After you have dealt with a problem via the alert monitor troubleshooting tools, the relevant object disappears.
Alert Monitor Troubleshooting Tools
Use
The alert monitor troubleshooting tools allow you to perform actions on selected objects in order to handle exception
situations.
Prerequisites
You have de ned methods and object classes in Customizing for LogisticsExecution Warehouse Management Cross-
Docking Monitoring De ne Object Class Methods.
Features
You can invoke the troubleshooting tools by:
1. Displaying the relevant alerts. For information on how this is done, see Using Basic Alert Monitor Functions .
2. From the ALV, selecting a row corresponding to the object on which you want to apply the method.
3. Choosing from the ALV tool bar and then choosing an option from the pop-up menu.
Activities
4/24/2022
Method Name Description What You Should Know
Create TO Enables you to create a replacement This method takes you to the Create
transfer order (TO) for a cancelled TO that Transfer Order for Delivery Note: Initial
does not currently have one. screen for the selected document.
For more information on creating transfer

orders, see Creating Transfer Orders in the
SAP Library for Warehouse Management
System.
Other Functions
This section contains information about the following functions:
Business Add-Ins
Authorization Checks
Archiving
Business Add-Ins (Add-Ins)
Use
Cross-Docking contains the Add-In LXDCK_CROSS_DOCK for in uencing the processing of planned and opportunistic cross-
docking . The Add-In enables you to tailor Cross-Docking ’s existing functions to your own requirements by allowing you to take
control of the application at critical points.
 Note
Detailed information on the Add-In can be found in the Add-In’s documentation. See the IMG for Logistics
Execution Warehouse Management Cross-Docking Add-Ins Cross-Docking Enhancements.
Features
The Add-In contains the interface IF_EX_LXDCK_CROSS_DOCK, which itself contains the following methods:
Method Description Purpose
OPPORTUNISTIC_CANDIDATE_SELECT Determine TO to be Cancelled in Enables youto determine which transfer

Opportunistic Cross-Docking order (TO) to be cancelled during
opportunistic cross-docking
During putaway TO creation and within the

evaluation of opportunistic cross-docking,
the system searches for corresponding
picking TOs which can be cancelled and
replaced with the putaway TO. This method
enables you to determine which of the
picking TOs will be cancelled.
4/24/2022
Method Description Purpose
DOCUMENT_DATE_CHANGE Determine Document Date and Time Enables you to determine the date and time
which forms the basisfor cross-dock
planning. You can determine adifferent
reference date and time for outbound
deliveries than what is de ned in
Customizing for Logistics
Execution Warehouse
Management Cross-Docking General
Settings Maintain Warehouse Level
Settings , or seta different time other than
what the system recommends for either the
inbound delivery or inbound/outbound TR.
PLANNING_DOCUMENTS_MATCH Determine Planning and Candidate Enables you to change the algorithm used
Documents Matching by the system in determining the optimal
cross-docking decisions
PALLETIZING_DATA_DEFINE Determine Palletization Data Enables you to determine your own

palletization option to be used in the cross-
dock planning process
PLAN_DECISION_SELECT_CHANGE Determine Selected Plan Decision and Enables you to determine which of the
Adjust Decision Qty planned cross-docking decisions is to be
selected for processing, or not select a
decision, even if one exists
You can delay decision processing until a

later point in time.
CROSS_DOCK_DISABLE Disable Cross-Docking Enables you to disable cross-docking via

ltering
You can exclude a group of materials from

being considered for cross-docking.
FIFO_CHECK Determine FIFO Tolerance Enables you to in uence the creation of

transfer orders for cross-docking decisions
by doing the following:
Skipping the strict FIFO check for a

speci c material
Changing the FIFO tolerance (as

de ned in Customizing for
Logistics Execution Warehouse
Management Cross-
Docking general
Settings Maintain Warehouse
Level Settings) for a speci c
material
Authorization Checks
Use
4/24/2022
The authorization checks control the ability of warehouse managers to use the monitor and alert monitor.
Integration
The authorization checks have to be implemented using the standard SAP authorization concept. For more information on the
standard SAP authorization concept, see the SAP Library for Users and Roles (BC-SEC-USR).
Features
You can assign the following authorization object to users:
L_MON_XDCK
Determines the abilities of managers to use the monitor and alert monitor. Authorization object L_MON_XDCK comprises of
the following authorization elds:
Authorization Field If Users Has Authorization for Field:
Location User is able to run the monitor or alert monitor for this warehouse.
Method authorization group Methods of this type appear in the object pop-up menu. Possible
values are:
Display
Maintain
Methods These methods appear in the object pop-up menu.
Object class This object class appears in the monitor or alert monitor hierarchy
tree.
Archiving
Use
Batch programs have been provided to archive records in Cross-Docking and delete old data from log tables. These programs
can be used to free space in the database and to provide accessible records for future reference.
 Note
For more information on archiving, see the SAP Library for SAPNetWeaver Components Cross-Application
Functions Archiving Application Data (CA-ARC) .
Features
The following object can be archived:
Archiving Object Includes Pre-Archiving Write Program Delete Program Read Program
Checks
4/24/2022
Archiving Object Includes Pre-Archiving Write Program Delete Program Read Program
Checks
LXDCK_ARC Cross-docking Include: RLXDCKWT001 RLXDCKDL0011 RLXDCKRD001

decisions
Status of the
Link between object is
decisions and Completed
cancelled transfer or Cancelled
orders .
The object
has reached
the
residence
time, as
determined
in the
variant by
the user.

Warehouse Management System (WMS) - 4

Uploaded by

Copyright:

Available Formats

Warehouse Management System (WMS) - 4

Uploaded by

Document Information

Original Title

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

Warehouse Management System (WMS) - 4

Uploaded by

Copyright:

Available Formats

4/24/2022

SAP ERP Support Package Versions | 6.0 EHP7 SP17

Original content: https://help.sap.com/docs/SAP_ERP_SPV/34fc810a607e4ae5a287b6e233b8566f?locale=en-

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

Mobile Data Entry (LE-MOB)

Warehouse Management System (WMS)

For more information, see Handling Unit Management .

Task and Resource Management (TRM)

GUI and Character Device Support

Bar Code Support

RF Support of Warehouse Management Processes

Mobile Data Entry supports a wide variety of warehouse processes, including:

Goods receipts and issues

Loading and unloading

In Customizing for Mobile Data Entry , you can de ne the following:

The size and number of screens

Menus and menu sequences

Bar code types and Application Identi ers

Use of the Enter function

Mobile Data Entry supports both GUI and character-based devices.

Currently, two device types are supported:

1. Devices for forklifts: 8 lines by 40 characters each

2. Portable handheld devices: 16 lines by 20 characters each

RF Device Basic Functions

Back Returns you to previous screen

Det Displays detailed information for a speci c item

Enter Checks veri cation elds

LOﬀ Enables you to log oﬀ from the RF device

More Displays additional available pushbuttons/functions

Nxt Navigates you to the next screen

OK Con rms a message and leaves the screen

PgUp ( ) / PgDn ( ) Displays the previous or next item

Save Con rms the step

Yes/No Answers a message

Pushbutton Function Process Where Used

APM Enables you to select auxiliary packaging Packing

BnEm Marks a storage bin as being empty. Inventory Counting

ByMt Enables you to pack/unpack material Packing and Unpacking

Chk Calculates diﬀerence quantity when Goods Receipt

Picking (except for Bulk Picking)

Pushbutton Function Process Where Used

Conf Con rms a diﬀerence Goods Receipt

Diﬀ Enables you to report quantity diﬀerences Goods Receipt

DlSU Deletes a SU from the Selected Storage Inventory Counting

G.TO Creates a TO for a delivery. Goods Receipt

GRDt Sorts by goods receipt date Stock Overview Inquiry

HU V Displays information on any lower-level HUs HU Inquiry

HU.D Displays additional information on a HU HU Inquiry

Packing and Unpacking

Items Displays information on the items of a Goods Receipt

LdUn Enables you to load/unload a delivery Goods Receipt

MatV Displays information on a material HU Inquiry

Mt.D Displays information on a material Packing and Unpacking

NBin Changes the destination bin for a single- Putaway

Pushbutton Function Process Where Used

NSU Adds further SUs to the selected SU list Clustered Putaway

NwIt Enables you to add a new quant to a storage Inventory Counting

Pack/Unpck Enables you to packs/unpack delivery Goods Receipt