You’re offline. This is a read only version of the page.
I have a payment applications where if I run the payment applications details the batch totals $83,500 but when I look at the batch on the screen and run a quick query of it, the batch totals $88,500. The $5,000 difference was not posted and it never should have been a part of the batch. It is actually a duplicate of another item that is part of the payment application batch. I want to go in and remove the $5,000 from the batch as it relates to a different payment application but I can't get to it. Any suggestions on how I can do it?
- Thanks
*This post is locked for comments
The SQL Management Tool is not part of Dynamics SL but, rather, part of SQL Server. You will need someone who has access to SQL Server run those queries for you if you do not have access to this tool. Running delete queries with this tool can be dangerous so that is best left to someone familiar with running SQL commands as the wrong syntax or missing where clauses can delete an entire data table content. Your SL partner should be able to do this for you.
Unfortunately, once a batch suspends you cannot access it with any SL program. It is my understanding that the next version of SL (SL 2015) will allow the user to delete a suspended batch but you have to have been granted initialize rights to do that.
Thanks for responding. One questions - how do I get to (where do I find) the SQL Management tool?
Thanks
Leah,
This issue can occur if you start a payment document entering the customer id and reference number and then go back and edit either the customer number or reference number. Once those 2 fields are entered they establish the record. So, if you need to edit either of these fields you need to use the delete key to delete the partially started record and then click new to restart the correct payment document.
So, now that you have a batch that is basically out of balance but released (you did not say it was released but I suspect that is the case) you have to remove the partial document. That has to be done with a couple of queries using the SQL Management tool.
First, execute the following query to find the document to be deleted (xxxxxx is the payment batch number):
select custid,refnbr,origdocamt,* from ardoc where batnbr = 'xxxxxx'
Look through the results for your offending document. There should be a custid / refnbr combination that does not belong in the batch. When you find it, execute the following two queries:
delete from ardoc where batnbr = 'xxxxxx' and custid = 'yyyyyyyyyy' and refnbr = 'zzzzzzzzzz'
delete from artran where batnbr = 'xxxxxx' and custid = 'yyyyyyyyyy' and refnbr = 'zzzzzzzzzz'
In the above, yyyyyyyyyy will be the customer id of the bad record and zzzzzzzzzz will be the reference number of the bad record. Once the 2 delete queries are run you should be able to release the suspended batch on the release batch screen.
If you do not find the condition described above, respond back and we can look at some other ideas but what I have described is fairly common with my clients and the above resolves the issue.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (