We performed a comparison between QlikView and SAP BusinessObjects GRC based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Tableau, Oracle and others in Reporting."This is a very cool application with endless options of creativity and visuals."
"A well designed app brings freedom of inquiry to meetings, allowing me to answer questions in real time and this has transformed progress and outputs of our monthly group meeting."
"This solution has simplified getting to and understanding our data, no matter where it is housed."
"On the positive side, QlikView's scripting is a great asset as it functions as an ETL."
"The initial setup is not very complex."
"Once you open it up, you see everything that you can do."
"It's pretty easy to deploy."
"One of the good thing is that you can integrate different data source technologies. So you can model your environment without having any of our views running."
"It is wonderful from the control perspective. The GRC tools help you in knowing what are the risk controls, how to mitigate risks, and how to ensure that there are no conflicts between the roles. From the user perspective, you get to know what are the permission risks and access risks. You get a lot of useful information."
"We have enterprise clients for the product."
"The best features are the scalability and flexibility to implement applications on top of the BW."
"Initial setup was straightforward. It took maybe one week."
"The tool helps create reports for projects, including the creation of any ad-hoc reports"
"Better source data connectors."
"The pricing is high."
"Improvement in collaboration, between that and publishing of reports and publishing of models."
"Syntax editor needs some work, it's frustrating to have valid syntax being flagged as incorrect."
"Improvements are required in the hide and unhide functionality that falls under the layout container feature that has been used in my company in recent times."
"They could provide a user-friendly analysis process rather than specialized IT resource code."
"Scalability really depends on the size of your data and QlikView server architecture. For the biggest data sets, it could become an issue at some point."
"Enhancing user-friendliness would be highly beneficial."
"BusinessObjects is very dated. It is not that user-friendly. It should be made more user-friendly. In addition, if they could make predictive analytics an embedded part of it where people get to know what is there to offer, it would be great."
"An additional feature I would like to see is the option to add wait time and integrate sources in wait time."
"Technical support could be better and faster."
"We cannot actively log in to the system. It should also improve support."
"I think the old system is better than the new one. From an improvement perspective, the tool needs to ensure that the new technologies it offers are better than the old ones."
QlikView is ranked 5th in Reporting with 158 reviews while SAP BusinessObjects GRC is ranked 1st in Continuous Controls Monitoring with 5 reviews. QlikView is rated 8.2, while SAP BusinessObjects GRC is rated 7.6. The top reviewer of QlikView writes "Useful for data visualization and business intelligence". On the other hand, the top reviewer of SAP BusinessObjects GRC writes "Improved our organization's reporting culture and has given us insights into operational results". QlikView is most compared with Tableau, Microsoft Power BI, Amazon QuickSight, SQL Server and TIBCO Spotfire, whereas SAP BusinessObjects GRC is most compared with Greenlight Continuous Monitoring, RSA Archer, Security Weaver, IBM OpenPages and Oracle GRC Controls.
We monitor all Reporting reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
Hi,
We haVE experience with both, so my summary is as follows:
SAP BO lost positions at every angle compared to QlikView because:
1/ Qlik is in-memory - and much-much faster
2/ Qlik is licensed fairly cheaper
3/ Qlik is more stable on highload
4/ Qlik package is more complete compared with same functionality package from BO (like ETL, …)
QlikView = SAP BO * 1000 at a reporting level.
Nowadays, SAP BI solutions developed by IT department's try to have a solution in memory like QlikView for reporting: fast, easy to use (SAP BO is too hard) for end user, low cost (human, time).
In my experience,
Business Objects has enterprise administration and controls, so reasonably
good governance. It is very good for creating standard reports so if you
have a need to create and burst out 200 reports on a Monday morning say, it
is very good for that.
It is based on creating a Universe so their is quite an intensive build
period before beginning to drive and insights. The Universe acts as a data
map and the data continues to reside in the database. The issue with this
is that if you ask for frequent updates this hits the databases and
depending on the latency there may be a significant time lag to see your
results.
It is not good at agile data discovery and visualisation and as such could
be seen as a traditional BI tool ie people know what data they have and
what they want to see.
QLikview is very much in the category of data visualisation and
exploration. unlike the traditional BI tool it is very good for exploring
things you dont know in the data. That said, a bit like Business Objects
you do need to build a Qlikview DataMart (QVD) to hold the data in-memory.
QLikview does work in database up to a point but a numer of users have
commented on how clunky this is and not very efficeint. The number of
databases supported is poerhaps limited as well.
in a way there is a similar problem to that found with BObj in that in
order to see and explore the data in a Qlikview application, or document
(dashboard) you have to decide what data you want to appear in the QVD.
This involves scripting of the data access to build the QVD as well as
scripting of the front end app to presen the data. there is therefore quite
an overhead and again, you only see what you have prepared for.
The concept of exploring Big Data in a free way ois therefore, difficult
with QLikview. For those who know what they want to see it can be an
attractive experience with the ability to explore and filter data quickly
but within the constraints of the QVD(s)
Overall, both have significant strengths but both are looking a little
dated compared to other tools in the market.
In terms of the specific question " which is better for reporting" - that
would have to be Business Objects.
Hope this helps
Regards
Alan
Our company evaluated QlikView but found SAP BO meeting our needs. Hence we went with SAP BO and have found it good.
I would say they serve different audiences but can also be used at the same time in an organization.
If we look at QlikView it is more for the business then IT, however if you
want to use all the possibilities, you can program a lot. With that part in
mind, maintaining will get problematic unless you use QlikView server and
let a general department (like IT) handle the most used official templates.
It has great visuals which you can use to define a dashboard to your
likings. But to make use of it all, you would have to spend some time on
it. If I would look at people who are making analysis, I wouldn't like to
get to know all that stuff. But as a BI Consultant it is a good product to
work with it.
SAP BO, I have used the different versions for lets say more then 10 years,
is more for enterprise companies with a good integration with the other SAP
software. It is used from the portal and for reporting I think it is one of
the better reporting tools. They have got Webi for interactive reporting,
Crystal Reports for pixelperfect reporting. Next to that they also have
dashboarding tools.
The Webi is mostly used by business for making adhoc reporting. The other
parts are mainly maintained by the IT department, so more an IT tool then
for the business.
If you combine both, you actually get a good solution. Give the business
for analyzing what they want to do on their own (although there is also
Tableau or SAP Lumira) and do the more official stuff, reporting and
dashboarding within the IT.
If you would like to make a comparison on Enterprise software, then I would
say SAP BO vs Jaspersoft (Open Source). I am currently busy with Jaspersoft
server (multi-tenant version) and that has some interesting parts.
The tools have total different approach : in BO you have to build your "world" from your data base and that's the reason IT people recommend this tool but it is more report generator than a BI tool
With QLIK - VIEW you start with the need and then analyze the insights you are looking for . QLIK - VIEW can serve you in more complicated information reports. with QV you can build report applications that you can not do with BO
QlikView does an excellent job of evolving with an organization as it can move faster than an organization thinks. As clients work with their data, their business understanding grows.
In my experience the two are different tools for different purposes. QlikView is a very good data exploration tool, but not so much a traditional reporting tool for batch type reports. SAP BO is more traditional ,but in my experience pretty buggy, to the extent that we are replacing it with Microstrategy.
Thanks,
Rich