HU is assigning to delivery before confirmation of the TO

[Former Member]

We have SU managed warehouse. And two step confirmation.

While users doing 2nd step of confirmastion with the RF t.codes, some times users facing the error message that "HU is already assigned to the delivery"

While observing the in the delivery HU will be appear in the "pack" icon and delivery data is being updated in the HU object table (VEVW).

But data in VBFA is not being updated.

The normal behavious should be TO should be confirmed along with that delivery data should be updated to HU tables and VBFA table should be updated.

In this case we suspecting due to some inconsistancy delivery data is being updated in the HU tables before TO tables updataion. Later while system updating TO tables finding that HU data already having delivery information.

Could any one please suggest is there any solution for this problem or any correction note available?

[Former Member]

Hi,

Did you set up 'HU picking control' at the movement type to 'Adopt source HU as Destination HU'.

Vinod.

[Former Member]

Hi Vinod,

Thanks for the reply.

We have the value "1" (Propose source HU as Destination HU) in the HU picking control.

But I dont think this field is the control for my issue.

We are having SU management. You might be knowing picking for the delivery is alway being via TO.

The normal process is below.

1) TO should be confirmed with the required SU. Along with the confirmation of the TO, system updates the SU number in the delivery. We can see the HU number in the pack icon. Also can see the HU in the document flow.

In our case users does the confirmation in two steps with RF scan.

Step 1) Picking confirmation.

Step 2) While doing transport confirmation (putaway), they are getting error message that, HU is already assigned to the delivery.

Simtoms

1) In the document flow we couldn't see the HU data (VBFA table is not updated)

2) In the pack icon we could see the HU number. In VEKP and VEPO tables delivery number is being updated.

We are suspecting that users are doing some thing wrong while scaning with RF scanner.

When we asked the user they said that while confirming the TO with scanner, by pressing some wrong button like F7 etc, they are getting this problem.

Hope you understood the issue.