Batch determination based on WM storage type stock positions

Question

Hello experts,
I am hoping the get some advise on the best method to achieve this:
We have batch determination turned on for select customers and the system is proposing stock that is mainly in our each or lose pick storage types (110), the issue with that is the fact that we do not pick in less then case qty for those customers so if the stock doesn't exist in our general storage the user must re-determinthe batch codes before delivery release.
This process is becoming very time consuming so I would like to improve it.
My first thought is to create a custom check in the batch search strategy that will only propose batch codes that exist in our general storage (search strategy based on WM stock positions)
Are there any other options to achieve a batch search strategy based in WM stock positions other then the one above and does that solution sound practical?

Answer 1

I'm not referring to the type of picking either (i'm not referring to picking strategies at all). I'm referring to storage type search criteria defined in OMLY.
"We need batch determination based on WM storage type stock positions" -> you are running BD at delivery level and therefore, there is nothing from a standard perspective that we can do to run BD based on WM storage type again. Since the BD has already occurred, we need to find other venues to direct the pick to the appropriate storage types.
This is what I'm understanding but I reckon there's something that I'm missing and so let's take the below example and then you can get back with corrections:
R001 plant
ZM01 storage location
Z01 WH
110, 120, 130, 140 storage types (110, 120, 130 are case/lose pick, and 140 is general)
Since you had mentioned earlier that the BD is running at plant level, I'd assume the storage location ZM01 is automatically determined (since the batch resides in ZM01). Since the batch is already determined, based on your 'storage search strategy' (110, 120, 130) the system tries to pick this batch in these storage types. Now, when there is no full case, you have to manually change the storage type to 140 to pick and this is where the problem is. So, I was recommending that since there is no standard way to automatically pick the full case from 140, use the enhancement.