on 2009 May 26 11:22 AM
When we are displaying any asset through AS03 system shows message " value of Ordinary deprec. have changed in dep. area 01 in fiscal year 2009 for all the assets.
If we click on the message system shows following diagnosis
Values for Ordinary deprec. have changed in dep. area 01 in fiscal year 2009Message no. AU390
Diagnosis
Depreciation terms were changed in depreciation area 01 since the last time depreciation was recalculated. The values for Ordinary deprec. that were saved in the database in fiscal year 2009 are therefore different from the newly calculated values by an amount of 22.33-.
Procedure
Check if the newly calculated values are correct. If they are, then carry out a depreciation recalculation. You should be aware that if you recalculate depreciation, new values could arise for all open fiscal years, and these would then have to be posted to the general ledger by means of a depreciation posting run.
If, on the other hand, you want to keep the values that are saved in the database, you have to set the depreciation terms back to how they were at the time of the last depreciation recalculation.
To see a comparison of the old and new values, you can use the Display dep. calc. function in the asset value display or the Recalculate values function in the Asset Accounting menu.
Proceed
And if we click on Proceed system take us to transaction recalculation of depreciation (t-code AFAR).
As per the diagnosis given in the message depreciation is recalculated whereas we have not run recalculation of depreciation (AFAR) but we have changed the useful life of Asset Class 2260 & 2265 from 12 to 10 years. and transferred few assets within company code by transaction code ABUMN. Is this happening because of that ?.
We are surprised that till last depreciation run (period 5) business were not getting any such type of message and from period 5 onward system started showing this message.
I was just checking planned depreciation for F.Y. 2009 of few assets and found that depreciation is not calculating properly.
I have run AFAR in test mode and taken list of recalculated assets and also checked the recalculated depreciation manually and found that depreciation is calculated properly. Now we want to run AFAR in final mode but before moving ahead we want take concern from asset expert that we are going on right track or which another steps to be taken to resolve the same.
One more thing I have noticed that if we run AFAR from F.Y. 2008 in test mode when F.Y. 2008 is closed system shows message "Error in Dep. Calculation" for all the assets related to F.Y. 2008 and before and when we open F.Y. 2008 and run AFAR again in test mode then system shows message "Error in Dep. Calculation" only few AUC assets.
When you change the depreciation key you can get this (in some cases to).
When have changed the default proprossal in an new asset from 12 to 10 there is no reason for this mesage. When this is done in 2009 and 2008 was closed (and no transaction in 2008) you run AFAR only for 2009. Do atest run and you see the result
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Paul,
Thanks for quick response.
I have ran AFAR in test mode in F.Y. 2009 when F.Y. 2008 is closed and checked that deprecation is calculating properly but the assets pertaining to F.Y. 2008 and there before are showing in error "Error in Dep. Calculation. I have ran AFAR in testing box by opening F.Y. 2008 and seen that system is not showing any error.
Now my question is, if i will open F.Y. 2008 in production system and run AFAR and repeat deprecation run for recent period what will be the impact in last F.Y. 2008.
Thanks,
Vishwa Dikondwar
Now my question is, if i will open F.Y. 2008 in production system and run AFAR and repeat deprecation run for recent period what will be the impact in last F.Y. 2008.
Do this as test then you will see the result, With AFAR you will already see if there are changes for 2008. Run AFAR only for 2009, when you run it for 2008 it is possible that there are changes.
User | Count |
---|---|
102 | |
8 | |
6 | |
6 | |
5 | |
4 | |
4 | |
4 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.