EWM Queue determination is not reading destination activity area

[Chethan_tv]

Hello EWM Experts,

I have a hard stop, where I am not able to determine right picking queue. If this is not allowed in standard config, is there any Enhancement spots..? Below is the scenario and current configuration.

1. I need to setup a new picking queue for Heavy materials (>35 pounds) to pick separately.
2. So that user can separately pick heavy materials and physically drop them off at final ship stage (Without any internal steps)
3. So I created new WOCR & applied item filter with min weight 35
4. Created & assigned new Storage process with OB01 & OBSH steps to new WOCR
OB01: Pick
OBSH: Pack and ship (given destination location as ship stage 8030)
5. Now, below shown queue determination (also attached)

Existing setting - Source: 0100 queue: OUTFLAM
New entry - Source: 0100 Destination: 8030 queue: OUTHEAVY

6. Access sequence also maintained for destination AA.
7. 8030 is sorted for PICK activity.

All the tasks are going to OUTFLAM queue only, even for new WOCR..

[Chethan_tv]

For my new WOCR - new queue OUTFLHEAVY should come.
But for all tasks OUTFLAM is coming

[JuergenPitz · Accepted solution]

Hi,

I do not think that this can work in the way you want to.

- The queue determination is done in the WT.

- After that the WOCR determination comes. Then your WOCR changes the destination and you know the new destination activity area. But I don't think that the system then tries to find a new queue.

So it might be seen as a gap, but that is the sequence of what the system determines and how it works in the standard. There is a BAdI for the queue determination during WO creation, I suppose this is what you would have to use.

Brgds

Juergen

---

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!

[Chethan_tv · Accepted solution]

Thank you
All your points make sense, after new destination from WOCR - system will not assign new queue.

Is this the BADI for queue - /SCWM/IF_EX_RSRC_QU_DET ?
Is there any blog or document to see how this works? Thanks a lot for your help

[j_calinas]

Maybe you can post an image of the WO creation log..

I wonder if the activity of the WT is PICK or INTL?

[Chethan_tv]

Attached here is WT screen shot, This config of new WOCR is made only during wave release & not by manual WT creation.. During wave release system is not showing up WO creation Log, strange.

Activity is PICK..
In attached screen shot: source is 0118 & destination is 8030..
Queue determination is same -

Existing setting - Source: 0118, Activity: PICK, queue: OUTFLAM
New entry - Source: 0118, Destination: 8030, Activity: PICK, queue: OUTFLHEAVY

[j_calinas]

Yes, seems fine. can you post a screenshot of your configuration under 'assign queue determination criteria' and 'Define Queue Access Sequences' please.

Suggest you activate WO log, even if only temporarily, to understand which sequence entry the system is taking and why

[Chethan_tv]

Queue determination & Queue Access Sequence:

WO log:

[j_calinas]

Its normal that system is getting queue OUTFLAM, seems that system is using seq.no 3 to determine that queue.

You need to make a sequence with flags in: source AA, dest. AA, and activity, in the acess sequence..

Then in determination you already have 0118, 8030 and PICK, so it will work.

[Chethan_tv]

Right, New queue is determined now. Access sequence was the issue..
Thank you so much

[Chethan_tv]

I missed this sorry..
New queue is getting picked, but now all tasks are going to only new queue (OUTFLHEAVY)

Why system is not suggesting OUTFLAM.. for other tasks..

[j_calinas]

Hi,

Acces sequence that contains destination AA should come first in the access sequence list. Have you checked that?

[Chethan_tv]

Thanks for the response
Yes tried all the ways.. only destination AA as sequence 1 & also destination AA along with source AA as sequence 1..

Why queue is not reading destination AA, as per my knowledge queue gets determined during WT creation. I have all entries in WT that matches new queue. But still old queue is coming..

Thanks for your help in advance 🙂