Skip to Content

Error :

While creating the Payment Proposal for a Vendor open items through F110  , we were unable to process it. The payment proposal could not be found out and the Proposal Run log in Additional log tab, suggested to have a look at the run time error through ST22. Please note that we have SAP_FIN 720 implemented in our system.

F110 :

 

ST22 :

Analysis :

To begin with, all the open items were analysed and at the first instance, nothing looked unusual. However, when we had a close look, it was found that there were some open items related to prior FY and had been migrated to SFIN. The values of such documents were compared in 3 main tables such as FAGLFLEXA, ACDOCA and FAGL_SPLINFO_VAL.  While the values were identical for all the documents, it was inconsistent for 1 document.

To cross check, we exclude this document from the Payment Proposal and the same could be created successfully. So we decided to correct the value in the table directly with the help of our technical colleague.

We assumed that the values in FAGLFLEXA are correct since the document was posted before we migrated to S4 HANA Finance.

As per the Currency  Customisation for this company code, the additional 2nd local Currency is INR (OB22) but as it can be seen from the above that Crcy 3 is USD. The Amount in GC column holds a value ‘0’ which means the dr & the cr wont match and that is one of the reason of error.

The INR value in FAGL_SPLINFO_VAL does not match with the values of ACDOCA & FAGLFLEXA

 

Solution :

The Values in ACDOCA and FAGL_SPLINFO_VAL were changed and the values looked same in all the tables.

 

Result :

Payment Run was successful.

 

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.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply