BTP Architect at a government with 1,001-5,000 employees
Real User
Top 5
Oct 24, 2025
Areas that could be improved with SAP Integration Suite include tools for monitoring and separated error analysis. Some reports contain everything, leading to difficulty in finding particular messages, requiring custom fields to filter out. The reporting should be improved, and currently, performance metrics, statistics, and other essential features require Cloud ALM. In PIPO, there were complex and effective tools to measure performance and how messages were processed, but Integration Suite still does not have solid reports that are useful for evaluating and understanding possible bottlenecks. It is essential to predict potential problems in advance, not just react to errors after they occur.
I believe there are areas where SAP Integration Suite could be improved, such as enhancing message transformation capabilities and simplifying conditional routing features compared to the on-premise tool SAP PO (Process Orchestration). Over the past five years, Integration Suite has evolved rapidly, but there is room for improvement, especially in message transformation techniques and graphical mappings. These improvements would make the application even more robust and user-friendly.
They could provide graphical data for over-viewing metrics such as payments, receipts, creditors, and refunds. The users prefer graphics instead of theoretical data.
If there are two or three instances, we have to make integrations for two to three instances. The instances are costly. If we need it for development, quality, and production, the cost is multiplied by three.
Senior Integration Consultant at a consultancy with 11-50 employees
Real User
Top 5
Nov 30, 2023
The product's UI could be faster. There's a limitation on the amount of logging data that can be generated and stored. There's a one-gigabyte limit for daily logs and a cumulative limit of thirty gigabytes over thirty days. It could be possible to send logs to an external service via HTTP, making it less tied to a specific backend system.
SAP Integration Suite is a comprehensive integration platform that facilitates seamless connectivity between applications and data sources, enabling businesses to streamline processes and enhance operational efficiency.SAP Integration Suite empowers businesses to address complex IT landscapes by providing tools for connecting cloud and on-premises applications. Its robust framework supports API management, data integration, and process automation, offering flexibility and scalability to meet...
Areas that could be improved with SAP Integration Suite include tools for monitoring and separated error analysis. Some reports contain everything, leading to difficulty in finding particular messages, requiring custom fields to filter out. The reporting should be improved, and currently, performance metrics, statistics, and other essential features require Cloud ALM. In PIPO, there were complex and effective tools to measure performance and how messages were processed, but Integration Suite still does not have solid reports that are useful for evaluating and understanding possible bottlenecks. It is essential to predict potential problems in advance, not just react to errors after they occur.
I believe there are areas where SAP Integration Suite could be improved, such as enhancing message transformation capabilities and simplifying conditional routing features compared to the on-premise tool SAP PO (Process Orchestration). Over the past five years, Integration Suite has evolved rapidly, but there is room for improvement, especially in message transformation techniques and graphical mappings. These improvements would make the application even more robust and user-friendly.
The setup process for the SAP integration Suite is not straightforward. It involves some technical aspects and can be complex.
They could provide graphical data for over-viewing metrics such as payments, receipts, creditors, and refunds. The users prefer graphics instead of theoretical data.
If there are two or three instances, we have to make integrations for two to three instances. The instances are costly. If we need it for development, quality, and production, the cost is multiplied by three.
The product's UI could be faster. There's a limitation on the amount of logging data that can be generated and stored. There's a one-gigabyte limit for daily logs and a cumulative limit of thirty gigabytes over thirty days. It could be possible to send logs to an external service via HTTP, making it less tied to a specific backend system.