Skip to Content

Unable to Cancel Material Document for Expense Item with Batch Management on.

Feb 27 at 08:47 AM


avatar image
Former Member

Dear Experts,

I am facing issue while posting cancellation of return delivery for Batch Managed Material Received with account assignment (Cost Center), Please let me know if there is some option in system to solve this problem or this is a system bug?

System Details: S/4 HANA 1709

Please help!

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

1 Answer

Jürgen L
Feb 27 at 09:07 AM

Why did you explicitly mention " for Batch Managed Material" while none of your screenshots from the movements shows any batch number?

Did you switch on batch management after the initial receipt?

The whole message has a different structure than usually for this M7021 message

The first part of the message does not make much sense at all, there are usually the abbreviations which are explained in the long text, and on the right side I see a 0004000000 which is probably the batch number, but from where is this batch number coming? Do you create batches when doing cancellations? Did you enter this number after you made the screenshot of the movement?

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

I have mentioned Batch Managed as there is nothing wrong with non batch managed materials & 0004000000 is supplier code.

Batch was already on and this is happening with all the materials which have batch management enabled.

When GR was posted no batch was created as shown in the screen shots also while posting cancellation of GR there is no batch there but still system is giving this error of Quantity. As it a non stock (Direct Expense) transaction system should not check the stock level at all. I have a doubt that it is a system but just need to make sure before going to SAP.


I can just recommend to open a call at SAP Support, even the supplier number does not make any sense in this message, at least it has never been this way before S4HANA