![]() |
All Purchasing Transactions list error - Purchasing Navigation List |
Upon further review, the issue is due to bad data in the Vendor ID (VENDORID) column in the Purchasing Receipt History table (POP30300). In summary, if you have a purchasing receipt with a blank vendor ID or a vendor ID that does not exist in the Vendor Master table (PM00200), it will cause the Items list to fail with the error above.
The following query should help in identifying the offending record(s):
' Created by Mariano Gomez, MVP ' This code is licensed under the Creative Commons ' Attribution-NonCommercial-ShareAlike 2.5 Generic license. SELECT * FROM POP30300 WHERE VENDORID NOT IN (SELECT VENDORID FROM PM00200);
Once you have identified the record(s) causing the failure, you can use the Vendor Maintenance window to add the missing vendor or further study the issue to remove the offending receipts if necessary:
![]() |
Vendor Maintenance window |

GP2010 Purchasing List Error - Partner Online Technical Community forum
Until next post!
MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/
4 comments:
Thank you very much for your post. We've been searching and asking in the Dynamics GP Community for months and here it is. However, we didn't get the error until we upgrade from GP2010 SP1 to GP2010 SP2 aka R2.
Based on your post we figured that the problem is the In-Transit Inventory transaction, in the Receiving Transaction entry window, does not allow VendorID to enter.
Hope Microsoft will remove that check in SP2 as they did in GP2010 RTM and SP1.
Thank you for your post, it is very helpful as usual. I am using Dynamics GP 2010 and having this same issue. After I ran your query, there are few records show up with BLANK vendor ID, every other columns are either just zero or NULL values. It seems like they are some corrupted records, so I removed them. But now, when I go to Purchasing->Navigation List-> All purchasing transactions, it gave me a different error message "Violation of PRIMARY KEY constraint 'PK##1133951'. Can not insert duplicate key in object 'dbo.##1133951'".
It seems some duplicate records are still existing when it is trying to insert into the temp table.
Any help would be appreciated!
Haitao,
Thanks for the kind words.
The only suggestion I have is to run a SQL Server Profiler trace or a DEXSQL.LOG to see which record is causing the problem.
MG.-
Excellent! works for me, great job! thanks!
Post a Comment