Fun with Financial Reporter - @ANY in Reporting Tree

Something else learned along the way last week . . .

1. The @ANY value, which is typically assigned only to the summary level, enables the reporting tree to be used for all companies. However, all child nodes must have a company assigned to them for the roll-up to work.

2. You can have multiple companies defined in Financial Reporter. If you select the company code @ANY, the FR default company is used to generate reports.
I had always assumed that @ANY also rolls all dimensions across all Companies up to the summary level as well - like below. But that is not the case.



The Branch dimension in the example needs to be accompanied by a Company value on the line.



This will roll the cross-company Branch results up to the summary level but the config in the previous image will not.

More fun with Fixed Assets . . . Part II - Mid month (15th of month) Convention

If you're using the Mid month (15th of month) Depreciation convention, there's a bug where if you edit the Remaining periods value, the asset will never fully depreciate. The final half month depreciation is left as NBV at the end of the asset life. Supposedly a fix is being investigated . . .

More fun with Fixed Assets . . . Part I - Negative Depreciation

F&O wants to produce negative depreciation for 6 of the 12 months remaining, then make up the remainder of the depreciation in the last 6 months. This is a newly imported asset that we've updated the remaining periods on after it was acquired and after a Depreciation journal for accumulated depreciation as of 4/30/2020 was posted.





I did some testing on this and it seems F&O wants to depreciate based on the Service life for the remainder of the acquisition year, then switches to the balance of Remaining periods for final year. Very odd and probably a bug . . . 

Fixed Asset Depreciation Proposal Producing Inconsistent Results

D365 F&O, PU 34.  Fixed asset depreciation proposal was working inconsistently across assets in the same company, and across companies as well. Some assets in one company were depreciating, while others weren't. Likewise, assets were depreciating normally in some companies and not others.

After a couple hours of troubleshooting, discovered the cause was the Depreciation profile Calendar setting set to Fiscal/Period instead of Calendar/Month. Setting to Calendar/Month resolved the issue.