Hello to all,
I've this scenario.
Nav 5.0 SP1
Item with Variant with million of ILE
Costing MEthod Average, period = Month
I've already a smarter version that COMMIT after each item has been calculated.
As a next step i was thinking to COMMIT after the calculation of each period.
(I need that cause I've some ILE backposted and I need to calculate since 14 period ago costing ~50hours)
Is something feasable that someone has already done ?
If yes who can address me to the right direction.
Thank you to all,
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" :-)
Palle Arentoft,Dynamics NAV Specialist
- One have to fully understand the question in order to give the right answer. So always try to be as precise as possible when asking for help!
You can close the Inventory period for which adjustment is already done.
Why you want to change in default program?
Don't forget to the post(s) that solved your problem
Probably I haven't exposed my issue very well.
I've "Avg. Cost Adjmt. Entry Point" with 14 period open to be calculated for a specific item with variant.
Calculate a period (in my case Month) can cost about 6/7 hours and the standard report R795 commit only at the end.
My native idea was to commit after the calculation Avg calculation of each period.
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 ?
I would rather check on performance by doing some database tuning and optimization rather than changing the default functionality /programs.
Just think twice before changing the process.
I found your reply very interesting and inspiring (in fact I've just coded an ACIE modules that commit after each period :)
what is the modification u have done to commit after each period, i am facing the same issue. some items are taken more than 2 days to complete.
please give me code.
I found your reply is very instresting. could u please tell me how to solve this issue at my database. bcz i am facing the same issue.
© 1995-2013 Dynamics User Group, all rights reserved.