Jonathan, I see that this is a payment application batch. One of the most common causes for such a batch to suspend is when the user selects a customer and enters a reference number and then goes back and tries to change either the customer number or the reference number. This results in a partial document for the original customer / reference number combination. What you need to do, after you have entered both a customer number and a reference number, and realize that one of them is wrong, is to click the delete button and respond that you want to delete the document (this is the one you just defined). You can then start a new document within the batch using the correct customer id and reference number.
Now, to determine if this is what happened with this batch you can look at the event log for the last release you attempted to see what is being reported as the reason for the suspended batch. If the reported error is an out of balance error then you likely have this issue. Correcting it requires some SQL Management Studio work as you cannot edit a suspended batch. Execute the following command (with xxxxxx being the suspended batch number):
select * from ardoc where batnbr = 'xxxxxx'
Look for a line with the origdocamt = 0. If you find it, execute the following two commands (where yyyyyyyyyy is the reference number of that document line and zzzzzzzzzz is the customer number:
begin transaction
delete from ardoc where batnbr = 'xxxxxx' and custid = 'zzzzzzzzzz' and refnbr = 'yyyyyyyyyy'
If that command indicates it deleted 1 record, execute the following:
commit transaction
If that command indicates it deleted more than 1 record, execute the following command:
rollback transaction
You should only be deleting 1 record at the ARDoc level so if it deletes more than 1 record you undo the delete with the rollback and check your command line to make sure it is correct.
If you did only delete 1 record then execute the following:
begin transaction
delete from artran where batnbr = 'xxxxxx' and custid = 'zzzzzzzzzz' and refnbr = 'yyyyyyyyyy'
If that command indicates it deleted 2 records, execute the following:
commit transaction
If that command indicates it deleted more than 2 record, execute the following command:
rollback transaction
There should only be 2 transaction records for a payment.
If both steps did what they should have done, go back and try to release the batch again.
If the event log indicated some other type of error or the first query did not find any records with a origdocamt of 0, report back what the event log stated.
