The receipt with this number already exist in the system. Some user might have played with the number series of the receipt. On the purchase header there is a field "Receiving No.". Delete it manually.
We have removed the value in the Receiving No. field on the Purchase Header. User has successfully posted the Purchase Receipt.
You have mentioned that some users might have played with the number series of the receipt. But how?
In fact, the No Series specified for the Purchase Receipt was over. What they did was to modify the Ending No. for the Purchase Receipt No Series Code. Do you think that this might have caused this?
Do you think that this problem can occur again? How can we avoid this in the future?
Hi,
I think No. series of the purchase header should be checked as only default. U face that problem due to checking of no. series as manual. if u remove the check from manual and place the check on default u will solve the problem. bye.
During posting, a COMMIT process was ran. So it created the purchase receipt header, but the error rolled back to the commit. This is why you're getting an error.
Check your customizations to do error checking on fields before the COMMIT is ran.
Comments
http://ssdynamics.co.in
Thanks for replying.
We have removed the value in the Receiving No. field on the Purchase Header. User has successfully posted the Purchase Receipt.
You have mentioned that some users might have played with the number series of the receipt. But how?
In fact, the No Series specified for the Purchase Receipt was over. What they did was to modify the Ending No. for the Purchase Receipt No Series Code. Do you think that this might have caused this?
Do you think that this problem can occur again? How can we avoid this in the future?
Thanks and Regards,
Beatrice.
I think No. series of the purchase header should be checked as only default. U face that problem due to checking of no. series as manual. if u remove the check from manual and place the check on default u will solve the problem. bye.
Regards
Paul
Dynamics Nav Functional Consultant
Check your customizations to do error checking on fields before the COMMIT is ran.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
My question might sound stupid but can you please explain how to do this?
Thanks and Regards,
Beatrice.
If you don't have a developer's license, it's best to ask your solution center to come in and take a look at it for you...
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book