Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Hi, there's a issue on last two months (end of January) the depreciation amount suddenly drop. We have to do an adjustment , any setting or bug in AX3 to cause this problem.
Please don't use capitals only in titles or the body of your posts. It is considered as screaming which is not allowed on this forum. I have corrected it for you.
Can you tell what depreciation profile you are using? What settings have been done in your environment?
Sorry for the capitals used. We are using straight line method.
Is it possible that somebody was changing the amount to be depreciated manually after creating the depreciation proposal?
Cannot be, cause not even one fixed assets having the same problem actually is the whole fixed assets list. Even I try it at TEST environment still the same problem.
If you can replicate that in a test environment then this seems to be buggy. As AX3 is already out of support you will need the help of a developer to get that fixed though. There are no hotfixes provided for download for this old version.
I know, but I just I want to know what others setting causing this problem. It's ok , thanks.
I don't know any setting that causes such a behavior and can only imagine that somebody played around with the value models' remaining periods.
For more details you probably have to have a developer look at that
For an example:- setup for the depreciation of BLDFA00014 Dec'17.
It should be depreciated at IDR 705,833.33 per month.
In Dec'17, the calculation is (IDR169,400,000-IDR705,833.33)/240 = IDR702,892.36, which is not correct.
This might have indeed been an issue for which MS provided a hotfix. Yet, since AX3 is already out of support for a long part you are on your own getting this fixed.
Business Applications communities