Another pain point is the amount of IT support that is required to run this thing, and again, specialized knowledge of Hyperion products and how they work is required for IT to adequately support it.

Nobody except the HFM admin (which I used to be) in our company even touches this module. Not a great solution at all if you want multiple end-users to create reports in something other than Excel. It also requires a significant level of expertise to be able to use. I think there must be a strategic decision to move away from it and go to something more like Oracle BI because I just can't understand why in the world they don't update the reporting product. The interface for designing reports is not intuitive, and not easy to modify once a report is built.

The Hyperion Financial Reporting product is ridiculously outdated and clunky to use.This makes sense, but requires some significant expertise that most organizations do not have in-house. So, while the product is extremely flexible, you still have to be careful how you design your rules and calculations to make sure that you do it on the smallest subset of data as possible to avoid large processing times.

The consolidation process performs in direct correlation to the complexity of the calculation/consolidation rules. It has the been the quickest way for us to bring the system to it's knees. If multiple users attempt to translate the same data set, say goodbye to your performance but you have no way of knowing! (Unless you want to pull up a task audit which is not a very realistic expectation). Needing to translate the data over and over again is frustrating and there is no visibility into how many users are running a translation.

One pain point for us is the consolidation and translation process.

Integration Platform as a Service (iPaaS).

Unified Communications as a Service (UCaaS).

Sap bpc wiki