Announcements
No record found.
Adjust Cost - Item Entries is being run daily at night. However, even for 1 to 2 fast moving items, processing time will reach to 2-3 hours.
*This post is locked for comments
Hi Beverly.
there are a number of possibilities. Can you tell me what version you are using and what costing method you are using?
The adjust costs has got a lot better between versions 3 to 6. If you are using version 3 then upgrading to 6 will help a lot. Average costing, however, is always slow. Standard or FIFO are much faster.
James
Hi James,
We are running on Version 6 R2 and average costing method. If we change to FIFO would it shorten the Adjust Cost -Item Entries processing time?
Thanks.
Beverly
Using FIFO instead of Average will speed up the adjust cost dramatically. However switching to it will involve setting up new items and journaling the stock across (and all other associated transactions - sales orders - BOMs etc.) as there is no option for changing the costing method of an item once it has been used. There may also be a problem in relation to changing your accounting practise.
My only other suggestion is to run the adjust costs process on the job queue using an application server. This way it can be run overnight so while it won't be much faster it will at least be invisible/.
We have 24/7 operation. If we run on job queue using an application server, does this mean it will allow other users to still transact and post transactions?
The big challenge we have right now is that during Adjust Cost run, the users who really need to post are locked out because of Adjust Cost. If there is a way of not locking out the table during Adjust cost, that would be great so that while it is running, users can still transact and post.
Beverly,
The Adjust Cost will always have blocking, which will effect Users, but there are ways to reduce the blocking. The application server is a good idea, and will free up the User that is blocked, it however will NOT reduce blocking as it is the same process, thus other Users will still have the same experience. The first thing you could do is to take a look at the following document you can download from the following blog:
blogs.msdn.com/.../microsoft-dynamics-nav-sql-server-configuration-recommendations.aspx
You will for sure want to implement the REPEATABLEREAD option as outlined in the document. This will reduce the amount of blocking in SQL Server on the outer edges of the Indexes. This will not totally take care of the issue, but should help. The only other way to make this work faster is to optimize the speed of the posting, which will reduce locking/blocking. You can do this in many ways, but the most optimal would be to make sure you have all indexes up to date and statistics up to date. Statistics should be updated nightly and indexes rebuilt/reorganized at least weekly. This is also outlined in the document under a section of Maintenance Jobs. You would also want to optimize Indexes to make sure no additional Scans are being done, you can use DMV's to look at this, and optimize your indexes, and something a partner could help with or Microsoft with Performance Tuning Billable Services we provide, but checking with your partner would be first option. The last thing would be to optimize hardware and disks to optimize for performance as the faster things run, the less locking/blocking you have. Since you are 24x7, you really need to optimize for speed so that things work faster. This is the direction I would take anyway. Hope it helps.
Nick
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
We are thrilled to have these Champions in our Community!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
