Task Interleaving in SAP EWM

[krishnakumar_chokkar]

Introduction:

In this blog post you will learn about the task interleaving in SAP EWM. Task interleaving helps to cut down the unnecessary movements and enables better optimization of unutilized resources leading to reduction of travel time and improving operational efficiency.

For example, during an inbound process, once the goods are dropped to the respective storage type, a warehouse order will be assigned automatically to the same resource for picking up goods from the same /nearest storage type. This helps in better utilization of the resources.

Solution Approach:

The below mentioned configuration steps can be employed to achieve this functionality:

• Create a Resource Types using the below mentioned node:

IMG Path – SPRO -> IMG -> SCM Extended Warehouse Management -> Extended Warehouse Management -> Cross-Process Settings -> Resource Management->Define Resource Types.

If required assign bin access types and hu type groups by selecting the respective options.

• Define queue types using the below mentioned node:

IMG Path – SPRO -> IMG -> SCM Extended Warehouse Management -> Extended Warehouse Management -> Cross-Process Settings -> Resource Management->Define Queue Types.

• Define queue by assigning the queue type using the below mentioned node:

IMG Path – SPRO -> IMG -> SCM Extended Warehouse Management -> Extended Warehouse Management -> Cross-Process Settings -> Resource Management->Define Queues.

• Define queue determination criteria using the below mentioned node, so that queue will be assigned automatically once the warehouse task is created.

1. 
   
   
   
   1. In this case the put-away warehouse process type is: N019 and picking warehouse process type is: Z019.
   
   
   2. Both the put-away and picking storage type activity area is N019.
   
   
   
   

IMG Path – SPRO -> IMG -> SCM Extended Warehouse Management -> Extended Warehouse Management -> Cross-Process Settings -> Resource Management->Define Queues=>Define Queue Determination Criteria.

• Define Resource Group using the t-code:/SCWM/RGRP.

• Maintain queue type sequencing using the t-code:/SCWM/QTSQ.

• Maintain queue sequence for resource group using the t-code: /SCWM/QSEQ.

• Create resource using the t-code:/SCWM/RSRC.

• Maintain user by assigning the resource using the t-code:/SCWM/USER.

Testing:

• Created outbound & inbound delivery to perform this testing.

Outbound delivery: 80003961

Inbound delivery: 180002180

• In the delivery screen, create warehouse order/task for both outbound & inbound delivery, manually by clicking on CREATE button and then SAVE.

First create a warehouse task for an outbound delivery using the t-code: /SCWM/TODLV_O.

Then create a warehouse task for an inbound delivery using the t-code: /SCWM/TODLV_I.

• Warehouse order/task can be viewed in the monitor screen using the transaction code:/SCWM/MON.

Warehouse order is created for an outbound delivery and it is assigned to the respective queue: OUTBOUND.

Similarly warehouse order is created for an inbound delivery and it is assigned to the right queue: INBOUND.

• Login to the RF by mentioning the warehouse number and resource using the t-code:/SCWM/RFUI, then follow the path System-Guided->System-guided Selection.

As per queue type sequencing, system should propose the INBOUND queue first and then OUTBOUND queue, so that a product will be dropped to the storage type: N019 for put-away & other product will be picked for an outbound delivery from the same or nearby storage type.

Scanning the HU from Goods Receipt zone

Scanning the destination bin to perform the put away.

Next an outbound delivery warehouse order is proposed automatically to perform the picking activity. Scan the source/destination bin, product, and quantity.

Conclusion:

This blog post walks you through various steps involved in Task interleaving with test results. As per the queue type sequencing INBOUND queue is assigned first and then OUTBOUND queue.Hence its results are verified by executing the above test scenario.