Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
Active Participant
0 Kudos
While trying to reverse an accrual document posted through transaction code FBS1, the system did not allow us to the reversal and the below error was displayed.

The document which was to be reversed look like the below :

Analysis :

As we can see that the above document is related to a Sales Order so we analysed the Sales order for that particular Sales order item 210. It was found that the same has been fully delivered and no delivery or invoice is pending against it.

Solution :

There may be a lot of other reasons for Error V1 131 : business transaction cannot be carried out and there are several OSS Notes are available for the same. However, in this case the reason of the error was found to be a simple one i.e. the status of the Sales order for that particular item.

The Status was FNBL MtoO RESA TECO i.e. its Technically Completed hence not allowing any posting. We changed that to the below

It was changed from “FNBL MtoO RESA TECO” to “REL  MtoO RESA” by selecting the “Reset” option of tab “Completed”

Result :

We can now being able to reverse the document through F.81.

*The above screenshot has been while doing Test run.

Suggested Reading for V1 131 Error : OSS Notes 580290, 548969, 157233, 316521, etc

I hope this content will be helpful to the SAP community members. If you have any feedback or idea to enhance this content, feel free to add your comment or simply share it if you liked it!

Disclaimer and Liability Notice :

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. The writer of this article and SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP and the writer of this blog responsible or liable with respect to the content of this document.
Labels in this area