I have a batch that is stuck.
We go into Batch Recovery window and select the batch that won't post,
and select the Continue button.
An error appears:
Batch PAYABLES failed to complete posting. Use the Batch Recovery
window to complete the posting process.
(Well we are already in the Batch Recovery window)
click the More Info button and see the additional information:
"A save operation on table 'PM_Transaction_WORK' caused a sharing
error."
We go into each transaction in the batch, and the final line item in
each transaction says WORK, like it is trying to process these
transactions in the batch. However the posting is stuck.
Please assist.
For some reason,posting of the batch was interrupted before all lines
completed posting. That's why you have some records in WORK status.
To resolve -
1. Run the following script against the company database. Replace XXX
with the batch number or the name of the batch that you are trying to
post.
UPDATE SY00500 SET MKDTOPST=0, BCHSTTUS=0 where BACHNUMB='XXX'
Note The value of BACHNUMB is the same as the value of the Batch ID
window in Great Plains.
2. View the contents of the SY00800 table that is located in the
DYNAMICS database to determine the value of the DEX_ROW_ID field for
the batch that you are trying to unmark. You can view the contents of
this table by running the following script.
SELECT * FROM DYNAMICS..SY00800
Note If no results are returned, go to step 5.
3. Run the following delete script that is based on the results that
you received in step 3. Replace XXX with the DEX_ROW_ID value of the
batch that you are trying to unmark.
DELETE DYNAMICS..SY00800 where DEX_ROW_ID= 'XXX'
4. Verify the accuracy of the transactions.
5. Verify that you can edit and post the batches.
Hope this helps,
Frank Hamelly
MCP-GP, MCT, MVP
East Coast Dynamics
www.eastcoast-dynamics.com
blog: www.gp2themax.blogspot.com
Print the payables trial balance with options before and after running
checklinks. Compare both reports to see if the checklinks routine has
modified any balances.
Checklinks looks for inconsistencies among tables. I have used it to fix
similar issues. Try the batch recovery after running checklinks.
I tend to notice little errors like these when checklinks is not run on a
database every month or two.
"Vinny Kelly" <vinn...@gmail.com> wrote in message
news:85e113c0-ce9e-4704...@v35g2000pro.googlegroups.com...
On Mar 23, 7:16 pm, "Frank Hamelly, MCP-GP, MCT, MVP"