Sometimes, a user will click the red X in the top right corner of the Dynamics GP window while still having other windows open. Make sure that you first close out of all windows, saving any documents you have open, then click the Microsoft Dynamics GP button, and choose Exit. After the batch is recovered, go into the area page related to the batch, select the appropriate batches option, which will depend on the origin of the batch, and select the batch.
Then click the Print button to print a Batch Edit List. Look for error messages within the Edit List, which will indicate what needs to be done to correct the batch. Next, open the transaction s with the error, make the necessary corrections, and you should be able to post the batch. There are times when the batch will continue to be stuck in Batch Recovery. In this post, I am going to highlight a great tool in Microsoft Dynamics GP that can help you make it through your day. As you can see, in my example, there is only one batch that has a problem if there were multiple batches, they would all show up here.
Next, take a look at the Status field — Dynamics GP is telling you that there are transactions errors and an edit is required to fix the batch. From this screen, you can hit the Mark All button and then hit Continue. From here, the simplest way to identify the issue with this batch is to print an Edit Report — I can do this by clicking on File in the top left hand corner of the window — then Print, to open the Report Destination window.
Leave the Report Type as Standard, check off the Screen box and uncheck the printer box. This will print the edit report to the screen for you.
If this truly was intended to be an intercompany transaction, they would need to first register the IC module, and then manually correct the Journal Entries.
This step is extremely important to ensure data integrity. For the above ii if the batch is returned to the unposted state, running an edit list will reveal what the error was, some of the typical edit list error messages include:.
The error messages are typically located near the top with details within the report itself for the transaction. They are quite descriptive and will point you in the right direction to isolate the issue. This next error will require SQL database access. Our recommendation is to always back up the database before proceeding and testing the scripts in a refreshed test company.
Our technical experts at Encore can assist in recovering the backed-up data if an error occurs. Once the batch status has been set back to available 0 , please continue to print the edit list to review the transaction. Opening Sales Transaction Entry window — your previous transaction — level posting session has not finished processing.
The first step if the above three scripts provides results would be to delete them. Please back up the database or table before proceeding. If the above three scripts are used, always back up and verify on an updated test database before removing records. Join us to learn how to create a report, discuss the options available to save reports, how to use preset dates, and how to best use your GP reports. January 18 am — am PST.
0コメント