Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover 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 TimelineWatch the 2020 Release Wave 1 virtual launch event
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
I wanted to see if anyone has experienced this same issue.
Currently we are running into an issue in AX 2012 R3 (we are on the latest CU as well) in which committed cost against project budgets do not relieve when the invoice post.
within our current workflow we use the auto-post function after the last approval step.
I have tested this issue by removing the auto-post step in the workflow and then tested posting manually (with the button on the form) after the workflow is completed and this method works as intended (the committed cost clears).
so it seems the root of the problem stems from the job behind the auto-post task. We have done some debugging with no resolve as of yet. I thought I would run this by you all and see if anyone would happen to have a recommendation for a proposed solution that you could share?
Also, I did a brief issue search on LCS and did not find an exact match to our issue as of yet there.
please let me know your thoughts or if you need any additional info thanks l!
Did this automatic action work before correctly? Did it stop after an update to the latest CU or was anything else changed? If you don't have customizations in this area, I would suggest to create a ticket for Microsoft Support as you already searched on LCS. I don't have a machine with a setup ready to verify the behavior.
In the meantime, don't enable the auto post function.
I would recommend that you start investigating LCS for potential hotfixes especially if you operate an older R3 version.
There have been a couple of hotfixes releases for issues around committed costs and you might have simply run into an older system bug.
So, please check LCS for available fixes.
Thanks for the question. I assume this is a Project Purchase order ? Is this a product based purchase or a procurement based purchase ? Do you have the create Item requirement parameter on for Project purchase orders in the Project management and accounting parameters ? Are the commitments associated with the Purchase order or the Item Requirement? (You can verify this by looking into the commitments on the Purchase order)
Invoicing should relive the commitments and post the actual costs. There are more than one fix that we have released to address this scenario. Based on the answers to the questions above we can narrow down to the right fix. On a side note if it is possible I would recommend upgrading to the latest CU as there are many fixes which we released to address this scenario. If you are on the latest update and still can simulate this scenario then please log it as a incident.
Thanks for the response. This is a project purchase order. It is procurement based. The commitments are against the project categories that are budgeted on the project.
We are on the most recent CU for 2012 R3.
As a mentioned, this is only happening when we use the auto-post function through the workflow. If I turn off the auto-post function and then post manually after the workflow has completed, the committed cost alleviate as they should.
Good Morning James.self,
Have you been able to make some progress here?
Would be great if you could keep us updated and know if some additional help/support from the community is required.
Many thanks and best regards,
Thanks for the update.
You can log this as a incident with Microsoft for addressing this through a hotfix.
Business Applications communities