cancel
Showing results for 
Search instead for 
Did you mean: 

SAP EWM Task Interleaving - Selection of next WO

Private_Member_324719
Participant
0 Kudos

Hello,

Currently in our project we are using task interleaving in one resource group, with two queues, inbound and outbound in a multi-aisle Rack storage type.

In our scenario, the only factor we have influencing WO priority is the WPT priority. So, all the inbound and outbound WOs in the rack storage type are being created without LSD, but with different priorities.

Task interleaving is working as expected (inbound, outbound, inbound, etc) but i have some questions regarding how the system is determining the next optimal WO in each interleaving queue:

- How does the system finds the optimal WO in the queue, if all the LSD are the same? Just with WO priority?

- In the case of several WOs with the same priority, which WO does the system propose in system-guided? The one that that has a source bin nearest to the current location of the resource?

- How does the system finds this distance? Is it enough to maintain coordinates at bin level? Or do we need to configure 'Travel Distance Calculation' functionality? With storage type-specific networks?

Thank you in advance for any help you can provide,

João

Accepted Solutions (1)

Accepted Solutions (1)

schulte-bahrenberg
Contributor
0 Kudos

...by the way -

it looks like priority is not considered at all in case interleaving is active. Just based on the first look at the coding. Needs further analysis (first screenshot shows sorting without interleaving, 2nd with interleaving):

sorting-of-wos-in-queues.jpg

sorting-with-interleaving.jpg

Private_Member_324719
Participant
0 Kudos

Thank you for the help Hendrik.

From my tests it seems that in interleaving,the system looks for the highest priority WO in each interleaving queue. But i will investigate.

Answers (1)

Answers (1)

schulte-bahrenberg
Contributor
0 Kudos

Hi Joao -

in terms of distance calculation you can check the subroutine WO_SORTING_BY_DIST_CALC in report /SCWM/SAPLRSRC_MAIN. You can see for distance calculation there is a badi involved with fallback class /SCWM/CL_EX_TDC_START_D. If you look at method

CALCULATE_TRAVEL_DISTANCE it seems you have to maintain nodes etc. in the storage type specific networks (/SCWM/TDC_SETUP).

Note that I am not sure he as I have not used it in depth...