Skip to Content
0

Delivery TO cancellation creates TO again (WMTA)

Dec 13, 2016 at 04:58 PM

44

avatar image
A K

Hello,

I am facing a issue where we are using the WMTA condition type in the Delivery to auto create the Transfer Order for the delivery. But in doing so when there is a need to delete the delivery it is required to first delete the TO to be able to cancel the delivery.

When the TO is cancelled using transaction LT15 it gets cancelled but in the delivery the WMTA immediately is getting inserted and creating a Transfer Order Immediately. Thus the user is not able to cancel the Delivery and is stuck.

The condition record for WMTA is maintained for immediate output as the need is to have the TO created as soon as the delivery is created.

I am not sure if this is the standard SAP behavior. I tried to search forums and internet but could not find any similar issue. Do you have any idea what could be the solution to this issue.

Thanks,

AK

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Jürgen L
Dec 14, 2016 at 12:46 AM
0

LT15 alone will not trigger another WMTA, for this somebody has to go into VL02N.

But you wanted to delete the delivery, did you do it? Is it deleted now? Did you get a WMTA for a deleted delivery?

Share
10 |10000 characters needed characters left characters exceeded
A K Dec 14, 2016 at 08:18 AM
0

Hi Jurgen,

Yes the TO got deleted using the LT15 transaction and when I went back to Delivery to delete it there is already a New WMTA condition inserted which created another TO so I was not able to delete the delivery.

So this goes in circle when I delete the TO system is inserting a new WMTA immediately and thus I am not able to delete the delivery.

Thanks

Show 1 Share
10 |10000 characters needed characters left characters exceeded

in OSS note 115690 - Direct transfer order for delivery (WMTA TS 4)

SAP says: "As a rule, message type WMTA should not be processed with time spot '4' (immediately). This is recommended for technical reasons."

0