Delete a delivery document when open transfer order exists

[Former Member]

Hello Gurus,

I have searched this forum completely before posting this question. But I couldn't understand on how it happened from any of the answers.

Ideally, the delivery document cannot be deleted when it has a TO on it but when it is deleted, we can follow the steps below

· Go to LT12 (confirm) or LT15 (cancel) and enter the warehouse number and TO number

· On this screen, start debugging by entering /h in the command line and press enter

· Single step (F5) until LTAK-VBELN is filled Clear the value and click on the update (pencil) icon

· Now proceed with continue (F8) Press save to cancel / confirm the TO

But I couldn't understand on how the system allowed to delete the delivery. I tied a lot, but I couldn't delete a delivery which has a TO. Please tell me the reason for this inconsistency. How is it possible?

BR,

Swathi

[Former Member]

hello gurus,

I the solution of the issue is known and fixed.

But what I failed to know is:

1) How the system allowed to delete the delivery document despite open TO? (without any error/ warning)

2) Why did it happen one time only? ( I tried to replicate with the same set of data but I couldn't delete, even the user couldn't do it for 2nd time)

3) Does it depend on anything else otherwise (based on any prerequisite/ setting/ config)?

Please reply.

[phanikumar_v3]

In standard system you can delete a delivery even though the transfer order exists.

System will not throw any warning/error for this.

May be you included VL173 in your OVM1 settings--any changes here you find??

Pl update.

Phanikumar

[Former Member]

Hello,

I dunno. I was never allowed to delete the Delivery with open TO.

Infact the user was able to do it but for one time only.

So wondering what could be the reason.

Does it depend on anything else (prerequisite/ setting/ config)?

Please share if you know it.

Thanks,

Swathi

[phanikumar_v3]

Dear Swathi

It can be done with user interference if they are allowed for transaction code OVM1.

If you keep VL173 message type with W/E--then only system will caution the user.

But if you keep VL173 with message type BLANK--then system will not throw any caution--simply deletes the delivery by user.

Might be this is in your case,user have used the lag of SAP and might be playing.

You can test this whatever i suggested.

Here, only one thing can help you--you need to catch the changes in table--V_160MVL with your Abaper.Hope this helps.(remove the authorisations of OVM1 to such users)

Pl update...

Phanikumar

[Lakshmipathi]

If the issue is for all the deliveries, then you can check the configuration.  Since it has happened only for a particular delivery, the only option could be direct table entry deletion.

G. Lakshmipathi

[Former Member]

Thanks for your reply Sir!

The issue was with one delivery only and that was fixed with ABAP debugging. But I wonder what could be the root cause or how the system allowed it just for one delivery when it has a TO. When I tried it, I couldn't delete any delivery which has a TO.

[Lakshmipathi]

Even if there is a subsequent document, you can very well delete directly from table

G. Lakshmipathi

[Former Member]

Hi Swathi,

As you have already explained you should not be able to delete the delivery when the TO exist, it

seems that the user  somehow managed to delete the link of the reference delivery.

Regards,

Enrique

[Former Member]

Yes, But, the system did not give any warning/ error message to the user when performing the deletion. But For me, It threw an error message when tried to replicate it.

[Former Member]

Hi Swathi,

Did you read my first reply?

1. Reason and how to prevent this:

A delivery could be deleted as it wasn't possible in former releases to
return the materials back to stock (with transaction LT0G) which could
cause a kind of deadlock. Nowadays it is possible to return materials
and to update the delivery. Nevertheless the deletion of the delivery
could still be controlled by a message.

If your materials will be loaded to a truck immediately, then of course
it is not that easy to return the materials from the 'interim bin'.
In such cases you could use the controllable error message VL 173
to prevent the deletion of a delivery if a transfer order exists.

Therefore please maintain message VL 173 as an error message (type E
not W)

with transaction 'OVM1' or within customizing:

  Logistics Execution
    -> Shipping
      -> System Modifications
        -> Specify Characteristics for System Messages
          -> Define the message types of system messages

Afterwards you should receive an error message as soon as you try to
delete a delivery with an existing transfer order and it won't be
possible to delete the delivery.

2. How to cancel open transfer orders where delivery has been deleted.

  Please check KBA 1454038 ~ How to Cancel / Confirm a transfer order when the delivery h

Could you please check whether error VL173 has been maintained as well as the suggested KBA?

Regards,

Enrique

[venu_ch8]

Dear  Enrique Sosa Dominguez

Small doubt on this VL-173 Will control whether system will allow to cancel the delivery Even ofter TO Creation

but 

The issue was with one delivery only and that was fixed with ABAP debugging. But I wonder what could be the root cause or how the system allowed it just for one delivery when it has a TO

But it happened to only one delivery only not with all delivery so why can check here

Regards

venu 

[Former Member]

You are correct Venugopal.

[Former Member]

Hi Swathi,

1. Reason and how to prevent this:

A delivery could be deleted as it wasn't possible in former releases to
return the materials back to stock (with transaction LT0G) which could
cause a kind of deadlock. Nowadays it is possible to return materials
and to update the delivery. Nevertheless the deletion of the delivery
could still be controlled by a message.

If your materials will be loaded to a truck immediately, then of course
it is not that easy to return the materials from the 'interim bin'.
In such cases you could use the controllable error message VL 173
to prevent the deletion of a delivery if a transfer order exists.

Therefore please maintain message VL 173 as an error message (type E
not W)

with transaction 'OVM1' or within customizing:

  Logistics Execution
    -> Shipping
      -> System Modifications
        -> Specify Characteristics for System Messages
          -> Define the message types of system messages

Afterwards you should receive an error message as soon as you try to
delete a delivery with an existing transfer order and it won't be
possible to delete the delivery.

2. How to cancel open transfer orders where delivery has been deleted.

  Please check KBA 1454038 ~ How to Cancel / Confirm a transfer order when the delivery h

Regards,

Enrique

[Former Member]

VL 173 is not maintained. I will maintain and update you.

[Shiridi]

Is this the correct KBA number that was provided?
"KBA 1454038 ~ How to Cancel / Confirm a transfer order when the delivery"

Regards

Shiridi Srinivas