There are few parameters that impact counting in MSDyn365FO. We all know about “Lock items during count” parameter that locks the item for any inventory update (Registration, Product receipt posting, Picking, Packing slip posting, etc.) if you have an open counting journal with it.
Another setup that you should know about is Warehouse items. It gives the ability to define different counting groups for different warehouses, setup default receipt/issue or picking location for an item in a particular warehouse and review counting status (i.e. whether item is being counted and in what journal it’s included). Therefore, if you have multiple warehouses and want to count the stock on each warehouse separately you should setup Warehouse items per each warehouse you have.
However, we still have limitations here. Setting up warehouse items per warehouse gives the ability to add same item to different counting journal with different warehouse, but you cannot do it per location.
The simple scenario that you can think of, is when several people do a stocktake and everyone counts different locations. In this case, if the same item has stock in multiple locations and we have an open counting journal for this item we will get next warning: “Item XXX is locked for updates in warehouse YYY because it is being counted.” when we try to add it to another counting journal.
Of course, you can build the process to have only one journal for all items that are being counted and then someone will go and update it with actual values. But what we really want, is to have a counting journal for every worker, so the user can work only with lines he needs.
In previous versions it was not possible, but now we have “Counting status registration policy” field on the counting journal name and header. The field has two options: Enable counting status registration and Disable counting status registration.
When it’s set to “Disable…” we are able to add same item into multiple counting journals (which solves the issue), at the same time “Enable…” keeps original validation described above.
Good to see that we have options now and more flexibility even in this pretty straight forward process.
For those of you who cannot find it in your AX 2012 environment, you can get this feature by installing KB4057006.