Do not get canceled movement 331 movement 332

[82000051]

Colleagues, please help me. By an erroneous movement 331 wrote off finished products to samples, now I can’t cancel this movement. I tried both in MIGO and in MB1A, everywhere you need to enter a cost center. But the write-off took place without specifying the cost center, I can not specify it.

Can I use the 552 movement?

[VeselinaPeykova · Accepted solution]

Use MBST transaction to reverse the document with 331 movement type, then create the correct document with the movement type that you intended to use.

As an alternative - you can use transaction MIGO, select A03 - Cancellation R02 - Material Document.

Edit: 552 does not seem to be the right approach for reversing the incorrect posting, 552 is for reversal of scrapping while you made 331 - GI to sampling QI. For 331 the reversal movement type is 332, not 552.

[82000051 · Accepted solution]

Good afternoon, thanks for the reply. Unfortunately MBST does not work with this type of movement (

Like cancellation in MIGO by document number.
A 332 reverse movement requires a cost center

[VeselinaPeykova · Accepted solution]

82000051 what you describe is strange and does not look like standard behavior.

I just tried 331 via MIGO and the cost center is determined automatically at document save; 331 and 332 in the system that I used have the same field selections; reversal to the document with 331 uses the information from the original document...

Check if somebody has modified the standard settings for MIGO/MB* transactions.

The reason why I would not use 552 is that at least in the system that I checked the postings are quite different compared to 332, so using 552 will not be a real reversal. This is why I believe that it makes sense to find out why 331 works differently compared to 332.

[82000051 · Accepted solution]

Got it, is there a problem with setting up the transaction itself most likely?
I will open a request for correction
Thank !

[VeselinaPeykova · Accepted solution]

82000051 if you are not authorized to display/modify configuration settings in SPRO then yes - you need to submit a ticket to your local support desk so that they can investigate and propose a solution.

[82000051]

I think that the problem is that when posting 331 the transaction QA 11 was used, I can’t cancel it in MIGO. Perhaps something like through the creation of an inspection lot?