Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
I get this error when posting a Financial Batch Transactions->Financials->Batches
What could be the reason and how do I fix it?
I found this list of Batch Statuses from Accolade's old web site:
1 Batch is currently posting.
2 Batch is currently being deleted.
3 Batch currently receiving transactions from outside the module.
4 Batch is done posting.
5 Batch is currently being printed.
6 Batch is currently being updated.
7 Batch was interrupted during posting.
8 Batch was interrupted during printing.
9 Batch was interrupted during updating of tables.
10 Recurring batch has application errors and one or more transactions did not post.
11 Single-use batch has application errors and one or more transactions did not post.
15 A posting error occurred while trying to post a batch of computer checks.
20 Batch was interrupted during the processing of computer checks.
25 Batch was interrupted during the printing of the computer check alignment.
30 Batch was interrupted during the printing of computer checks.
35 Batch was interrupted during the printing of a check alignment form before reprinting checks.
40 Batch was interrupted during the voiding of computer checks.
45 Batch was interrupted during the reprinting of computer checks.
50 Batch was interrupted during the processing of the remittance report.
55 Batch was interrupted during the processing of the remittance Alignment report.
60 Batch was interrupted during the printing of the remittance report.
100 Batch is processing computer checks.
This Batch Status field is in the SY00500 table in the company database.
Also, if you have any modified forms or reports, export them to a package file, create an empty reports dictionary and try again. Next, import the package files you created earlier into the blank reports dictionary.
You could also try to rebuild the auto procs by dropping and recreating them in the SQL maintenance window.
The last thing I can think of is to go into the Database Maintenance Utility and recreate the stored procedures.
Thanks but it didn't answer my question.
So what was the answer?
What was the answer?
Usually, the following Microsoft Support article takes care of this problem:
The batch was named as the GP user ID; renamed the batch and it fixed the problem.
yes, but do not use an user id for the batch name.
Open up the batch, rename and save it with the new name.
Business Applications communities