Automatic source HU determination in picking from bulk storage in EWM

[sandeepk6891]

The level of available quantity field in bulk storage type cannot be set to blank(highest level HU). So we cannot determine the source HU automatically for pick warehouse task from bulk storage type. As a result we have to enter source HU manually during warehouse task confirmation.

Our client requirement is to determine source HU automatically to avoid this manual work.Our client is not using RF and not interested in doing this manual work. Moreover since the HU requirement is mandatory for bulk storage types we ended up creating HU Ids during Putaway using bulk strategy

Is there anyway system can propose source HU automatically during the pick warehouse task creation from a bulk storage type.

or

Is there anyway we can do putaway into bulk-storage type without HU Ids

[sandeepk6891]

Hi Daniil,

They wanted to use bulk storage for capacity management i.e max number of HU's (and a specific HU type) that can be stored in a bin type as well as in the format of the number of stacks and rows.

We tried using pallet strategy(without HU requirement-HU Ids) but the requirement of setting number of stacks and rows are not met.

[Daniil]

Hi Sandeep, if max number of HUs should be limited it requires as well to have HUs. Otherwise system cannot know how many HUs are in the bin. In goods receipt process you can use Packaging specification to generate HUs in advance. Not sure how stock removal is done from the bulk in your processes, but if it is does not matter which HU is taken you can maybe with development fill the HU Number during WT confirmation. Or you can adjust WT creation to have HU wt created in advance, it will split Aqua and picking WT can take in this case the exact HU, and you confirm both WTs at the same time. I do not know any solution with standard.

BR,

Daniil

[Daniil]

Hi, is there any reasons to use Bulk storage type?

[Andreas_Mergler]

Hi,

that was my first thought, too. Why use bulk storage if you do not want work with HUs?

Bulk storage will only work in a reasonable way if you have HUs. And if you can pick any HU in a bulk bin - there is no real sense in telling the operator to pick a specific HU if that HU is located "in the back" and / or in the middle of a stack.

BR Andreas

[sandeepk6891]

At present they are using WM and WM supports bulk strategy without creation of SU-ID.They are comfortable with that process.So the first requirement is to use bulk strategy without HU-ID.

If bulk strategy is used to ease operations to pick anything that is readily available and if you are not interested in tracking using HU-IDs i think it makes sense.