This article has been archived. It is offered "as is" and will no longer be updated.
This article applies to Microsoft Dynamics AX 4.0 for all regions.
Consider the following scenario in Microsoft Dynamics AX 4.0:
You mark a sales order and a purchase order.
All the inventory dimensions are the same.
You post an invoice for the purchase order. And, you post an invoice for the sales order.
You run an "inventory close" procedure for the period that covers both the purchase order and the sales order.
Then, you post a negative "deliver now" quantity to reverse this marked transaction in a non-closed period.
In this scenario, you receive the following error message:
Quantity must not be empty.
A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics AX service pack or the next Microsoft Dynamics AX version that contains this hotfix.
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Before you install this hotfix, verify that the Microsoft Dynamics AX client users are logged off the system. You should be the only client user who is logged on when you implement this hotfix.
To implement this hotfix, you must have a developer license.
Note We recommend that the user account in the Windows Logins window or in the Database Logins window be a member of the Administrators User group in Microsoft Dynamics AX.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To install this hotfix, change the code in the updateReserveRefTransId method of the \Classes\InventUpd_Reservation object as follows.
if (qty != 0) // Add this line to prevent the re-reservation for closed marked transactions. mapReceipt.insert([inventTrans.InventRefTransId,receipt.InventDimId,receipt.StatusReceipt],qty);
You must have Service Pack 1 for Microsoft Dynamics AX 4.0 installed to apply this hotfix.
After you have installed the hotfix, you must exit the Microsoft Dynamics AX client program. For the code changes to take affect, you must restart all Microsoft Dynamics AX Application Object Servers (AOS). You do not have to restart Microsoft Windows.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.