EWM - Two-Step Picking - Storage Type

[xavier_fuentes_tafall_197]

I have a client, where your need to pick in two steps:
- does not depend on the material
- depends on the storage type where it is stored

I believe that in "Customizing" there is nothing for that: am I wrong?

Is there a "BAdI" or something for that?

[Ajit_Routray]

Hi Xavier Fuentes,

As per my understanding, the way to attack to this problem is to make this Storage Type as fixed bin, but Stock need to pick from this storage type as priority compare to other Storage type.

-> Use implicit enhancement to check fixed bin table as If product is assigned to this storage type then you need to update 2 step indicator so it cumulates all quantity and picker should pick all quantity from this Storage Type by using 2 Step Process.

Cumulate Function Module: /SCWM/CUMULATE_QUANTITY_1ST

Please let us know if you have questions.

Kind Regards,

Ajit

[xavier_fuentes_tafall_197]

I'm sorry, Ajit, but it can't be like that.

According to the customer's wishes, the stock does not have to be always in that warehouse type.

In addition, this storage type cannot be the first choice in goods issue strategies either.

My client's requirement is that all goods issued from this warehouse type, regardless of the product, is done with "2-steps Picking".

Anyway, thanks for your interest.

[Ajit_Routray]

Hi Xavier Fuentes,

Thank you for providing clarity.

As per my understanding, the below would be alternative Approach to your Current Process (2 Step Process):

-> warehouse type (Storage Type/Activity Area in EWM)

-> Redesign "2 step Picking" as 2 step Processes using POSC or LOSC as per your need

-> Create WO for the same Warehouse Type (Activity Area) using WOCR (Maintain the activity area as sequence in WOCR) where you can use Combined Picking in RF as well as Process Steps (POSC/LOSC) similar to 2 step

I am sorry, you would not get functionality like 2 Step Picking but almost do the similar execution of picking/product warehouse movement flow process.

Please let us know if you have further queries.

Kind Regards,

Ajit

[Ajit_Routray]

Hi Xavier Fuentes,

As per my understanding of 1st Picking Warehouse Task creation:

-> 1 Step:Product's quantities are cumulated. I do not find any BADI here but code can be inserted via implicit enhancement. Problem is how to know these product/quantities would pick from Storage Type/Bin during cumulation. Suggestion: Rough Bin..not sure..other alternative as per your design

-> 2 Step: These cumulated product quantity then passed through for bin determination/WT Creation.

Wave Release Function Module: /SCWM/WAVE_RELEASE_1ST

Cumulate Function Module: /SCWM/CUMULATE_QUANTITY_1ST

Question: Did you try to map the same process with combined RF Picking ? You can activate combined picking for Activity Area as the same as storage type.

Please let us know how did you fix this issue.

Kind Regards,

Ajit

[xavier_fuentes_tafall_197]

Thank you for your interest, Ajit

Combined RF Picking is not possible because, normally, 2-steps Picking is already being used depending on the material master data.

As you well say, my problem is how to know if these products/quantities will be selected from the warehouse type for which I want do, always, two-steps picking during accumulation…

Because of this, I don't think the BAdI mentioned by Juergen will work: there, I already have the first step of Picking in two steps...

But... And if it is not necessary because I extract the stock of another warehouse type?

At the moment, I still don't know where, at what point in the process, to "attack" the problem, the question...

[alexander_pozhidaev_ti]

Hi,

Can you describe your requirements in details? Maybe you can use pick-point.

https://help.sap.com/viewer/3d97bec9bf1649099384bb8167df3cf2/9.5.0.2/en-US/52c8cb53ad377114e10000000...

BR, Alex.

[xavier_fuentes_tafall_197]

Dear Alexander,

I think that it's not the same.

One difference:

• Two-step picking "uses" wave management: for two deliveries, with the same product, the "picking" is done at origin for the total; you take it to an intermediate location and there you distribute the stock...
• With pick point, you'd go to the source location twice.

That's how I understand it.

[JuergenPitz]

Hi,

"I believe that in "Customizing" there is nothing for that: am I wrong?"

No, unfortunately not. Although that depending on the source storage type is more or less the only thing which would make sense to control 2-step picking, the standard has not control for that. Just like in ERP.

"Is there a "BAdI" or something for that?"

There is a long list of BAdIs, did you check? There is /SCWM/EX_WAVE_SAVE, change wave date when saving (or similar). I guess that would be it.

Brgds

Juergen

---
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!

[xavier_fuentes_tafall_197]

Hello, Juergen

I'll prove it, but I don't think your answer is good for my question:

"BAdI:: Change Wave Data When Saving

...

Requirements:

You can only change non-critical fields. If you save a wave and change fields that are contained in the structures /SCWM/S_WAVEHDR_NOCHG (for the wave header) or /SCWM/S_WAVEITM_NOCHG (for the wave item), the system does not copy these changes to this wave. You also cannot add any new wave headers or wave items, or delete existing entries."

[JuergenPitz]

Hello xavier.fuentes.tafall.1973 ,

well, did you check the structures? The field which controls the 2-step picking relevance is not part of the structure (AFAIK). I I also do not think that you wan to add any new wave headers, don't you?

Brgds

Juergen

[xavier_fuentes_tafall_197]

Hi, Juergen

Not really.

I'm gonna do it.

Thank you again