Great Plains Payables Computer Check Batch Recovery Notes From The Field

It is not really difficult to do it when your system is on Microsoft SQL Server and

Dynamics GP has one of the recent versions with Batch Recovery functionality. We would like to describe how to do the job if you have old Dynamics on Pervasive SQL Server 2000 and its version is 7.5, 6.0 or older. Also if you are technical consultant you can use Pervasive SQL Driver with DDF file to create ODBC connection to Btrieve files. However if you are not too technical the method described below should help and it doesnt require ODBC connection as we are deleting physical files:

1.Symptoms. You edited checks and tried to print them. Something happened and checks printing failed and now when you are opening Computer Checks batch in Payables Management module you see the status Check Processing

2.What need to be done. There are two tables SY00500 Posting Definition Master in Company folder and SY00800 Batch Activity in System folder. We need to repair batch records in these tables but we would use more straightforward method simply deleting or renaming these tables

3.Ask all the users to log off Great Plains and look at the Master Posting form. Here write down all the Batches currently existing in the system with their origin and frequency if they are recurring we will need to recreate these batches after the fix. Find your Dynamics folder on the server and in System subfolder rename SY00800.btr file. Now open Company subfolder (it is typically named by company abbreviation) and here subfolder named Company and rename file SY00500.btr

4.Recreate AP Computer Check batch by opening AP Batches and entering its name and description in this form plus select origin Computer Checks. Please note that batch name should be exactly the same as the one failed to print checks

5.Open Post Checks form in Payables Management module, select the option to Print Checks and go ahead with printing and processing checks. At this point you should feel relieve that problem is gone and you can send printed checks to happy suppliers. But this is not all as we still have to recreate batches that were deleted together with the table SY00500

6.Recreating deleted batches. Do this procedure in each respected module. Please pay attention to the fact that some batches could be recurring and you have to specify the frequency

7.Additional notes. Here we are referencing older versions of Great Plains Dynamics 7.5, 7.0, 6.0, 5.5, 5.0, 4.0 on Btrieve or later on Pervasive SQL 2000 database platforms

8.If you are on SQL Server DB platform. In this case there is no need to delete the whole table. Simply remove batch record in SY00800 which is hosted in Dynamics database and update BCHSTTUS and MKDTOPST fields from non-zero back to zero. In some complex cases there are additional tables in temp database and here we recommend you to find article in Microsoft Dynamics Customer or Partner Source

9.For additional information, please feel free to call us 1-866-528-0577 or 1-630-961-5918 (this number works for international customers) or email us help@albaspectrum.com We serve you USA/Canada nationwide via remote support (web sessions and phone/Skype conferences). Local service is available in Western Michigan, Chicagoland, Southern California (LA, Orange County, San Diego), Houston area of the state of Texas

by: Andrew Karasev

POST COMMENT

Recovery Time Of Stiffness After Full Knee Replacement Helpful Hints On How To Protect Your Data Data Analysis Solutions India Data Entry: What Is It? Information Management Of Database Server Perfect Tool To Repair Ost Database To Be Chosen To Recover Imperfect Corruption 3 Things You Should Know About Breast Augmentation Recovery How Mobile Coupons Can Pay For A Smartphone Data Plan How The Table Recovery Sql Server 2005 Is Possible? Ms Sql Database Recovery Tool To Alleviate Your Pains Spring Up Due To Corruption Looking For A Safe Data Recovery Program? Why Data Recovery From Your Defective Laptop Is Substantial? Version Control Is Necessary Of Application Source Code In High Availability Database Servers