I have a case where the storage dimension group was set wrong and needs to be changed (physical inventory checkbox was unmarked so on hand view is not consistent). Now I know to solve this, all I need to do is close all open transactions, count out the on hand and do the inventory closing.
The Customer said that this solution would not comply as he will have invoices open for the current period of the closing, and the next ones, and there is no way he will be able to post invoices or close production orders prior to their time. Is there a way to overcome this issue? Knowing that changing the Storage dimension group is a must.
Another workaround which would probably not accepted is creating new items with the correct settings.
The customer might look for a solution where the setting would be changed without validations (e.g. directly in the database). This might work depending on all settings and existing transactions if you review all scenarios carefully. Test it in a separate environment first. This is not recommended by Microsoft; also not by me. Let the customer be responsible for accepting the test.
Thanks for your reply. I closed with them any possible changing from SQL or directly on the database. They know I am not going to even look at this solution.
New items is on the table also, and the Finance team there would fancy this option than the dimension change through inventory closing and zero qty.
However, if I am correct they would still need to close all open transactions for the current items if they want to have correct numbers when they create the new items. Business wise that is.
Everything comes with a price... Indeed using new items, it would be nasty as there would be many open orders. They are claiming the "old" items then. How to deal with the period where you would have new and old item numbers for the same product... That would require some special procedures at the customer.
True, and that is what I am telling them. Anyways I have a meeting with them next week and they will have all options on the table. Let's see what they will decide.
For me after testing I believe the best option for us and them is to do a period closing, post all open transactions and change the dimension. But it's their decision after all
I've never tested this hard method in Ax 2012 and neither when there is a lot of transactions but I might give you some ideas.
In my situation it helped me and was useful, it was just after go live and we had the same issue as you have. Check my post :
But handle this with a lot of care it is not adviced and looks like the hard way. I wouldn't doing that myself before doing a lot of tests.
Great Work. I read it thoroughly and admiring the way. Unfortunately I tested it and would not let me clear the storage dimension group. Here is the error.
Looks like I am going to go for the hard option :(
Business Applications communities