Additional Requirements in SAP EWM

Requirements for Resources

Ensure that the resources in SAP EWM can meet the following requirements:

1 to 1 relationship

Assign a robot to a single resource in SAP EWM.

For robots integrated via integration services for SAP Warehouse Robotics, a robot processes the warehouse orders and tasks based on the configuration of the mapped resource in SAP EWM. SAP Warehouse Robotics determines the queues for the resource that is assigned to a robot based on the queue sequence of the resource group.

For robots integrated via fleet management systems, SAP Warehouse Robotics determines the queues from the resource groups selected in a robot process.
Resource type and group

Define resource types and groups for resources that are mapped to robots.
No radio frequency (RF) logon

Don't log on to RF devices for resources of the resource types that are mapped to robots.

Requirements for Warehouse Tasks

Robots can only process handling unit (HU) warehouse tasks.

If you want a fleet management system to determine the destination storage bin for a warehouse task, you need to make the required configurations in SAP EWM and implement the SAP Note 3381809 Information published on SAP site . In Customizing for Extended Warehouse Management under Start of the navigation path Master Data Next navigation step Define Storage Types End of the navigation path , in the section Putaway Control, you define how the destination storage bin is to be determined during warehouse task creation.

In the Generic Destination Storage Bin Search During WT Creation field (WT Generic), choose one of the following options:

Storage Type and Storage Section
Only Storage Type

You might need to confirm the option with the provider of your fleet management system and robot vendor.

When sending a robot task to the fleet management system, the API of SAP Warehouse Robotics sends the storage type and the storage section to the fleet management system for destination bin determination. If you choose Only Storage Type, the storage section is empty in this robot task of the API.

Note that the destination storage bins determined by the fleet management system must belong to the storage types and storage sections (if there are any). Otherwise, SAP EWM can’t confirm the relevant warehouse tasks.

Requirements for Warehouse Orders

Ensure that the warehouse orders in SAP EWM can meet the following requirements:

One HU warehouse task per warehouse order

Ensure that a warehouse order for a robot to process contains only one HU warehouse task.
Queue of the warehouse orders is only for the use of SAP Warehouse Robotics
No manual activities required for warehouse order processing

Ensure that warehouse orders in queues are qualified for robots to process. There is no need for manual activities.
No changes to warehouse orders
After you've created warehouse orders for robots, avoid updating these warehouse orders.
Note

If you update a warehouse order in SAP EWM after it is retrieved by SAP Warehouse Robotics, the system can't synchronize the changes to SAP Warehouse Robotics.
But depending on the type of changes, the results can be different. See the following details:
- If you change the latest starting date or processor, or remove the warehouse order from the queue, such changes won't affect the processing of warehouse orders by a robot.
- If you change the resource or status of a warehouse order, for example, to cancel a warehouse order, such changes can cause errors when SAP Warehouse Robotics tries doing the following actions in SAP EWM:
  
  Set the warehouse order status to In Process
  
  Assign a robot resource to the warehouse order
  
  Confirm the warehouse task or warehouse order
  
  For robots integrated via integration services, you can find the error details in the Monitor Robots app. You can handle the errors manually in SAP EWM.

Requirements for Exception Handling

Provide a dedicated queue for each warehouse in SAP EWM for exception handling for robots.

For robots integrated via integration services for SAP EWM, if you want to handle the exception for destination bin errors, ensure that you have defined the following settings in SAP EWM:

Exception code CHBD (Change Destination Bin)
Execution step A0 (Data Verification in Background)
At least one of the following business contexts:
- TIM (Confirm Warehouse Task (Internal Movement))
- TPT (Confirm Warehouse Task (Putaway))
- TPI (Confirm Warehouse Task (Stock Removal))

Requirements for Storage Bins

Ensure that the robots can access the physical source and destination bins of the warehouse orders. Consider the physical characteristics of your robots.

Requirements for HUs

For robots integrated via fleet management systems, you want to use the robots to move HUs, for example, carts, totes, and so on. When an HU becomes empty in the storage bins planned to be accessed by robots, do not delete the empty HU. To stop the system from deleting the empty HUs automatically after unpacking, deselect the Deleted checkbox in Customizing for Extended Warehouse Management under Start of the navigation path Goods Receipt Process Next navigation step Slotting Influencing Parameters Packaging Material Determination Define Packaging Material Types End of the navigation path .

If you want to unpack an HU, we recommend that you first move the HU and the stock to a storage bin that can’t be accessed by robots. If you really need to unpack the HU in a storage bin that’s accessible to robots, ensure that SAP EWM creates warehouse tasks for moving the empty HU. 

If you physically change the position of an HU, or you let the robot of your fleet management system change the position using a robot task not from SAP Warehouse Robotics, ensure that you update the correct stock information in SAP EWM. Otherwise, it can happen that the robot can't find the HU, or it might also cause robot collisions.