Now Available in Community - New TechTalk Videos for 2020
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We have an issue with purchase requisitions and POs since the start of 2020.
If a purchase requisition has a 2019 accounting date at the point it converts to a PO we get the error
"Purchase requisition line was pre-encumbered in a fiscal year that is different from the accounting date of the purchase order. Hence, the purchase order cannot be created"
And if we try to match a PO with a 2019 accounting date to an invoice in 2020 we get the error
"Stopped (error): Posting of order PO009184 cancelled The accounting date for the invoice must be in the same accounting year as the related purchased order. Run the purchase order year-end process or change the date to the current accounting year."
The problem is we can't run the PO year end process
"This process cannot be run because neither budget control for purchase orders nor the encumbrance process are enabled."
So we seem to be in an infinite loop and are having to ask people to recreate PRs and POs which is doing wonders for the popularity of the system (sorry for the unnecessary sarcasm better out than in)
try to check year end parameters in GL parameters and also run a process 'Purchase order year-end process'
We can’t run the PO year end process as we don’t have budgets or encumberants enables. See the original post for the error we get if we try to run the PO year end process.
Our developer traced the error message through and it was being caused by parameters under cost control being switched on. Make sure these two are off if you hit this issue!
Business Applications communities