cancel
Showing results for 
Search instead for 
Did you mean: 

Picking Strategy

Aravind9
Participant
0 Kudos

Hello All,

While receiving the material of quantity e.g 100, we have received in storage type 100. If we cancel the material document of the transaction, the same material which has been received in one storage bin is not picked rather it picks in random manner from different storage bins of same material.

Currently, the picking strategy is L (Partial quantity).

I would like to know which strategy will be suitable to pick the same material and same bin as received.

Are there any implications of changing the strategy to fixed bin one?

Please let us know your thoughts.

Thanks!

Aravind

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Aravind,

It is possible to automate the GR cancellation process by using user-defined strategies (a user-exit actually). To use user-defined strategies, you must select the User exit active field in the Stock Removal Control section of the appropriate storage type record (SM30, V_T3010).

Hope it helps.

Have a nice weekend!

Answers (3)

Answers (3)

Former Member
0 Kudos

Aravind -

First let me know, are you using batch management for materials received? If u r using batch management then the system will not consider any of the picking strategy, as when you cancel the batch then automatically it will consider the batches that are present in the material document, so there is no question or need of any development for reversing same material. If the batches not availabe or consumed you need to create it for reversal, till that TO will not get created for reversal.

However if you are not using batch management then there there is no way, in IM, system can determine which storage type to take material for reversal so it will take random material.

So there are ways like you use batch management or else you develop a exit which will consider the storage type while you put materail in.

Hope this helps to solve your query.

Amol

Former Member
0 Kudos

Hi Aravind,

I don't think your requirement can be addressed by a particular picking strategy. However, it can be controlled by a combination of system functionality and manual process.

First of all, you need to deactivate the automatic/immeidate TO creation for movement types concerned with GR cancellation. This is to prevent the system from creating a TO for GR cancellation which picks stock randomly (according to the storage type's picking strategy of course).

Then, a mannual TO creation for GR cancellation can the be used to manually locate the stock that needs to be returned.

Let me know if you have futher questions.

Cheers

Aravind9
Participant
0 Kudos

Hi,

Thanks for writing in.

Thats a good thing to have it in a way manually.

Could that be possible using User exits and make the flow automatic?

Regards,

Aravind

abhijit_sadhu
Active Participant
0 Kudos

Hello,

You can always develop a Z program to do this. But if you could do that via config, is always a good thing and as mentioned above, you should check your putaway strategy to FIFO or LIFO and see how the system is behaving.

If your system is not behaving the way you believe you have configured, try to raise a SAP note and see if they can , without telling the std. thing " consulting opportunity " if they can help you pin point your issue.

In this case user exit shouldnt be needed, a simple Z program should do. But the question is if you do turn off the auto TO or some std. setting, you always run a risk of some issue with some other scenario which might require the same config settings.

Just my thoughts,

Thanks,

former_member536836
Active Contributor
0 Kudos

Please check by using FIFO as picking strategy.

Regards,

Prashant

Aravind9
Participant
0 Kudos

FIFO --> will pick the one which has entered first. Here it is the case of LIFO.

But why does the strategy "L" has to pick partially from different bins?

Regards,

Aravind

former_member536836
Active Contributor
0 Kudos

Partial qty strategy is "A" as per the SAP standard. Please check what you are maintaining.

I believe if you are using FIFO or LIFO the problem should get resolve.

Regards,

Prashant