You’re offline. This is a read only version of the page.
86
Hello, our customer currently have issues when posting depreciation with calendar set as 4-4-5.
The system is calculating the amount equally for every month.
Everything is set correctly - the period frequency is Fiscal period and Depreciation year is Accounting or financial.
They upgraded from 2012 to d365 previous year. In 2012 they had no issues with that setup.
I red that maybe I need to create additional calendar on a weekly basis but the posts were from 3 years ago and I wondered if the things have change?
Can you please advice?
Hi all,
I did the same and observed one abnormality in service life. When I put service life as 5 years it automatically populate depreciation period as 263 periods. For 20 years it does 1058. While I can change it manually, I would try to rectify this to 52 weeks/year as it as 4-4-5 Fiscal Calendar. So every fiscal year will have 52 weeks, right?
Thanks
Hello Ludwig,
So I have an answer to my ticket. Our customer was working on R2 and on that version, the calculation was different for each period.
From R3 that was retired and with the described setups, the system is calculating equal monthly depreciations.
The solution still is to create a Fixed asset calendar on a weekly basis and when proposing the depreciation, to use To date = the end date of the respective period (4 or 5 weeks) and Summarize depreciation = Yes.
It will be an issue for calendars that already have transactions, because you cannot change it. The proposal is to create a new Book and to transfer all the assets there.
Hope that will help.
Regards,
Zlatina
Hi Zlatina,
Many thanks for the update.
I think the best is opening a support ticket with MS.
Would be great if you could keep us updated here.
Many thanks,
Ludwig
Hello again,
I tested on Contoso - FRRT. Started from scratch - created a new calendar 4-4-5; attached it to the Ledger; recalculated the periods; created new Book/Depreciation profile etc. but the result looks the same (I acquired the asset with the same value as in the example above; the depreciation periods are 96). So the system is proposing the correct dates for the proposal but the amount again is incorrect.
So the best approach is to open a ticket?
Hi Zlatina,
If you have a plain vanilla Contoso environment then try replicating the issue there.
Best regards,
Ludwig
Hello Ludwig,
Should I try that for the same company or for another? Because for that particular client I've tried on 3 different test DB and the outcome is the same. Maybe I should try replicating to a totally different DB? What will be your advise?
Many thanks,
Zlatina
Hi Zlatina,
None should actually be ok.
Can you please try replicating this issue in a different demo/test environment?
If you can and if you see the same outcome then open a support case with MS; might be a bug.
Many thanks and best regards,
Ludwig
Hi Ludwig,
For d356 the convention is None, but I have no access to the old DB for now - will write when I know.
Hi Zlatina,
Many thanks for the illustrative screenprints.
The 2020 depreciation seems indeed not correct based on what you expect.
Just wonder what you setup as depreciation convention in your old system and in D365FO?
Can you compare this setup in the book/value model?
Best regards,
Ludwig
Hello Ludwig,
The calendar is not new, still - I ran the recalculation process again (no change in the calculated depreciation).
So - this is the Ledger setup with the calendar
The Depreciation profile set up:
The Book set up
And also - the asset transactions - you can see that till 01/2020 all is OK (posted in 2012) and from 02/2020 the depreciation is the same every month (in d365)
Thank you for the time.
#1
Martin Dráb
439
Most Valuable Professional
#2
Abhilash Warrier
305
#3
Saalim Ansari
261
Share
Report
All responses (
Answers (
