Qlik Compose vs SAP Process Orchestration comparison

"There were many valuable features, such as extracting any data to put in the cloud. For example, Qlik was able to gather data from SAP and extract SAP data from the platforms."

"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."

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

"It's a stable solution."

"It is a scalable solution."

"One of the most valuable features of this tool is its automation capabilities, allowing us to design the warehouse in an automated manner. Additionally, we can generate Data Lifecycle Policies (DLP) reports and efficiently implement updates and best practices based on proven design patterns."

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

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

"Overall, I would rate SAP Process Orchestration a 10 out of 10."

"The solution is easy to use."

"The initial setup is easy."

"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 has all the features that are necessary."

"The solution's technical support is good."

"SAP Process Orchestration provides extensive integrations with external partners, supports B2B operations, and has prepackaged content that saves development time."

"It provides essential features such as continuous monitoring of all interfaces are crucial for our needs."

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

"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."

"There is some scope for improvement around the documentation, and a better UI would definitely help."

"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."

"My issues with the solution's stability are owing to the fact that it has certain bugs causing issues in some functionalities that should be working."

"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."

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

"The solution needs to move to the cloud."

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

"I feel that support is an area that needs improvement. They need to improve the response time and address the customer's issues as soon as possible."

"It's very difficult to find errors in a simple way."

"The product roadmap suggests it will approach the end of support in several years, and a lot of innovations are now implemented by SAP not in SAP PO, but in SAP Integration Suite, hence, the platform is stable, but doesn't receive a lot of new features in recent updates."

"This is an on-premise platform and one area they can improve on is having the ability to work with SaaS solutions."

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

"The price of the solution is expensive."

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

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

"The fee for maintenance is costly."

"Normally, you will have to choose CPU-based licensing...I rate the tool price a five out of ten."

"There are fees in addition to the licensing."

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

"The pricing for this solution is fine."

"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."

"Looking at market conditions, vendors nowadays are giving products at very low price levels. However, SAP Process Orchestration have not yet reduced their prices. The prices could be reduced a lot to stay competitive."

"My company deals with different pricing models of the product, according to which we don't pay for the solution directly, but we do pay for the maintenance part."