Qlik Compose vs SAP Process Orchestration comparison

"It's a stable solution."

"As long as you pick the solution that best fits with your requirements, you won't find that performance is a problem. It's good."

"It can scale."

"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."

"I like modeling and code generation. It has become a pretty handy tool because of its short ideation to delivery time. From the time you decide you are modeling a data warehouse, and once you finish the modeling, it generates all the code, generates all the tables. All you have to do is tick a few things, and you can produce a fully functional warehouse. I also like that they have added all the features I have asked for over four years."

"The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities."

"Qlik Compose is good enough. It is user-friendly and intuitive."

"I have found it to be a very good, stable, and strong product."

"The monitoring tools are the most valuable feature."

"The most valuable feature of SAP Process Orchestration is its flexibility in being able to build integrations with SAP systems and non-SAP systems."

"The product has good technical support but you usually will not need it because it is quite stable."

"SAP Process Orchestration offers easy maintainability and is a very flexible tool that easily adapts to any integration standards and artifacts that are readily available."

"SAP Process Orchestration is quite flexible in supporting various integration standards and protocols, and it's fulfilling all our needs."

"The standard adapter with EBA abilities is the most valuable feature. It has good process integration."

"I think it is a very stable tool. My company did not have any problem with the tool."

"Great monitoring tools and has its own alert framework."

"There should be proper documentation available for the implementation process."

"It would be better if the first level of technical support were a bit more technically knowledgeable to solve the problem. I think they could also improve the injection of custom scripts. It is pretty difficult to add additional scripts. If the modeling doesn't give you what you want, and you want to change the script generated by the modeling, it is a bit more challenging than in most other products. It is very good with standard form type systems, but if you get a more complicated data paradigm, it tends to struggle with transforming that into a model."

"There could be more customization options."

"When processing data from certain tables with a large volume of data, we encounter significant delays. For instance, when dealing with around one million records, it typically takes three to four hours. To address this, I aim to implement performance improvements across all tables, ensuring swift processing similar to those that are currently complete within seconds. The performance issue primarily arises when we analyze the inserts and updates from the source, subsequently dropping the table. While new insertions are handled promptly, updates are processed slowly, leading to performance issues. Despite consulting our Qlik vendors, they were unable to pinpoint the exact cause of this occurrence. Consequently, I am seeking ways to optimize performance within Qlik Compose, specifically concerning updates."

"Qlik's ETL and data transformation could be better."

"It could enhance its capabilities in the realm of self-service options as currently, it is more suited for individuals with technical proficiency who can create pages using it."

"For more complex work, we are not using Qlik Compose because it cannot handle very high volumes at the moment. It needs the same batching capabilities that other ETL tools have. We can't batch the data into small chunks when transforming large amounts of data. It tries to do everything in one shot and that's where it fails."

"I'd like to have access to more developer training materials."

"It is scalable, but there can be performance issues with high data volume or traffic, especially during month ends."

"SAP Process Orchestration breaks down sometimes."

"The user interface of SAP Process Orchestration should be more modern to enhance its appeal. It can seem complicated and outdated to new users."

"In terms of technical support, it would be helpful if they handled the tickets a bit faster when queries are sent to them."

"It is not a scalable solution for the cloud. I would not recommend this for the cloud."

"Data modeling is an area of concern in the product where improvements are required."

"I think the main area that SAP PO should improve on is offering pre-delivered content like they do when you use SAP Cloud Platform Integration (CPI). SAP should not forget that they still have a lot of customers using Process Orchestration and they should focus more on providing pre-delivered content in SAP PO."

"We encounter challenges while connecting to MQTT and MQDD adapters."

"On a scale of one to ten, where one is cheap, and ten is very expensive, I rate the solution a six."

"The price of the solution is expensive."

"While they outperform Tableau, there's room for improvement in Qlik's pricing structures, especially for corporate clients like us."

"It is a very expensive solution. We only pay for the license."

"We subscribe to annual licenses, and the competitive license cost is reasonable."

"The price of SAP Process Orchestration was reasonable."

"The cost of SAP products is quite high but the quality is really good."

"It's not an expensive solution."

"The product is not a low-priced solution, but I can say that it is competitively priced in the market."

"The pricing depends on what type of client you are with SAP and the contract you have. There is a licensing cost that needs to be paid."

"The fee for maintenance is costly."