EWM- Put away error -No destination bin determined

[former_member435196]

Hello,

I am trying to put away the goods in storage type with rule 5.(addition to stock/next enpty bin). When I am trying to create warehouse task I am getting below error. Every time I have to go to default value and enter destination bin. Why can't system determine destination bin automatically based on strategy? I am putting away loose material in to bin.

"Could not fully determine the destination data' Attached herewith message log.

Thanks,

Milind

[former_member146970]

Hi milind.chaudhari2

there are different parameters in putaway search strategy to determine correctly. check below

1. check storage type search sequence for putaway. (spro-ewm-goods receipt process-startegies - storage type search-define storage type search sequence)

ex:- WHSE - SEQ1

2. in above path assign storage type to sto type search sequence.

ex:- WHSE-SEQ1-ST01

3. create putaway control indicator and assign to material master

EX:- PUT1 -> ASSIGN TO PRODUCT MASTER IN /SCWM/MAT1

4. specify the storage type search sequence for putaway

ex:- WHSE - PUT1 - 1010 - SEQ1

above 4 steps are mandatory along with above steps, optimise access sequence is also mandatory

in same above path go to optimize access strategy for storage type search: maintain sequence 1 with put.ctrol check box indicator and process type - check box

now run a scenario , now it will trigger bin automatically,

Note:- 1. if different WPT is triggering then check and assign the same WPT in above 4rth step.

sometimes from process type det ind , other warehouse process type may trigger.

2. check for the bin weights and volumes against material weight and volume.

I hope this helps and solve your issue.

Thanks,

Raghuram Rajanala.

[sameer_abdul_0956]

Hi Milind,

- You need to keep WT GENERIC Field blank at Storage Type level under Put away Control

Thanks,

Sameer.

[Jiawei_Hong]

Milind,

If you solved this issue, could you share for us, thanks.

[former_member543347]

Milind,

No wonder that the system is working as you expect in stock removal and not in putaway: the two processes are deeply different. In stock removal you don't look for a bin, but for a quant.

Please check the definition of the storage bin type LOSE. Do you have any maximum capacity/weight/volume? If you are trying to overload the bin and you have activated the early capacity check, it can be that the bin type is skipped without any information in the log.

[former_member543347]

Hi Milind,

According to your log, you have a bin type determination. The system is looking only for bins of the type B001.

Is it possible that your existing bins on storage type 1111 don't have this type?

[former_member435196]

Hello,

I did all combinations of removing bin type from configuration and from bin, adding bin type in configuration and bin etc But still every time system fails to determine destination bin automatically. I have to manually select it. Surprisingly, for outbound process, system correctly determined the bin. Can you please look in to message log and suggest what exactly is missing parameter?

Please refer attached my new test case of put-away log and storage bin screen shot.

Thanks,

Milind

put-away-message-log.jpg

storage-bin-with-bin-type.jpg

[former_member435196]

Please find attachement

put-away-error.jpg

Thanks

[JuergenPitz]

No log attached...

Putaway rule 5 is next empty bin, 2 is addition to stock / empty bin. But that should not matter.

Brgds

Juergen

---
Want to influence SAP software development decisions for EWM?
https://influence.sap.com/ewm2019

Want to learn EWM?
Check for EWM courses @ https://training.sap.com/trainingpath/Applications-Logistics+Execution+%26+Warehouse+Management-SAP+...
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/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!

[former_member435196]

Hello,

I checked all my configuration but still not able to find out where is the issue. Ideally, system should search the bin automatically and put away. But is is not happening. From log, you can see that, system is able to find destination storage type but fails to find exact bin.There is no specific bin search failed error.

Thanks,

Milind