Commit should be always at the end of process because if anything goes wrong in between then it will rollback the entire process. I suggest just look at the performance parameter rather than changing the standard functionality. It may lead to unwanted result and can make you system vulnerable.
Probably I’m not so skilled about the Costing Method, but reading the MS white paper there is no link beetween each period.
This make reasonable in my opinion commit after the calculation of each single step. (dividi et impera) (doing that also the performace might increase)
what do you think ? does exist somebody that already did it or rather check the feasability ?
There is more than one solution here. Your main problem is that you are running out of time - so you want to split it up and let it run for a number of days.
You have to options without to much programming.
First option is to do the adjusting pr. period - with 14 periods you have to run the report 15 times (the 15th a full adjustment - just to be sure). Peik has written a example of doing correctly depending on the posting dates - take a peek at Http://mibuso.com/blogs/peik
I have myself done another solution:
I have created a Pre-preport that filters on one Item and then calling the Inventory Adjustment - with a commit between every item. You could also add a new field to a table so you know how far you have gotten when you stop the report ( perhaps CTRL+C the report in the morning.) The Pre-runner could also be programmed to stop at eg. 07.00 AM.
When all Items have been Adjusted - then go back a run the adjust-report the “normal way”
