We use this solution for standard reporting for cost and finance accounting. It creates VAT reports, balance sheets reports, and a lot of cost reports. You can split the company into departments and produce individual reports to deduct or extract, for example, German projects, which have to be brought for tax collection for Germany. Since ELIN is an Austrian company, we have to take out the part that has to be allocated to the German tax authorities.
From what I understand, we have data tables in proALPHA and then we have a kind of intermediate bridge, which is the Microsoft environment where this data is copied, and then from that database it is brought into Qlik Sense.
Some of the valuable areas of this solution include producing individual reports and closing the gap. Within proALPHA, it is not possible to implement a link of information from separate parts. This link can be done by Qlik Sense.
What would help is an Excel sheet that is linked directly to Qlik Sense so that instead of having to produce an Excel file, you would already have an Excel file that is connected to Qlik Sense. I don't know why it is not already set up this way because it would be more convenient. Right now, it is complex and you have to understand the data model prior to analyzing it, so basically I would like to see an integration with Excel in the future.
I have been using this solution for two years.
The solution is stable and reliable.
The solution is easy to scale and about 20 people work with it in my company.
The rollout should be for the full user amount, which is roughly 200% from 20 to 200. But one main report is missing, and it doesn't make sense to roll it out because if they desperately need this one report and if it is not included or not completely correct in this new tool, then we would have understandable complaints from the users.
Integration was my colleague's responsibility. It wasn't easy, and altogether it took about one year. My colleague used some consultants for support because it wasn't easy to understand, collect, and integrate the data in the correct way, but the rest he did himself.
As far as I understand, there is a very low level of maintenance because he does as much as possible by himself.
Some reports are not fully translated from the old QlikView version into the modern Qlik Sense, including some basic reports in the construction business. One main report is missing because if it was completely deployed in the new Qlik Sense system, QlikView could be closed forever because QlikView's so old.
QlikView only produces aggregated amounts, so you can never trim down in it. In Qlik Sense, it's the opposite. The results are produced by collecting the specific entries, so you always have to trim down, which is obviously the better approach.
Qlik Sense is a good tool for BI in order to connect in normal circumstances, but not for integrated data tables in big ERP systems. I would rate this solution as a seven out of ten.