cancel
Showing results for 
Search instead for 
Did you mean: 

Withdrawl from HU xxx only possible if total amount of HU is withdrawn

Hi experts,

we have a repack scenario during outbound process, the whole source HU will be picked with several WO/WTs, the destination HU same as the source HU within WT items, which cause the confirm WT error "Withdrawl from HU xxx only possible if total amount of HU is withdrawn ".

I would like to know where to confirge it to make the destination HU same as the source HU, how system define a action is Whole HU picking?

From my point of view, as it's a repack process, each WT should have a different package to generate their own HU, if the pack spec is not exist, then just keep the destination HU field empty and pop-up warning or error when confirm it.

BR

Yi Chao

0 Kudos

the destination HU equal to the source HU
Daniil
Active Contributor
0 Kudos

If I remember correctly, usually system doesn't set HU withdrawal flag + suggest source as a destination, if you have more than one WT.

Are these WT not from standard?

If by the process you need to move whole HU somewhere, and create there target HU's it sounds like a "pick-point" process.

With pick and pack steps you do picking without hu withdrawal and use pick HU. After this pick HU goes to the repackaging station.

And confirmation of your WTs is possible (or should be possible). Confirm in foreground in monitor, there you are able to change hu withdrawal flag and a destination HU

0 Kudos

Hi Mazurkevich,

We have several operations before these WTs creation:

1. Do the repack calculation for the outbound in a enhancement program, get the result of how many variant packages should be used to pack the target quantity;

2. Create a wave manually, use the wave type WT01, which will use the repack calculation result, input the outbound document and assign to this wave, then release it;

3. The WTs created according to the calculated target boxes, the destination HU not created yet, in the RF operation, user should scan the destination box barcode and manual assign it as destination HU, then confirm the picking WT.

But in the foreground WT details view, if the whole HU was picking during this process, the destination HU field filled the source HU number, I have to change them one by one manual, so I would like to know how does it happen and how can I make destination HU emtpy in the WT?

BR

Yi Chao

Daniil
Active Contributor

Hi Yi,
So as I said, it does not seems to me as a standard behaviour, standard usually checks if more than one WT creates from source HU, it is no HU removal flag. It make sense to check once more that no enhancements are involved into WT creation itself.

Anyway you can check as well customizing of the process type in the goods issue section should be one symbol customizing for the pick HU behaviour:

0 Kudos

Hi Mazurkevich,

Thanks!

I have checked this field of the WT process type and it's value already maintained as 3, but it seems not useful, there should be some others element impact the WT creation, especailly the HU picking and assignment.

Daniil
Active Contributor
0 Kudos

Hi Yi, you can check as well similar customizing in a source storage type, and recreate WT's to see if it helps.

0 Kudos

Hi Mazurkevich, yes, I checked both of the storage type picking control (no value)and warehouse process type control of HU pick( value 3), they are not match the whole HU picking situation.

What makes me confused is, if there just one WT and the request quantity equals to the target HU quantity, then it's whole HU picking, the destination HU is source HU. But in this scenario, one outbound delivery document (warehouse request), generated multiple WO/WT to pick one HU, in spite of the whole source HU is picked, but in different destination boxes, the destination HU fields should be not take the source HU but keep it empty or use other created empty HU. I have no idea if any more configuration impact it, or maybe control it in BADI.

Thanks!

Daniil
Active Contributor

Hi Chao,

If you familiar with debugger, you can check system behaviour in the functional module /scwm/*hu*homog* (something like HU homogenial Set).

It sets homve and movehu flags.

I am not sure, but since you mentioned packaging proposal, maybe thia is strange behaviour comes from warehouse order creation with cartonisation planning. But sure if it is possible to set there real HU as planned HU for all warehouse tasks.

Hope it helps

Hi Mazurkevich,

It's now my direction to research this problem, any result I will update following.

You are so nice, Thanks for your patient help! 🙂

BR

Yi Chao

Accepted Solutions (0)

Answers (0)