Computer Check Batch stuck in Batch Recovery Limbo!

[Ryan Hobbs]

We have a Computer Check batch whose status is "Computer Check Posting Error"
(SY00500.BCHSTTUS = 15). If we try and open via the Payables Batch Entry we
receive: "You cannot edit the batch or transactions in this batch. Use the
Batch Recovery window to continue processing this batch."

So, onto Batch Recovery:

This begins a never ending loop.

Batch ID in question is selected and "Marked" and [Continue] is selected to
process and we receive: "Data entry errors exist in batch <BATCH ID>. Use the
Batch Recovery window to process this batch.

Any suggestions on how to end this loop and resolve the issue?

FYI: We are using Safe Pay and the Safe Pay [Load / Reload Transactions]
brings in 0 checks with $0.00 and the batch in question appears in the Safe
Pay Upload History. We are running MS Dynamics GP Professional 9.00.0259
with SQL Server 2005 - 9.00.2047.00 ODBC Driver.

[rc]

This post might be inappropriate. Click to display it.

[Leslie Vail]

Do you have any idea what Batch Status 15 means?

[rc]

Batch Status 15 = Computer Check Posting Error

Post by Leslie Vail
Do you have any idea what Batch Status 15 means?

[Leslie Vail]

Here's the status definitions I have so far, can you add more to the list?
This doesn't seem to be documented anywhere:
0 Available
1 Marked to Post
2 Marked to Delete
3 Marked to Receive
4 ?
5 Printing
6 Updating
7 Posting Interrupted
8 Journal Printing Interrupted
9 Table Update Interrupted
10 Recurring Batch Error - Edit Required
11 Transaction Error - Edit Required
12 ?
13 ?
14 ?
15 Computer Check Posting Error

Post by rc
Batch Status 15 = Computer Check Posting Error

Post by Leslie Vail
Do you have any idea what Batch Status 15 means?

[SHEIKH ASIF]

Hi, Leslie,

Here are these:

0 = Available
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. Edit Required
11 = Single use batch has application errors and one or more
transactions did not post. Edit Required
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.

Regards,
Sheikh Asif

[Blythe Nichols]

We are on MS GP10 and have encountered the exact same issue. Has anyone discovered a solution when this happens?

Post by Ryan Hobbs
We have a Computer Check batch whose status is "Computer Check Posting Error"
(SY00500.BCHSTTUS = 15). If we try and open via the Payables Batch Entry we
receive: "You cannot edit the batch or transactions in this batch. Use the
Batch Recovery window to continue processing this batch."
This begins a never ending loop.
Batch ID in question is selected and "Marked" and [Continue] is selected to
process and we receive: "Data entry errors exist in batch <BATCH ID>. Use the
Batch Recovery window to process this batch.
Any suggestions on how to end this loop and resolve the issue?
FYI: We are using Safe Pay and the Safe Pay [Load / Reload Transactions]
brings in 0 checks with $0.00 and the batch in question appears in the Safe
Pay Upload History. We are running MS Dynamics GP Professional 9.00.0259
with SQL Server 2005 - 9.00.2047.00 ODBC Driver.