A client has been struggling with this issue for some time. They use Sales Order Processing (SOP) in GP and they also use the Master Number feature to tie quotes, orders and invoices.
GP has a dark side with this where it does not honor the next master number sequence. This is a very difficult problem to pin down as it does not correlate to any noticeable user task. But the master number will suddenly reset itself at random times. This can cause crossed master numbers in the SOP file causing unrelated documents to link together.
Turns out this is a known problem. There is something wrong with the way GP doles out numbers. This is something I've observed happen with Purchase Orders also. In fact there is a tool available for setting the next PO number. But nothing for the SOP master number.
What is available is an updated script from Microsoft that adds code to the SOPGetMasterNumber stored procedure to keep the next master number in SOP Setup from dropping below the next highest number in the master number table.
I've installed this script at this client and will report back if any problems arise or continue.
As an interesting side-note this problem has existed since I've been visiting this client in 2009 with GP 9. They are now on GP 2010 and I've looked at that stored proc in GP 2013 and it's exactly the same as GP 2010. Apparently if the problem is fixed in GP 2013 they fixed it via some means other than this stored proc. We shall see.
Update 8/27/2014:
Since applying this update we have had exactly ONE incident report where the SOP next master number dropped below the actual next number. This is proof positive of the solution found IMHO. Normally we'd receive several notices per week.
In addition we've had no reported duplicate master numbers since. Again normally those would happen at least a couple times a month. So far so good!
No comments:
Post a Comment