on 11-08-2014 7:05 AM
Hi Experts
In Two-Step Picking in Extended Warehouse Management the system picks stock from earlier "Release Withdrawal" stock which is at standard Intermediate storage type for two-step picking (2010).
The Process is ....
1. Create Wave
2. Assign outbound Delivery Requests to Wave
3. "Release Withdrawal" - First step in 2 step picking , the stock is removed from High Rack source bin.
and moved to intermedicate storage type 2010 for 2 step picking.
The system creates WO / WTs for deliveries assigned.
Confirm WO.
4. Step 2 in 2 step is allocation .... so from WAVE - "Release"
When you release wave the system picks stock from intermediate storage type 2010
which is removed in step 1 from source bin ( in High Rack).
The issue is , in 2nd step the system picks stock (HUs) from earlier "release withdrawals" from 2010 and
allocates it to deliveries for which it was not withdrawn.
say for
Wave :1 --> Deliveries assigned : Del 1 , Del 2
First Release withdrawal - HU1 and HU2 are removed for deliveries Del1 and Del2.
The HUs are at 2010 --> HU1 and HU2
Wave:2 --> Deliveries assigned : Del3 , Del4
Release withdrawal for this step removes HUs --> HU3 and HU4.
The HUs are at 2010 --> HU3 and HU4.
Now when we release wave 2 for allocation (by "release" button) ,
the system picks HUs from first wave HU1 and HU2 which are not relevant for wave 2 deliveries.
For wave 2 actually "release withdrawal" has removed HU3 and HU4.
Any idea , how to set it right so that correct HUs are picked for corrosponding waves ?
Thanks in advance ....
Regards / Vinod
Hi,
the behaviour you describe is the standard behaviour. It is actually different from ERP WM, where the system works with dynamic bins in the 2-step picking process, and by that you have some assignment between the material picked in the first step and the WT in the second step - whereas of course a dynamic bin is also nothing you can physically find in the warehouse, so it might not really help you. I also thought this is some kind of gap in the functionality of EWM - but is it really? Why do you need to pick in the second step from the "correct" HUs?
Brgds
Juergen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Juergen
Thanks for your explainations. The "correct HUs" are required because user has scanned full HUs from the source for the deliveries the wave is assigned. Picker has information of respective deliveries for which wave1 is released and HUs are to be picked. But in the meantime another wave (say, wave2) is released and the HUs from earlier wave for some other deliveries are available for picking as suggested by the system. This I think as u said is really a gap. Is there any other way of correcting this situation by Badi or some enhancement program ?
Regards / Vinod Sedani
User | Count |
---|---|
7 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.