Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012
Upgrading to Microsoft Dynamics AX 2012
Data Import, Export, and Migration
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
SSRS and SSAS Integration
I have an item with stock 25 On Hand quantity, but when I post the invoice the system threw an error "1.00 cannot be picked because only -100.00 is/are available from the inventory." Stock -100 calculated from Purchase order less Sales order, quantity adjusted from Movement journal is not calculated on it. And one more thing I have to mention that according to me this error occurred after inventory closing recalculation process. I had tested it on my test machine. Would have any solution to resolve this issue? Thanks in advance!
I'll simulate your scenario here, but if the inventory transaction happened within the same time frame your inventory closing were executed, then you're gonna have some issues, because when you run inventory closing, Dynamics Ax closes the selected period for any transaction.
Plus, is it PO or SO? Is it Batch controlled? You may have 25 on hand on your entire warehouse, but if it is batch controlled, you need to have the whole amount (considering you've already posted the picking list) on the same batch as you are trying to post.
Error occurred during sales order posting, we do not configure the batch dimension. Furthermore, find the transaction of an item below.
Weighted average inventory closing
Kindly paste the transaction into excel to check the error.
Run again inventory closing recalculation process, may be your Item number was block. If you cant run again this process you'll have to research by code.
I had run again inventory closing process including recalculation, but the problem is still exist.
I checked your inventory transactions by copy and paste into excel. You are using as inventory dimensions at least site, warehouse and serial numbers. The inventory is separated for serial numbers per dimension number (inventdimid). The current stock seems to be 139 items. When I counted the purchased and sold transactions for the dimension number that is used on the open sales transaction you have a current stock on this dimension number of -63.
You have to check the used site, warehouse and serial number values on all transactions to see which values were used. These values are not visible in the table you attached in this thread. When you know these values, you might use an inventory journal for having some corrections.
André Arnaud de Calavon
All the site and serial number were same, there were a few transfer transactions of warehouse(wh1010 to wh1020 / wh1020 to wh1010 etc.). The effect of these transfers was null. Therefore, all the transactions values were same except warehouse. Hope you got my point.
Look at your table in another view:
As the Dimension No is a unique combination of your inventory dimensions, a difference should be in site, warehouse, serial number or another dimension.
So AX thinks there is a difference and you don't have sufficient inventory...
Please check if all transfers are posted correctly. I can't see which dimension no is what combination of dimensions.
Hi Mr. Andre,
As you said that the combination of inventory dimensions should be difference in site, warehouse and serial number respectively, which is clearly shown in the given figure. But the highlighted entries has same combination whereas the dimension number is not unique. I am asking this to our consultants that why this happened? Your calculation was absolutely perfect, you got the right point that according to dimension item don't have sufficient inventory. But how can AX ignore the dimension number when posting the sales order?
use rich text formatting to view the table
AX cannot ignore the dimension no. on postings. This could be caused by manual changes in this table. I saw this once when we had to add the batch number in an implementation where we first did not have this dimension. All records in InventDim table were converted, but one user did not wait for the release of the conversion and created already some transactions. In that time after conversion we had "double" records as well. We corrected it with an script to change all related transactions and purchase lines to have only one dimension number.
Sounds easy, but we did some testing in another environment to be sure nothing else could go wrong.
In your case you have to be careful as well with the inventory closing. If you have used it for this item, check the related postings if this was correct.
Thanks for your consideration regarding this matter. I have discussed it with our consultant and they will be find some solution soon. If I need your more assistance I will contact you again. Thanks a lot!
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics