Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Mangala S]

?Hi There,

While entering a Payable transaction, I get this error “Unable to generate a Voucher number.” when I tried to close the window I get this error “unhandled database exception: A get/change operation on table ‘pm_key_mstr couldn’t not find a record.”

We took a backup of the database and I ran Check Links for Purchasing Series, all tables. No errors existed.

The Payables setup option is setup as below;

Please help. Thanks, Mangala

——————————
Mangala Shetty
Saint Elizabeth
Markham AB
——————————

[Jo deRuiter]

?Good Morning ?

Generally, this is caused by two or more users (can be caused by integrations) that try to reserve the next voucher number at the same time which causes the voucher number to not be able advance chronologically. 

The fix for this is to go into the Payables Setup Options (in your screenshot below) and just manually advance the next voucher number.

In your case I’d probably set it to 020000000  or something (you probably don’t have to go that far up).

If this does not resolve the issue, please let me know.

Thanks!

——————————
Regards,

Jo deRuiter
“That GP Red Head”
Senior Financial Systems Consultant
Heartland Business Systems, LLC
Little Chute WI
920-687-4797 (Work)
770-906-4504 (Cell)
——————————
——————————————-

[Bert Green]

I agree with Jo’s response. We do have this happen occasionally. I usually try to go in increments of 5000.

To be able to close the transaction screen I usually just enter an A into the voucher number field and then say to not save the transaction when closing the window.

——————————
Bert Green
GP Developer/GP Administrator
Berger Transfer & Storage, Inc.
Saint Paul MN
GP2015/MR CU11
GPUG All Star 2017
——————————
——————————————-

[Windi Epperson]

You could also use SmartList to see what the last voucher was an increment accordingly.  That way you don’t end up with a gap in voucher numbers since some auditors look at that.  Best to do this when everyone is out of that company so you know you get a true last voucher #.
Thanks
Windi?

——————————
Windi Epperson
President/GP Senior Consultant
Advanced Integrators, Inc.
Norman OK
405-946-1774 Ext 102
——————————
——————————————-

[Steve Plitzner]

You could legitimately have issues with the payables key file/table and you may need to do a web search for ‘Dynamics GP recreate/rebuild PM keys’ and follow up on those hits.  I wouldn’t necessarily start with that though…but you have already tried a few other things.

Has your company been using Dynamics GP for a long time?  If you are getting the error as soon as you open the Payables Transaction Entry window then it could be that the next default voucher number in sequence (based on your Payables Management Setup) is conflicting with an existing transaction’s voucher number that already exists in the Payables Work/Open/History tables.  I have seen this a few times where there are gaps in the numbering sequence or someone somehow changes or adjusts the default voucher number sequence that causes a duplicate number conflict or loopback issue.

You could verify the voucher numbers that exist versus what is in your Payables setup and if there is a conflict then you need to advance the next voucher number ahead to avoid conflict.   Keep in mind though that SQL database sorts and finds values moving left to right so ‘00000104866’ would get sorted differently (before) 00324, even though 324 is less than 104866.  

Check these tables in SQL for voucher number overlap – the most recently used voucher numbers will appear at top but pay attention to the leading zeros and the record sorting I mention above.  If there is a number conflict it could appear in any one of these tables but most likely would be in the PM30200.

select * from pm10000 order by vchrnmbr desc

select * from pm20000 order by vchrnmbr desc

select * from pm30200 order by vchrnmbr desc

——————————
Steve Plitzner
Imagineering, LLC
Eau Claire WI
——————————
——————————————-

[Bruce Strom]

If something like this happens where a puzzling database error happens once in a blue moon, first you should log out of Great Plains and log back in to get a fresh database connection.  If something happens once I just would not worry about it.

These sorts of errors can be caused by third party applications that do not use the Great Plains dexterity functions to grab the next voucher number/AJE number/etc.  In general programmers should avoid simply grabbing the next number and advancing it in their code, infrequently they will encounter these type of situations.

What is puzzling is that your screen shot shows you are using vanilla Great Plains, so I cannot really tell if a simultaneous third party function is also trying to grab the next number.

——————————
Bruce Strom
Programmer Analyst
Associated Grocers of Florida
sunrise FL
——————————
——————————————-

[Mangala S]

?Thanks a ton!! Thanks Jo! Resolved this issue.

This is what I did. I advanced the Next Voucher number to the next 500 and ran check links again and it worked!!

Thanks all! 🙂

Best Regards,
Mangala

——————————
Mangala Shetty
Saint Elizabeth
Markham AB
——————————
——————————————-