cancel
Showing results for 
Search instead for 
Did you mean: 

WM putaway strategy "C" open storage considering bins with inventory first?

Former Member
0 Kudos

I have enabled putaway strategy C utilizing open storage in WM. 


What I anticipated was that bin determination would consider the first alphabetical bin for that storage type.  However, what I am experiencing is the bin being determined is the first alphabetical bin with inventory; by-passing earlier bins without inventory.

Storage type settings:

Putaway strategy: C

Mixed Storage: X allowed

Addn to Stock: X allowed

For example, I have bins A and B.  Bin A does not have inventory but bin B has inventory.  My transfer orders will suggest bin B over bin A.

This is not a capacity issue and not related to mixed storage as I am allowing.

Has anyone experienced this and found a way to overcome it?

Accepted Solutions (0)

Answers (2)

Answers (2)

JL23
Active Contributor
0 Kudos

Before changing customizing you better check the bin determination log in your TO to know why this bin was found and which parameters were used in the determination

Former Member
0 Kudos

Thanks Jürgen.  I verified in the bin determination log for TO creation from LT01 and am not seeing any indication why some bins are being skipped.  There are no bins before this that are blocked for putaway or locked for CC.

mihailo_sundic
Active Contributor
0 Kudos

Hi Mike.

Please try manual putaway - select storage type in question, and manually enter problematic bin "A" which is skipped normally when you run in background.

Are there any errors?
Can you post a screen of the result when you enter destination st.type and st.bin and hit ENTER?

If there is any problem - reason to skip bn A this will show it in foreground.
It seems to me based on your bin determination screen that bin A isn't considered at all, but please show the screen from manual putaway to bin "A" and hopefully we'll see the reason for exclusion...

Former Member
0 Kudos

Hello Mihailo.  I have included two screen shots of LT01.  The first is the bin determined and then when I over-rode that to a earlier (alphabetically) bin.  Both only state the default message check your entries but even the over-rode bin allows for the TO to be created without any errors.

mihailo_sundic
Active Contributor
0 Kudos

Ok, I see... I think I have faced this once with strategy C.

It seems that SAP consideres for putaway only one bin in this type of strategy (C).
Like it is assumed that you will always need only one bin in open storage, and no need to open seamless bins if it's open storage.

The interesting thing is that the storage type, when moved to strategy B, in my case behaved perfectly normal, but when it was with the same settings (storage bin section search, storage bin type search).

I'll try to find out something more about the issue, but I remember having to code a user exit because I didn't want to use 'B' strategy back then.

Maybe I'm smarter now than I was

0 Kudos

Hi Mike

You are telling the system to add stock to existing stock in the warehouse.

Addn to Stock: X allowed

When the bin is filled according to your settings it will then look at A or the other bins in your system

Former Member
0 Kudos

Hello Quinten.  I do have addition to stock enabled.  I do not have capacity check enabled so it always considers B and never A unless I have inventory in A:  only then will A be considered.

0 Kudos

Hi Mike

I understand. What I meant was remove the addition to stock flagg.

Former Member
0 Kudos

I have disabled the addition to stock and created a new receipt.  The auto TO still from the receipt still went to then next bin with inventory (different part) and bypassed empty bins before it in the same stype.

0 Kudos

Hi Mike

I think a better way to look at this migh be to ask do you want the stock to go the next empty bin. If so then you might want to look at Putaway Strategy L - Next empty bin. 

The other question, have you cleard the warehouse of all stock first before moving stock back into the warehouse.

Former Member
0 Kudos

My desire is for SAP to determine first available bin.  This is really a precursor to capacity check.