Task Interleaving in SAP EWM
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.
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.
- In this case the put-away warehouse process type is: N019 and picking warehouse process type is: Z019.
- 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.
- 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.
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.
Very Good and detailed Blog Krishna..Keep it your Good Work..
Thank you Sir
Is it true though that interleaving always proposes an outbound task after an inbound task? So if there's 2 inbound and 0 outbound then the second inbound won't be executed?
it be executed. Interleaving tries to get next queue Type .It can be not only inbound - outbound, could be as well other chains like inbound > outbound1 > outbound2 > internal > whatever else > ...
Very nice information Krishna, certainly business would be benefited by this solution, resource KPI’s would be improved and potential efficiency of the resource would be increased, since he need not travel twice to visit the same bin once for to putaway the product and pick the product.
Thank you sir
Nice post. Keep up the good work, Krishna
Thank you Priya
"As per the queue sequencing INBOUND queue is assigned first and then OUTBOUND queue."
In your case of course you change between the two queues, as these two WTs are probably the only ones you have. But you have missed one important step in your description, that is to assign the queue types to the resource group (after assigning the queues). Otherwise no task interleaving will happen. You will only get something from the outbound queue (the second queue in your list) if there is no WT in the inbound queue.
All the above is no official SAP statement.
Want to learn EWM?
Check for EWM courses: https://training.sap.com/trainingpath/Applications-Extended+Warehouse+Management-EWM+in+S4HANA
Get a SAP Learning Hub Subscription: https://training.sap.com/learninghub
And it is EWM. NOT eWM - Duh!
And if your question includes the word "transfer order" - do NOT tag the question with Extended Warehouse Management!
Thanks for your response!
Before posting this blog, I have tested the above-mentioned scenario which has (one inbound & one outbound) in 2 different way i.e., one (with queue type and resource group assignment) and other (without queue type and resource group assignment). In both the cases, I could not see any difference with its results, so I dint mention about queue type and resource group assignment.
After your comment, I have taken one new scenario which has (2 inbound deliveries and 1 outbound delivery). For those 2 inbound deliveries, 2 WO’s (INBOUND queue) are created to move the goods from GR_Zone to the storage type N019 and for outbound 1 WO(OUTBOUND queue) is created to move the goods from storage type N019 to GI_Zone.
Result without resource group and queue type assignment:
In this case, one of the inbound WO is picked up first when selecting the system guided selection in RF. Once the goods are dropped to the storage type N019, the system should suggest the outbound WO to pick up the goods from the storage type N019 because its present in same location. Instead, the system proposed the other inbound WO to move goods from GR_Zone to N019.
Task confirmation time screenshot for reference:
Result with resource group and queue type assignment:
After this assignment, task interleaving works fine. For the same case, system proposed inbound wo first to putaway goods to St.type N019 , then it proposed outbound WO to pick goods from St.type N019 and finally it proposed other inbound WO to goods from GR_Zone to St.type N019.
Task confirmation time screenshot for reference:
I have updated that queue sequence step in the blog post.Thank you!
Krishnakumar, Good and detailed blog. Keep up the good work.
Thank you Suresh
Great blog on task interleaving. Good insight into optimization of resources and increasing operational efficiency. Very useful blog.
Thank you Sir
Nice post Krishna, very detailed and insightful. If implemented correctly will definitely increase material handling efficiency.
Thank you Don