Hi, At this stage of the game I normally fire up SQL and edit the SY00500 table to 'free up' the batch. It doesn't fix anything necessarily, but It gives you a fighting chance at troubleshooting. In the SY00500 table I look at the following fields: (well, I really look at all of them for discrepancies with the other batches.) Marked to Post - MKDTOPST Checks Printed - CHKSPRTD Batch Error Message 1 - BCHEMSG1 Batch Error Message 2 - BCHEMSG2 Batch Status - BCHSTTUS Error State - ERRSTATE Typically, I only change the Marked to Post and Batch Status Fields. You should be able to print the edit lists after making the changes. The changes will allow you to open the batch. To troubleshoot this a bit, I'd look at my payables module's A/P trial balance and make sure there isn't anything hanging. Also look at the checkbook register to see if anything got as far as the checkbook. Finally look at the state of the GL. If your Payables are OK and your checkbook hasn't been touched, I'd be tempted to just delete the transaction altogether and start over. I'd probably just delete the batch unless I had some other transactions in it. I'd move the good transactions to a new batch and leave the bad one in there alone. Then I would delete the batch. Kind regards, Leslie
↧