We are doing a test upgrade of Dynamics GP from version 10 to version 2013. Everything seemed to be going just fine but when we tried to fulfill an order the system seemed to lock up. As it turned out I don't think it locked up it is just that it is going through the entire IV00200 table looking for serial numbers. I ran a SQL and script log on both our version 10 and version 2013. While there are subtle differences between the two logs that seem to relate to security, the thing I noticed that I believe is causing the problem is a call to the one of the stored procedures on the IV00200 table. In version 10 there are parameters included in the call but in version 2013 the parameters are all null:
2013 SQL Log Entry
/* Date: 08/12/2013 Time: 10:55:54 stmt(159119392):*/ {CALL SSL.dbo.zDP_IV00200F_2(NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL)}
10 SLQ Log Entry
/* Date: 08/12/2013 Time: 11:47:25 stmt(21057512):*/ {CALL SSL.dbo.zDP_IV00200F_2('WG810001','SEATTLE',0,1,'1900.01.01',-99999999999999.99999,'WG810001','SEATTLE',0,1,'9999.12.31',99999999999999.99999)}
We do have a custom dictionary that interacts with the SOP and fulfillment process but I have removed it from the set file and still get the same behavior.
Has anyone else seen any such behavior and if so were you able to identify the issue and correct it?
Thanks!
Lonnie Nelson
*This post is locked for comments