SAP Techno-Functional Architect & SME at Graviton
Real User
Top 10
2024-04-29T17:23:00Z
Apr 29, 2024
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.
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.
API (application programming interface) management is the process of managing different API functions, such as designing, releasing, documenting, analyzing, and monitoring APIs in a safe environment.
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.