SAC Review from a 2-year every day userhttps://www.trustradius.com/corporate-performance-management-cpmSAP Analytics CloudUnspecified8.21751012019-07-09T17:03:28.463Z
July 09, 2019
SAC Review from a 2-year every day user
Score 7 out of 101
Overall Satisfaction with SAP Analytics Cloud
As an information technology enterprise, we have been working for 2 years with SAP Analytics Cloud. We are implementing it in multiple projects and as the experience learned in these 2 years I found some really good functionalities and some others that are missing. The SAP department from my company is currently working with SAC we put it on the roadmap for our client. SAC is offering a vision for reporting which is not so dense. Not really operational but really functional. Sales management and quick dashboarding instead of heavy reporting or planning
- Functional desing. Easy to learn and develop
- Live connectivity to SAP sources so the data is not needed to be in the cloud (important for some business for data privacity)
- SAC is working in different functionalities
- SAC is growing in a scheduled way so you can know which roadmap will be the following months
- Easy SSO with SAP sources
- In almost every wave or release something gets broken. We have been finding many problems along the different releases (missing functionalities or some stories get "broken" in some way)
- SAC is growing in a reactive way, not in a proactive way. That means that are the users directly who suffer the problem when implementing. That has happened the last two years of SAC
- Live connection is working really good. But data acquisition models are really bad. There is a limit of registers that is almost impossile to construct a model equal or similar than a live data connection. And that's needed because the new functionalities are based on offline models...
- In the stories the performance is really bad (now I have to say that is better than at the beggining). The page filters are taking a lot of time to load (connection to BW on HANA at least). Tables take a lot of time also to load compared to graphs and the scrolling is sometimes inside the table so there are some cells that cannot be properly seen.
- Application design and Canvas are not going to be unified. That's (in my opinion) a big fail.
Here there are two main differences: In the first case, when is about live data connection it is really a good solution against competency. But it needs a SAP data source so it can work. In terms of offline models it is not so good. Models uploaded from a data source, for example, BW are really complicated to create and to maintain by refreshing them. The quantity of registers is really small and sometimes is not possible to perform aggregations or similar.
That is one of the better things of SAC. Security, for example, plays a really important role when SAP is the data source. Is really simple to apply an SSO security in live data connection so that the security can be defined in the model. When adding security to a data acquisition model it has serious problems, so it needs improvement. Data is really simple to share, and the connectivity is really simple and easy.
- Dashboarding in a visual way (forget tables)
- When sources are SAP and live connectivity is available SAC is perhaps the best option
- Can manage many users so the concurrence is really good.
- The business content library is dense. That means users can be more autonomous
- When some dense reporting is needed through tables
- When the source is not SAP