Deivery document deleted after TO confirmed

[Former Member]

Hi Gurus

TO is created with reference to delivery document .TO got confirmed so the stock moved to 916 . after that delivery document got deleted . But the stock lies in 916 . how to reverse the  stock from 916 .

Thanks and regards

SKB

[mihailo_sundic]

As everyone said you can use LT01/LT10, but that won't solve the problem. To me, the problem is actually the reason that this happened and that's a config issue, see below.

What you need to do is disable the possibility to delete delivery item or complete delivery after TO is confirmed for that delivery (item). For that, you can use t-code SE91 and find message VL173 - set it from Warning to Error.

In this way, nobody will be able to accidentally/purpously delete confirmed item/delivery.

This is a very useful thing to set up in WM as you don't want any possible complications.

When you set VL173 as error, you'll first need to do LT0G before the delivery (or item) deletion. This way you control your process entirely, and no loose ends like your problem will appear.

[former_member576026]

Hi,

You can move the stock from 916 back to the warehouse via LT10/ LT01 in this case.

BR
Zhao

[Lakshmipathi]

Moved from SAP ERP Sales and Distribution (SAP SD) to ERP SCM Logistics Execution

[Shiva_Ram]

Use t.code LT0G to move the delivery stock back to normal stock. Check with your MM specialist on the movement type that you need to use.

In future, if you want to avoid this situation, not allowing deleting delivery when transfer order exists, follow the procedure given in OSS 1463938 - How to prevent the delivery deletion after the transfer order is confirmed

Regards,

[JL23]

Are you sure you can do LT0G if the delivery was deleted, I doubt as LT0G is made to unpick the picked quantity in a delivery, but without delivery it can't reverse the picked quantity in the delivery.

So just a standard LT01 with movement type 999 should be sufficient to get the stock back from 916 into the bins.