Dynamics GP uses OPEN, WORK and HISTORY tables to process transactions. As transactions move between the tables, interruptions (much like those that cause stuck batches) can cause duplicate data to be left in one of the tables. These scripts identify the duplicate transactions if you have any. Once you know which documents have duplicate entries, you can dig deeper into the tables to find out which record is the correct one.
- N.B. Duplicates often have missing data in the columns or are missing their corresponding line entries.
This script can help with the following error code: "The stored procedure createSQLTmpTable returned the following results: DBMS: 2627, Microsoft Dynamics GP: 0."
Benefits of using SQL Scripts
Dynamics GP is a great system full of lots of features, but every now and then we need to turn to SQL to help us. So we have gathered some of the most useful SQL scripts from our partners, and the GP community, for your use.
Supported Systems | |
ERP Software | Microsoft Dynamics GP |
Sending outdated and boring documents to clients is not going to make a good first impression. You're probably tired of the dreary default reports from Sage X3. Well, with our set of reports we have r...
$200.00
$200.00
If you're using Sage X3 PU9 to generate bank files, you've probably run into this little issue. When generating bank files, you can only save them to a Sage volume, which may not be the easiest place ...
$30.00
$30.00
Sometimes when testing a new GP system, you need to assign items to vendors, and want to avoid having to do so on an individual basis. This script allows you to do just that. Add all items to all vend...
Free
Free
Are you fed up of always being asked how to print posting documents in Dynamics GP? This script will allow you to set one method for all reports. As is, it sets all reports t print to screen but you c...
Free
Free