Can’t figure out why my fixed asset depreciation report is throwing back error. Any suggestions?

the error says some departments and classes are inactive. you need to activate inactive depts and classes, and your journal will go through (or show another error..)

Thanks @Karina. I noticed that too, and can’t figure out where it’s coming from because as far as I can see, I don’t have anything inactive at all. argh.

1. You may be able to dump the list of depreciable fixed assets with the department and class segments. 2. Then compare to the active departments and classes against the FAM listing. 3. Activate the inactive Segments 4. The identified FAM records and transfer between inactive segment to a active segment. If this does not work then this may be related to a FAM bundle update on field mapping.

some old ones are probably lingering somewhere…. I would run the list of assets with dept and locations to see what’s there if all your depts and locations are active and compare the two

Thanks for the suggestions!

Other thing to try is maybe you have switched on mandatory department and class on journal lines. If any of your assets have a blank department or class they won't be able to post

I have an update. I run the BG Summary Records List to find the asset records causing the errors. In view, I could see the department - which turned out to be a department where the assets have been fully depreciated for a while. The department was marked inactive back in December. We have run depreciation since then but didn’t get the error until now. We activated the department again, and voila. No more errors. But, but, but…. we should be able to inactivate a department associated with assets that have been fully depreciated. There was an update to the module, I understand. Maybe something related to that?

@Kika Barr - thank you for the update! yes, interesting and yes, logically it should allow you to run depreciations where fully depreciated assets have inactive department…. But I see the logic NS uses as well - if the asset is still in service with $0 NBV department must be active. Perhaps, this logic now prevails with 2022.2 upgrade.

That’s the only thing I can think of as well. We are poking about with our NS consultant. I will post more information if I get any. A huge thank you for the suggestions. They really helped. 🎉

I would contact NS support to confirm

We contacted NS support and found out the reason why our depreciation report was throwing errors. We created a department a while back, but didn’t setup correctly for depreciation. Once we marked it inactive, the reports were running without errors until the new version was released. It had logic in it to detect a mistake we made a while back. All good now. Thanks everyone!

@Kika Barr - thank for the follow up! always good to understand what really happened👍🏻

For sure!