SAP should improve the user interface, as it often lacks modern features and aesthetic appeal. Additionally, there are other areas in need of enhancement, including monitoring features and end-to-end graphical representations, which have not been improved for many years.
Some configurations can be a little tricky. The consulting team had to spend a long time checking SAP's community forums and documentation to achieve some goals. The tool could release some new functionalities.
SAP Process Orchestration Team Lead at a retailer with 10,001+ employees
Real User
Top 10
2024-07-09T16:17:13Z
Jul 9, 2024
I think the big improvement required in the tool stems from the fact that the whole issue around it is that we have some downtime failures during upgrades and patching. The downtime phase is when we do maintenance, upgrades, backups, and then, of course, on the operating system side, when we need to do security patches and all those things. The whole improvement should be about automating those updates so there is no downtime.
AVP IT at a construction company with 501-1,000 employees
Real User
Top 20
2024-01-19T09:39:20Z
Jan 19, 2024
Implementing changes and introducing new interfaces in Process Orchestration should have been more straightforward. The current system is burdened with a heavy load and has become overly complex, managing multiple parallel interfaces within a single box. It would be more desirable for the system to be lightweight, efficiently handling its tasks without unnecessary complexity. It would be beneficial to enhance the ease of implementing new projects and improve overall stability in our implementations.
We encounter challenges while connecting to MQTT and MQDD adapters. We have to purchase some adaptors to connect to the MQTT broker. They could enhance this particular area.
Process Orchestration needs to provide secure connectivity as no one has any data information. Adapters are missing like XML are missing in SAP Process Orchestration V 7.3 and SAP Process Orchestration V 4. I am not sure if they are present in the upcoming versions.
SAP Process Orchestration could improve from an API standpoint. This is not an API management tool, which is one of its drawbacks. However, SAP has released an SAP Cloud Platform Integration which has all of the features, such as API management along with process integration to replace what they had previously. There will not be any more improvements to SAP Process Orchestration because they are ending the support for the solution. All the users using SAP Process Orchestration should move to SAP CPI, this is what is replacing. There are no longer any updates and they only offer maintenance. This solution is only going to be supported until 2027 or it might be extended to 2030. However, there will only be maintenance support. No additional features will be provided or released.
Technological Partner at Code-10 IT Consultants SL
Real User
2021-12-21T10:07:00Z
Dec 21, 2021
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. The other main problem nowadays is that there is no easy migration from SAP PO to SAP CPI. In terms of moving from Process Orchestration to Cloud Platfom Integration given all the connectivity requirements (not only within SAP environments, but also with third-party systems), I feel that there is more work yet to be done by SAP. In addition, the knowledge and know-how gained from using SAP PO cannot be fully translated into SAP CPI, so there's another area that they could look into making easier for users.
The solution could be more scalable. SAP doesn't recommend anyone to use this tool for high-volume transactions. SAP does not recommend users to connect PI Process to be connected to third-party systems. If SAP was more complete, we wouldn't need to have third-party apps within the system. Right now, we need either DataPower or an IBM CVM solution to act as that connect point.
Global Integration Lead & Architect at a manufacturing company with 10,001+ employees
Real User
2021-09-20T15:54:35Z
Sep 20, 2021
The solution could improve by making it more user-friendly by limiting the code required. We have to add some code in some cases where we need complex logic or some other functions. If this was able to be done in a more simplified manner then it would save a lot of effort and time. By liming code like in case of dynamic variables usage. We have experienced latency and reliability issues when using large amounts of data. In the future, they should come up with a solution to this problem. Latency in case of huge amount of data. Iterface gets timed out if data is very huge.
Infrastructure Specialist at a energy/utilities company with 1,001-5,000 employees
Real User
2021-01-27T10:01:16Z
Jan 27, 2021
We centralize all interfaces that we need to have. However, we spend too much money and time to construct each interface. This is required due to the fact that the systems are outdated. We need to be working with new interfaces that are required in the SAP Process Orchestration or use an older interface that is not by SAP PO. It can be dangerous if you don't have enough security, as you can be exposed to a virus attack. It's very difficult to find errors in a simple way. There isn't a simple way to troubleshoot. When we working with Java technology, Java programming, we need to leverage tracing tools in order to find out where the problem is. It's difficult when errors occur. Troubleshooting is very hard.
Consultant (SAP Integration) at a consultancy with 51-200 employees
Consultant
2021-01-23T13:07:02Z
Jan 23, 2021
It is a dying platform. It is going to expire in 2030, so nothing is expected. It is all data. SAP has to provide us with a replacement or a way forward in their SAP integration field.
Sr. ABAP Developer at Nigerian National Petroleum Corporation
Real User
2021-01-22T20:00:33Z
Jan 22, 2021
The main job for building, developing, on the tool is the NWDS. That is a NetWeaver Development Studio, and it has some technical things you cannot do unless you switch over to the web version. Therefore, you find yourself switching between tools. You find yourself in contracts, with issues, errors, and all that. They should perfect that. Other than improvement in what it's currently doing, I do not have anything in mind in terms of a new feature that I would like to see. It just an improvement of what is already available. The usability, for example, is an area where it can be improved upon.
Dell Boomi and MuleSoft have dedicated application based connectors. All of these connectors work on the same protocols such as SOAP, HTTP, and REST. They have dedicated application connectors that can be for Amazon, Salesforce, ServiceNow, Slack, Google Cloud, Microsoft Azure, Workday, etc that are readily available to use. When it comes to SAP PO, SAP provides SOAP, HTTP, or the REST-based adapters, which we can use to integrate with any of the above-mentioned applications / Webservices / APIs, etc. have to bit-customize to integrate with those particular applications. This is true when using REST, SOAP, or HTTP. I feel both application-specific adapters and SAP provided adapters (SOAP /HTTP /REST) adapters, They Still use the same set of protocols to integrate/Connect with respective applications. Customers will think that they had a dedicated application adapter that will make our life easier. We can just plug in, play, and use it. This is the way sales and customers think and they will tend to go with these tools. 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. Instead of maintaining so many tools, they should explore all of the features and offer just one tool. It would be good and would help customers as well as SAP. Since they have a cloud version of integration to SAP CPI, it would be a good idea to provide a migration tool where we can install that tool and migrate the existing interfaces from Process Orchestration to CPA. Customers would appreciate the flexibility, and it would reduce the project cost and manual effort time.
Software Engineer at a manufacturing company with 1,001-5,000 employees
Real User
2020-07-19T08:15:00Z
Jul 19, 2020
The cloud capability features need improvement. New connection features will be released like OpenDrive, Dropbox, and SharePoint features. All of those connections have to be launched. Which will help develop us to integrate with many third-party products. The user interface is good, but it can still use improvement in some areas. can improve the UI areas. They should show a more graphical representation of the data.
SAP Process Orchestration Team Lead at a retailer with 10,001+ employees
Real User
Top 10
2020-06-04T09:41:23Z
Jun 4, 2020
The company has come out with a new version, SAP Cloud Integrator, which is not as good as the older version. They are trying to get us to move over to that even though the application is not ready yet. Technology changes and more people are going to micro services and API management tools, which doesn't provide all the functions that the project orchestration environment has. They have a great product but now they're moving into something new and discontinuing the old product. The community is not happy and I think SAP should listen to their clients, offer continuing support for the old product while improving the new. I think they could work on simplification. There is a business process modeling tool that they have besides the integration side where you could have one point connected, one system, one source to a target system, but they have the process modeling tool, which basically allows you to connect users to each other. You can connect users within a system and then they can connect that system to another system and get a result. It's like an orchestration, a workflow. I think all of that could be simplified.
Solution Architect - SAP Banking at a financial services firm with 10,001+ employees
Real User
2020-03-22T06:49:12Z
Mar 22, 2020
SAP has decided to move everything to the cloud, which means that we have to invest more. New investments would include things like redevelopment and data transfer. In general, we are not satisfied with the roadmap. I would like to see more flexibility. It does not have all of the industry-standard solutions available in PO and it is not plug and play, so we have to do a lot of development.
Partner & SAP Netweaver Solution Architect at a tech services company with 11-50 employees
Real User
2020-03-04T08:49:00Z
Mar 4, 2020
In my opinion, the part that SAP needs to improve in Process Orchestration is the monitor and governance. The monitoring governance offered by SAP is too technical. Only the consultants that have technical skills or development skills are able to manage this product. What is missing, in my opinion, is a better business monitoring component. Our company creates business monitoring in UI5 and Fiori applications that help the customer to have a better view of what good monitoring is. With the technical monitoring of SAP, someone in the organization has to have technical skills rather than business skills. So using these solutions in combination, we are able to give the client another more business-oriented kind of monitor and governance which is not so technical.
The solution could be more customizable. It's customizable, however, it's underdeveloped. It supports custom modules, custom adapters, etc., but they need more time to truly develop them. It would help if the solution offered flexible adapters like REST adapters or some custom solution. It would help make it a more flexible product. In terms of technical support, it would be helpful if they handled the tickets a bit faster when queries are sent to them.
Improvements are needed with respect to being able to handle a very large volume of data. The responsiveness of technical support needs to be improved. The pricing can be improved.
SAP NetWeaver Process Integration facilitates the integration of business processes that span different departments, organizations, or companies. SAP PI is based on general standards so as to enable 3rd-party systems to be integrated. At the center of SAP PI is an XML-based communication that uses HTTP (Hyper Text Transfer Protocol). Irrespective of the scenario used, the application-specific contents are transferred in messages in user-defined XML eXtensible Markup Language) from the sender...
SAP should improve the user interface, as it often lacks modern features and aesthetic appeal. Additionally, there are other areas in need of enhancement, including monitoring features and end-to-end graphical representations, which have not been improved for many years.
Some configurations can be a little tricky. The consulting team had to spend a long time checking SAP's community forums and documentation to achieve some goals. The tool could release some new functionalities.
I think the big improvement required in the tool stems from the fact that the whole issue around it is that we have some downtime failures during upgrades and patching. The downtime phase is when we do maintenance, upgrades, backups, and then, of course, on the operating system side, when we need to do security patches and all those things. The whole improvement should be about automating those updates so there is no downtime.
Implementing changes and introducing new interfaces in Process Orchestration should have been more straightforward. The current system is burdened with a heavy load and has become overly complex, managing multiple parallel interfaces within a single box. It would be more desirable for the system to be lightweight, efficiently handling its tasks without unnecessary complexity. It would be beneficial to enhance the ease of implementing new projects and improve overall stability in our implementations.
We encounter challenges while connecting to MQTT and MQDD adapters. We have to purchase some adaptors to connect to the MQTT broker. They could enhance this particular area.
SAP Process Orchestration breaks down sometimes.
There is room for improvement in terms of performance. Another area of improvement is technical architecture.
The solution needs to move to the cloud.
Process Orchestration needs to provide secure connectivity as no one has any data information. Adapters are missing like XML are missing in SAP Process Orchestration V 7.3 and SAP Process Orchestration V 4. I am not sure if they are present in the upcoming versions.
The solution's administration management feature is very complicated to use. They should make it easier to access.
Process Orchestration doesn't provide authentication for data sent to us, meaning we have to rely on client certificate-based or basic authentication.
This is an on-premise platform and one area they can improve on is having the ability to work with SaaS solutions.
SAP Process Orchestration could improve from an API standpoint. This is not an API management tool, which is one of its drawbacks. However, SAP has released an SAP Cloud Platform Integration which has all of the features, such as API management along with process integration to replace what they had previously. There will not be any more improvements to SAP Process Orchestration because they are ending the support for the solution. All the users using SAP Process Orchestration should move to SAP CPI, this is what is replacing. There are no longer any updates and they only offer maintenance. This solution is only going to be supported until 2027 or it might be extended to 2030. However, there will only be maintenance support. No additional features will be provided or released.
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. The other main problem nowadays is that there is no easy migration from SAP PO to SAP CPI. In terms of moving from Process Orchestration to Cloud Platfom Integration given all the connectivity requirements (not only within SAP environments, but also with third-party systems), I feel that there is more work yet to be done by SAP. In addition, the knowledge and know-how gained from using SAP PO cannot be fully translated into SAP CPI, so there's another area that they could look into making easier for users.
The solution could be more scalable. SAP doesn't recommend anyone to use this tool for high-volume transactions. SAP does not recommend users to connect PI Process to be connected to third-party systems. If SAP was more complete, we wouldn't need to have third-party apps within the system. Right now, we need either DataPower or an IBM CVM solution to act as that connect point.
The solution could improve by making it more user-friendly by limiting the code required. We have to add some code in some cases where we need complex logic or some other functions. If this was able to be done in a more simplified manner then it would save a lot of effort and time. By liming code like in case of dynamic variables usage. We have experienced latency and reliability issues when using large amounts of data. In the future, they should come up with a solution to this problem. Latency in case of huge amount of data. Iterface gets timed out if data is very huge.
We centralize all interfaces that we need to have. However, we spend too much money and time to construct each interface. This is required due to the fact that the systems are outdated. We need to be working with new interfaces that are required in the SAP Process Orchestration or use an older interface that is not by SAP PO. It can be dangerous if you don't have enough security, as you can be exposed to a virus attack. It's very difficult to find errors in a simple way. There isn't a simple way to troubleshoot. When we working with Java technology, Java programming, we need to leverage tracing tools in order to find out where the problem is. It's difficult when errors occur. Troubleshooting is very hard.
It is a dying platform. It is going to expire in 2030, so nothing is expected. It is all data. SAP has to provide us with a replacement or a way forward in their SAP integration field.
The main job for building, developing, on the tool is the NWDS. That is a NetWeaver Development Studio, and it has some technical things you cannot do unless you switch over to the web version. Therefore, you find yourself switching between tools. You find yourself in contracts, with issues, errors, and all that. They should perfect that. Other than improvement in what it's currently doing, I do not have anything in mind in terms of a new feature that I would like to see. It just an improvement of what is already available. The usability, for example, is an area where it can be improved upon.
Dell Boomi and MuleSoft have dedicated application based connectors. All of these connectors work on the same protocols such as SOAP, HTTP, and REST. They have dedicated application connectors that can be for Amazon, Salesforce, ServiceNow, Slack, Google Cloud, Microsoft Azure, Workday, etc that are readily available to use. When it comes to SAP PO, SAP provides SOAP, HTTP, or the REST-based adapters, which we can use to integrate with any of the above-mentioned applications / Webservices / APIs, etc. have to bit-customize to integrate with those particular applications. This is true when using REST, SOAP, or HTTP. I feel both application-specific adapters and SAP provided adapters (SOAP /HTTP /REST) adapters, They Still use the same set of protocols to integrate/Connect with respective applications. Customers will think that they had a dedicated application adapter that will make our life easier. We can just plug in, play, and use it. This is the way sales and customers think and they will tend to go with these tools. 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. Instead of maintaining so many tools, they should explore all of the features and offer just one tool. It would be good and would help customers as well as SAP. Since they have a cloud version of integration to SAP CPI, it would be a good idea to provide a migration tool where we can install that tool and migrate the existing interfaces from Process Orchestration to CPA. Customers would appreciate the flexibility, and it would reduce the project cost and manual effort time.
The cloud capability features need improvement. New connection features will be released like OpenDrive, Dropbox, and SharePoint features. All of those connections have to be launched. Which will help develop us to integrate with many third-party products. The user interface is good, but it can still use improvement in some areas. can improve the UI areas. They should show a more graphical representation of the data.
The company has come out with a new version, SAP Cloud Integrator, which is not as good as the older version. They are trying to get us to move over to that even though the application is not ready yet. Technology changes and more people are going to micro services and API management tools, which doesn't provide all the functions that the project orchestration environment has. They have a great product but now they're moving into something new and discontinuing the old product. The community is not happy and I think SAP should listen to their clients, offer continuing support for the old product while improving the new. I think they could work on simplification. There is a business process modeling tool that they have besides the integration side where you could have one point connected, one system, one source to a target system, but they have the process modeling tool, which basically allows you to connect users to each other. You can connect users within a system and then they can connect that system to another system and get a result. It's like an orchestration, a workflow. I think all of that could be simplified.
SAP has decided to move everything to the cloud, which means that we have to invest more. New investments would include things like redevelopment and data transfer. In general, we are not satisfied with the roadmap. I would like to see more flexibility. It does not have all of the industry-standard solutions available in PO and it is not plug and play, so we have to do a lot of development.
In my opinion, the part that SAP needs to improve in Process Orchestration is the monitor and governance. The monitoring governance offered by SAP is too technical. Only the consultants that have technical skills or development skills are able to manage this product. What is missing, in my opinion, is a better business monitoring component. Our company creates business monitoring in UI5 and Fiori applications that help the customer to have a better view of what good monitoring is. With the technical monitoring of SAP, someone in the organization has to have technical skills rather than business skills. So using these solutions in combination, we are able to give the client another more business-oriented kind of monitor and governance which is not so technical.
The solution could be more customizable. It's customizable, however, it's underdeveloped. It supports custom modules, custom adapters, etc., but they need more time to truly develop them. It would help if the solution offered flexible adapters like REST adapters or some custom solution. It would help make it a more flexible product. In terms of technical support, it would be helpful if they handled the tickets a bit faster when queries are sent to them.
Improvements are needed with respect to being able to handle a very large volume of data. The responsiveness of technical support needs to be improved. The pricing can be improved.