We get an error message that says that the batch is out of balance, even though it is not!
*This post is locked for comments
Reading what you responded with it sounds like the batch that has the issue is not the invoice and memo batch that created the credit memo but the subsequent payment application batch where you applied the credit memo and the issue occurs during the release of that payment application batch. If I am wrong on this then the following does not apply.
The payment application batch creates a document as soon as you select a customer and enter a reference number. If you go back and edit either the customer or the reference number field, the screen creates a second document for the edits leaving a partial document out there for the first combination. this may be your issue but there are some other possible causes as well.
To resolve the problem you will need to run a couple of SQL queries to determine the problem and fix it. First you need to look at the documents associated with the payment application batch using the following query
SELECT * FROM ARDOC WHERE BATNBR = 'XXXXXX'
Substitute the XXXXXX for the payment application batch number. If the only item in that payment application batch is the application of this credit memo then this query should come back with nothing as there should be no new documents. If the application of that credit memo was done along with new payments, the only documents should be for the new payments. The action taken on the ARDoc table depends on whether you have new payments or not and what this query finds. Report back to me what the query finds and whether there are new payments involved or not. Based on what you report I will advise what the next action should be.
It is an an Accounts Receivable batch (Invoice and Memo (08.010.00) for a Credit memo to be applied to an invoice. When the credit memo is applied to the invoice and posted a system error 6124 message was received.
It would be helpful to know what kind of batch you are talking about (what module) but certain SL screens (like the AR payment application batch) can create a "ghost" document that will cause this error.
Are you getting this message while releasing the batch or when trying to save it? If it is during the release then there are several more factors that can cause this.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Andrés Arias as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
