Today I was doing some AX 2012 performance R&D to see how big is the contirbution of SQL to AX 2012 performance issues.
From my experience and following Microsoft guidelines, we would strongly recommend not to virtualize your Microsoft SQL server. For larger Microsoft Dynamics AX 2012 installations a Microsoft SQL Server installation on physical hardware is recommended. However, Microsoft supports Microsoft Dynamics AX 2012 installations with virtualized hardware for a number of virtualization solutions.
Take an example, for 10 items shipped in a Transfer Order you have received only 8. You can do the following to close the transfer order.
In the Setup tab, of the transfer order, you can place a % for Under delivery, in order to consider the order as completed.
I was playing around with AX 2012 in one of my labs and I started getting following error.
To be frank with you, I had made couple of KB updates and few cuddling with my system registry for checking some components. But believe me I landed up in a mess and started getting the following error, was clueless on what was leading to this issue.
A strange design change in AX 2012 Client calendar look ups observed.
To give you a brief, until AX 2009,we considered AX client calendar taking the local client system setting. Meaning, if we go to windows >> change the date, time settings and change the first day of the week as monday;my expectation with AX 2009 is, if I do this modification and open my AX client and then go to any of the date field and click Calendar lookup then I should be able to see the calendar for this month starting with day as Monday.
When the encumbrance process is enabled, we can create purchase order encumbrances that are recorded in the general ledger when a purchase order is confirmed.
Encumbered amounts on a purchase order are relieved when a vendor invoice is confirmed to spend all or part of the encumbered amount. Relieved amounts are subtracted from the amount of the purchase order encumbrance.