SAP Process Orchestration Reviews

The solution is used for file servers, soft services, and other RSC services also connected with SAP Process Orchestration

SAP is an ERP solution that has provided protection in NSG, and our models are integrated into each other.

The adapter, the communication channels, center receiver agreements, and a lot of features in SAP Process Orchestration are good. When we need connectivity confirmation, we connect with the Process Orchestration. Plus, we can also connect the SAP HANA system, Oracle ACC, to the Process Orchestration server.

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.

I have been using the solution for two years.

It is a very stable solution. I rate its stability ten out of ten.

I rate its scalability an eight out of ten. Around five hundred end-users are using the solution.

I rate the support five out of ten because we needed the support and communication while deploying the solution and did not need it after that.

Neutral

The initial setup is easy. Just some steps need to be followed, like data types, message types, and operations. The solution gets automatically connected. The deployment takes six months. I rate its setup phase a ten out of ten. Only one person is needed for the deployment. The deployment was done on the cloud and on-premises.

It was implemented by both the in-house team and a third-party team.

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

I will recommend the solution as it is a very secure solution. I rate the overall solution a ten out of ten.

SAP Process Orchestration has all the features that are necessary.

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 have been using SAP Process Orchestration for approximately 11 years.

The technical support from SAP Process Orchestration is good, but the response times are based on the priority of the issue which causes delays. However, SAP offers different support. If you need priority to your issues, you can choose MaxAttention, which is a different kind of support that SAP offers. MaxAttention is very good in terms of emergency issues.

When SAP Process Orchestration is integrated it is important it is done well. This can be done through the services and architecture. There are many connectors to do most of the complex integrations.

It is important to understand how Java works and the pipeline.

Someone who has to work on a PO should at least have a basic understanding of Java because as it is an integration tool, the way SAP provides to transform the messages from one structure to another is very good. This understanding of Java as a backend is important because SAP also supports writing mappings on Java, which they call it Java Mappings.

I would rate this tool from an ESB point of view for integrating on-premise applications, a nine out of ten, not as an overall integration tool. An overall integration tool has API management which is missing.

I rate SAP Process Orchestration a seven out of ten.

We are using the solution for authentication purposes.

The product is a useful solution for integrations with any internal systems or any third-party systems as we're connecting SAP to our end-user.

SAP works best when a business doesn't require any additional apps in the architecture.  

The solution is very stable. 

Technical support is helpful.

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. 

In terms of the Orchestration, I've been using it for the last three years, however, the systems landscape I've been familiar with for more than ten years.

The stability of the product is very good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The solution isn't meant to scale when high-volume transactions are in play. The scalability could improve. 

Currently, the technical team is using it, and all the users who are using SAP for the first time are connected via an API due to the fact that they are integrated with a third party or other internal downstream applications.

While I have never contacted technical support, my technical team has. Their level of service is fine. We have an enterprise license and it's a very big company. The responses we get are very quick. We have SAP implemented in almost 38 countries. 

I was not involved in the initial setup. I cannot speak, from first-hand experience, how easy or difficult it was at the outset. 

It's a BI (Business Intelligence) solution and we have a few managers that assist in maintaining it. 

I'd rate the solution at an eight out of ten. We've been pretty happy with the product so far. 

I would recommend the solution to others. All SAP products are good. As long as businesses are flexible they will be fine. If they try to customize any of the SAP solutions themselves, it becomes really hard in terms of the process.

I am an integration architect involved in the implementation side of SAP PO (Process Orchestration) where we deploy hybrid implementations for customers. Of our ten current customers, most are technical users of SAP PO.

Every day we integrate more and more components with other components. Naturally, the tendency of the market nowadays with middleware tools like SAP PO is to have all the various systems integrated within themselves and with third-parties, and so on.

In my opinion, SAP PO is the most mature suite of tools to integrate processes across SAP environments at this moment. It's really unbeatable because it allows you to integrate whatever scenarios you can imagine. Compared to the rest of the tools available, including other SAP tools like SAP Cloud Platform Integration, it's the most well-developed and versatile suite on the market when it comes to process integration.

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.

I've been using SAP Process Orchestration for the past 12 years. 

It's a very stable and mature solution.

SAP PO is not as easily scalable as the cloud solution, but it is certainly scalable. That's the idea, after all. Every day you need to integrate more components with other components, scaling up as you go.

The technical support is good.

The initial set up is quite easy and straightforward. Of course, that depends on who does it, but with my years of experience, it's not a problem. All in all, it took me around one week for the installation.

I am the implementation consultant and I can say that the pre-requisites and staff requirements for implementing SAP are very target dependent, and it all depends on the project at hand.

Like most other middleware tools, it's not particularly demanding in terms of having lots of people involved. However, you do need professionals who are well-qualified.

The license is a one-time payment, and additional costs are only incurred on the infrastructure side since it's an on-premise solution.

