102 movement not cancelling the 101 Unconfirmed Transfer Order

[Former Member]

Hello,

When user create a GR with 101 movement against PO system creates a Transfer requirement which gets automatically converted to transfer order as per configuration.

Immediately after making the GR user realized that he has made a mistake and needs to cancel the GR. So for this He will use Cancel Material document  option and with102 movement type he creates another material document. This again creates a TR,TO and confirms it immediately.

But this 102 is not cancelling the Unconfirmed TO created by 101. Can you please help understand what is the setting required so that the 102 movement should automatically cancel the unconfirmed TO created by 101 movement.

Thanks in advance for your help.

Rgds,

AK

[MANIS · Accepted solution]

To created as a result of 101 is having the reference of TR created for the initial material document  now since you are cancelling this you need to return back the stock to 902

normally the process flow is once you perform the GR against PO

it post the stock to 902 now in your case you mentioned automatic TO gets created and confirmed so check what is the destination storage bin in the first TO (Once TO confirmed you cannot cancel it)

Now as a result of cancellation you will have Negative Quant in 902 so using T-Code : LT01 or LT10 you can transfer the stock from physical bin to 902 to make it zero

[Former Member · Accepted solution]

Hello Manish,

When I do the GR the TR and TO is created please note that the TO is NOT confirmed and now we process the GR reversal. In such case what is the standard SAP behavior.

Thanks,

AK

[JL23 · Accepted solution]

A goods receipt in MM creates a quant in the interim storage type and a Transfer Requirment, thats it. A conversion from a TR to TO, no matter if manually or automatically is a separate process step

And because of that, a cancellation can only create quant and TR with opposite signs.

If you have not yet done the follow on process of TO creation then the quant and the TRs equalizing each other and vanish both from the system.

With an existing TO you have to do it manually.

[Former Member · Accepted solution]

Hello,

The reason I am asking is I was getting a different behaviour from the system earlier which was as below:

1. GR Steps :

                     101 movement --> 5XXXXXX301  --> TR 178 --> TO 542 (Unconfirmed)

2. Gr Reversal:

                     102 movement --> 5XXXXXX302  --> TR 179

With this 102 system was earlier Cancelling the TO 542 and in the TR 178 when displayed showed a dummy TO which was 5XXXXXX302 and in the TR 179 it showed a dummy TO 5XXXXXX301.

Suddenly this behavior stopped and now Both TR (for 101 and 102 mvt) have there separate TO's which have to be confirmed to see the correct stock position. So I was trying to understand is there something I could have changed that is causing this ? Also we recently moved to EHP7 not sure if that could be causing this. Please advise.

Thanks,

AK

[JL23 · Accepted solution]

I am far away from EHP7, my observation and answer is based on an extra test that I made in my system

[Former Member · Accepted solution]

Hello AK,

If you are looking for a Solution, Cancel the Transfer Order # 542 using LT15 and then you can delete/Close the TR# 178.

About 101 TR showing the TO of 102 Movement and Vice versa, I have never heard of any such functionality as both the Movements are handled separately in WM.

Thanks,

Sai Arala.

[raghug · Accepted solution]

I checked both in a EHP7 and on an older release 700-0019, and neither one of them cancel the original TO created on the inbound step. I don't ever remember SAP doing anything to an open TO from an IM movement natively dating back to 3.1H... are you sure there wasn't something custom in your system?

I did however notice a difference in the TRs. On the older system, when the 102 reversal was done, the TR for the 101 had a header status of 'E' for complete and there was on TR for the reversal. Once I cancelled the original TR using LT15, the TR header was put back to blank, which means it is still active.

On the new system, creating the 102 created the new TR but also kept the old TR marked as 'E'. This is correct in my opinion.

In both cases, however, I was left with an orphaned TR for the reversal that I couldn't do anything other than manually mark complete or delete.

[Former Member · Accepted solution]

you need to cancel to manually first then you do the reversal

[raghug · Accepted solution]

Yes, Rashi, if you read the chain, the original poster A K was suggesting that in the older pre-EHP 7 system they upgraded from, the TO was automatically getting cancelled. What version of SAP are you on?

A K - What version of SAP did you upgrade from?

[Former Member · Accepted solution]

I am using EHP 7 ,

I dont see being cancelled automatically,

AK

if you were getting automatically TO cancelled in earlier version a s you have mentioned, and after upgrade it is not happening

so really you will be having

your earlier version  system, because after upgrade we have the earlier version to debug the issue doing comparison,i

You will be having quality client, login to the qa

IF that is found in your qa system then you can raise to sap for the help,

Regards

Rashi

[ankurch]

This message was moderated.