If you try reports in the Cognos Finance folder other than the m-Fin reports, you might encounter this indignity:
We here in the OUC have starting calling this the Red X of Death. Here is the cure.
Do the following, while you are connected to Cognos using MSIE:
Select the Trusted Sites zone (the green checkmark).
This week OUC and I finish up our series of Town Hall meetings introducing m-Fin reporting to the Boulder, Colorado Springs, Denver, and Anschutz Medical campuses. It has been my pleasure to present our work to you. The m-Fin reports are available in CU's Cognos production environment. If you find you do not have the necessary access privileges you may contact email@example.com
You are invited to sign up for hands-on training:
Seven m-Fin reports have migrated to CU's production Cognos environment. These are the first m-Fin reports to reach production.
If you are accustomed to finding production Cognos from the my.cu.edu portal you may enter there. The m-Fin reports reside in the same folder as the other OUC Cognos financial reports: Public Folders > CU Reporting > Finance
When m-Fin reports are run by org they return more speedtypes than are needed, particularly for project funds. The reports do have a filter to test whether a speedtype has had any activity during the fiscal year. The problem is even just roll-forward activity is considered current fy activity. Roll-forward processing is what moves ending balances for projects from one fiscal year to the next. Roll-forward processing by itself should not be considered current fy activity.