inventory recalculation slow progress
Belal
When running inventory recalculation in AX2009 SP1 RU3, calculation list
starts with around 6700 items and rapidly decreases till reaching 265 items.
At this moment items calculation list decreases at a rate of 1 or 2 items per
day. I notice that there is very low disk utilization during calculation
while processor is highly utilized. This is the first time I run inventory
close and calculation after upgrading from AX4-SP2, and we have not faced
this problem before in AX4-SP2.
I am asking if this is normal in AX2009? is it expected that recalculation
enters endless loop?
Regards,
Belal
Belal
than 10 days and still 270 items in calculation list with decrease rate of 1
item per two days. To avoid this I have two work arounds:
1 - change session date to 1/2/2010 and run inventory close with
recalculation till 31/1/2010. Then set session date to 1/3/2010 and run
inventory recalculation till 28/2/2010 and so on. This way closing consume
1.5 hours and recalculation consumes 25 minutes.
2 - Run inventory close routine without recalculation for each month
individually. This way closing consumed 3 hours.
I am asking which method is more recommended? Should they give the same
results for items cost? Why closing takes much time in the second procedure?
Regards,
Belal
George Burrell
Build 5.0.1500.2116, AX 2009 SP1 Hotfix Rollup 4 (RU4)
During Recalculation I thought the process had stalled. I did Calculate Button > Pause, and Calculate Button > Restart and then I could once again see part numbers being calculated.
However when it came time to build GL Journal, the system hung again. I interrupted the program which crashed Ax. I cancelled this Recalculation (even though all the FIFO matching was complete) and performed a CLOSE successfully. It ran very well.
QUESTION - is the Recalculation process far more fragile than CLOSE? Has anything been done to fix Recalculation?
George Burrell
Build 5.0.1500.2116, AX 2009 SP1 Hotfix Rollup 4 (RU4)
During Recalculation I thought the process had stalled. I did Calculate Button > Pause, and Calculate Button > Restart and then I could once again see part numbers being calculated.
However when it came time to build GL Journal, the system hung again. I interrupted the program which crashed Ax. I cancelled this Recalculation (even though all the FIFO matching was complete) and performed a CLOSE successfully. It ran very well.
QUESTION - is the Recalculation process far more fragile than CLOSE? Has anything been done to fix Recalculation?
> On Tuesday, March 30, 2010 5:36 AM Belal wrote:
>> On Tuesday, April 06, 2010 8:39 AM Belal wrote:
>> In my case, inventory recalculation of 3 months of transactions consumes more
>> than 10 days and still 270 items in calculation list with decrease rate of 1
>> item per two days. To avoid this I have two work arounds:
>>
>> 1 - change session date to 1/2/2010 and run inventory close with
>> recalculation till 31/1/2010. Then set session date to 1/3/2010 and run
>> inventory recalculation till 28/2/2010 and so on. This way closing consume
>> 1.5 hours and recalculation consumes 25 minutes.
>>
>> 2 - Run inventory close routine without recalculation for each month
>> individually. This way closing consumed 3 hours.
>>
>> I am asking which method is more recommended? Should they give the same
>> results for items cost? Why closing takes much time in the second procedure?
>>
>> Regards,
>>
>> Belal
>>
>> "Belal" wrote:
George Burrell
Build 5.0.1500.2116, AX 2009 SP1 Hotfix Rollup 4 (RU4)
During Recalculation I thought the process had stalled. I did Calculate Button > Pause, and Calculate Button > Restart and then I could once again see part numbers being calculated.
However when it came time to build GL Journal, the system hung again. I interrupted the program which crashed Ax. I cancelled this Recalculation (even though all the FIFO matching was complete) and performed a CLOSE successfully. It ran very well.
QUESTION - is the Recalculation process far more fragile than CLOSE? Has anything been done to fix Recalculation?
> On Tuesday, March 30, 2010 5:36 AM Belal wrote:
>> On Tuesday, April 06, 2010 8:39 AM Belal wrote:
>> In my case, inventory recalculation of 3 months of transactions consumes more
>> than 10 days and still 270 items in calculation list with decrease rate of 1
>> item per two days. To avoid this I have two work arounds:
>>
>> 1 - change session date to 1/2/2010 and run inventory close with
>> recalculation till 31/1/2010. Then set session date to 1/3/2010 and run
>> inventory recalculation till 28/2/2010 and so on. This way closing consume
>> 1.5 hours and recalculation consumes 25 minutes.
>>
>> 2 - Run inventory close routine without recalculation for each month
>> individually. This way closing consumed 3 hours.
>>
>> I am asking which method is more recommended? Should they give the same
>> results for items cost? Why closing takes much time in the second procedure?
>>
>> Regards,
>>
>> Belal
>>
>> "Belal" wrote:
>>> On Thursday, March 31, 2011 8:29 PM George Burrell wrote:
>>> This problem seems to have happened with me also, in AX2009,
>>>
>>>
>>>
>>> Build 5.0.1500.2116, AX 2009 SP1 Hotfix Rollup 4 (RU4)
>>>
>>>
>>>
>>> During Recalculation I thought the process had stalled. I did Calculate Button > Pause, and Calculate Button > Restart and then I could once again see part numbers being calculated.
>>>
>>>
>>>
>>> However when it came time to build GL Journal, the system hung again. I interrupted the program which crashed Ax. I cancelled this Recalculation (even though all the FIFO matching was complete) and performed a CLOSE successfully. It ran very well.
>>>
>>>
>>>
>>> QUESTION - is the Recalculation process far more fragile than CLOSE? Has anything been done to fix Recalculation?