Balance in transaction currency is too large for automatic correction

[marceloromeiro]

Hi all,

I'm facing a problem with the Journal Entry - Clearing (Asynchronous) API in an SAP Public Cloud environment. I developed it based on a community post (https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/guidelines-for-api-journal-en...), and I'm receiving the following error: 'Balance in transaction currency BRL 1,157.74- is too large for automatic correction.'

I've tried making various adjustments, modifying the payload, and only had success when I performed a partial clearing with 0.01 (where I believe there's some tolerance the system has when validating the balance).

Has anyone used this API or experienced a similar problem when clearing documents?

These are some links I used as references in this development:

• Journal Entry - Clearing (Asynchronous) Documentation
• Guidelines for API Journal Entry – Clearing (Asynchronous)

Best Regards,

Marcelo

[marceloromeiro]

I'm also looking at this post (https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/a-simplified-guide-to-effecti...) to solve my issue.

In that example, the author passes two document types, RE and KZ (payment and invoice entries), in the payload.

In my scenario, I'm only passing the RE document.

Do I need both document types to fully clear an open item?

[Jeremy_Deo · Accepted solution]

Hello again,

Considering that this is an application whose primary function is the reconciliation of accounting documents, it would seem logical to me that the scenario includes an invoice (RE) and a manual payment voucher (KZ) yes.

In any case, accountingly speaking that's what makes the most sense.

Best regards,

Jeremy

[marceloromeiro · Accepted solution]

Hello Jeremy,

[marceloromeiro · Accepted solution]

Hello Jeremy, I will try to post a manual payment and then run the API with both sets of information to see if it works.

[marceloromeiro · Accepted solution]

After analysis and tests to discover what could be happening, I realized in an example scenario that both documents were being passed to this clearing API: the invoice, a document of type RE, and the vendor payment, type KZ.

For this API, both documents must be passed together, one as a credit and the other as a debit, where one will be positive and the other negative. As expected, the sum of the lines must be equal to 0, otherwise you will receive this balance error.

For my scenario, I implemented the Journal Entry BOI, posting a document of type KZ and then called the clearing API. Just one point of attention: it's the item that will be passed for clearing. In my case, I had to pass item 2, because item 1 was returning a message that was already cleared item.

Thank you for your help, Jeremy, and I hope this has helped you all.

Best Regards,

Marcelo R.

[Jeremy_Deo]

Hello again dear user,

I found another answer in the SAP community that might be useful for you.

Here's the link below :

https://community.sap.com/t5/technology-q-a/journal-entry-clearing-asynchronous-soap-api-error/qaq-p...

I hope thiw will help you this time.

Best regards,

Jeremy

[marceloromeiro]

Hello Jeremy,

I checked the post and saw that there is an SAP note (3080961 - SAP Fiori: Tolerance check with maximum percentage rate) that makes an adjustment.

Since our environment is Public Edition, the note is already applied.

I'm debugging this tolerance code to see if I can identify what's wrong, but without success so far.

[Jeremy_Deo]

Hello dear user,

I've never faced such issue before but I might find a solution to your issue.

Can you flag the checkbox “FX Rate First Item” in the app “Edit Options for Journal Entries - My Settings" and proceed again ?

Hope this will help you solve your issue.

Best regards,

Jeremy

[marceloromeiro]

Hello Jeremy,
Thank you for the response.
I made the adjustments and continued to receive the same error.
I tested with my user, as I believe this configuration is user-specific, but in my case, it will be executed by a communication user.