My advice is that it's not a good idea to re-implement the wheel. It's better to go with secure and mature tools. And if you have a SAP ecosystem it's better to stick with the products of SAP. SAP PO is a very mature product and if you're going the cloud middleware route, I'd put forward that it's a good idea to have a hybrid test scenario with a combination of SAP PO on-premise and SAP Cloud Platform Integration together.

I would rate SAP Process Orchestration a nine out of ten.

I primarily use Process Orchestration for integration.

Process Orchestration fulfils the need for middleware to mediate types of connectivity.

Process Orchestration doesn't provide authentication for data sent to us, meaning we have to rely on client certificate-based or basic authentication.

I've been working with Process Orchestration for over ten years.

Process Orchestration's stability is fine.

Process Orchestration is highly scalable.

It depends on how much you pay SAP for support. If you pay for maximum attention, you can access a dedicated person to help with any problems.

The initial setup was a little complex because there were a lot of distributed components.

We have seen an ROI from Process Orchestration.

The fee for maintenance is costly.

Adobe has stated it is ending support for Process Orchestration in 2027, so it would be better to look for an alternative like SAP CPA. I would give Process Orchestration a rating of nine out of ten.

We use it for facilitating seamless communication among varied enterprise applications and integrating diverse hybrid technologies to enable the exchange of data and information between servers.

It facilitates the automation of various processes, particularly those demanding real-time data exchange between systems. This tool is instrumental in bridging gaps between two systems by synchronizing data, ultimately minimizing human intervention through the automation of diverse processes within Orchestration. SAP Process Orchestration serves as an excellent middleware tool for interfacing and exchanging data across digital channels.

Our priority is to establish a high-availability environment that is error-free, stable, sustainable, and easily scalable. It offers simplicity in design and configuration, along with the capability to seamlessly adapt to evolving business requirements. It provides essential features such as continuous monitoring of all interfaces are crucial for our needs. The documentation provided by SAP is clear and easy to follow.

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.

I have been working with it for approximately seven years.

The system frequently experiences hang-ups, posing a significant challenge. Unfortunately, there seems to be no definitive solution; troubleshooting involves multiple root causes, and restarting is not always an effective resolution.

Currently, over a hundred interfaces are utilizing the server, and we intend to streamline our middleware infrastructure. The plan is to consolidate multiple middleware servers, encompassing more than a hundred to two hundred interfaces, into a centralized environment. This approach ensures scalability, optimal system performance, and facilitates the smooth transfer of all interfaces from various systems to a single centralized environment. The long-term goal is to simplify monitoring by having a single environment overseeing all types of interfaces.

The technical support from SAP is commendable. However, the support process involves different levels. Level one entails a basic investigation, and based on the incident's complexity, it may escalate to the second or third level. If it is product-related, it reaches level three of product support. Despite the established process, reaching the product support level is time-consuming. The resolution of actual product issues takes longer than anticipated. To enhance customer experiences, SAP can reduce the initial response time, improving turnaround time for issue resolution. Additionally, there is a need to enhance stability and optimize SAP BI for handling high-volume transactions and data exchanges, making it more lightweight.

The initial setup is quite straightforward.

Deploying SAP Process Orchestration for a couple of interface scenarios can be accomplished within a timeframe of four to eight weeks. Leveraging our in-house consultants, the initial steps involve managing the hardware and determining the landscape structure—whether opting for a two or three-system configuration. Configuration activities include linking all satellite systems to the SAP PO system and establishing necessary settings such as File Landscape Extension, exchange profiles, technical systems, and business systems. The next steps involve defining these elements within the SAP Process Orchestration environment. Once the groundwork is laid, the interface development process begins. Breaking down the interfaces into specific formats and fields is crucial. This involves creating mappings for the fields, specifying how data exchange should occur between systems. This comprehensive exercise is undertaken by the SAP Process Orchestration consultant.

We subscribe to annual licenses, and the competitive license cost is reasonable. We find that the cost is even more affordable compared to other options available in the market.

It is highly recommended for customers seeking a lightweight application. Overall, I would rate it seven out of ten.

The solution is mainly used for integration.

The monitoring tools are the most valuable feature.

The solution needs to move to the cloud.

I have been using the solution since 2004.

It is a stable solution.

It is a scalable solution.

The technical support is good for us as we are the premium clients.

The initial setup is simple. It takes three weeks to deploy it.

The implementation was done by in-house team.

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.

It is a good solution. I rate the overall solution a nine out of ten.

It is mainly an SAP proprietary integration tool, and SAP suggests using it as process orchestration. However, irrespective of the integration we deal with, it is strategically focused on forecasting a global integration platform for our business.

The most valuable features are the troubleshooting, electing mechanism, processing times and monitoring techniques.

I have 17 years of experience working with SAP at my company. We are using version 1.5 of SAP Process Orchestration, which is deployed on-premises.

It is a good and stable product.

It is scalable and it requires some maintenance.

I rate the technical support a nine out of ten.

Positive

The initial setup was straightforward. It is an easy deployment if you follow the SAP standards.

I rate this solution a nine out of ten. SAP is good in the market.